Use the TSQL backup command to backup an active database.
Some advantages or running a server are * Centralised Print Management * Username and Password control * Centralised Backup * Control of workstations, for example with Microsoft Active Directory and Group Policy * Servers usually have better redundancy, for example hot swap hard drives and fail over network cards * Server software, for example Microsoft Exchange and SQL Server can only be run on servers. Not all server services need a server, for example MySQL can be run on a WindowsXP computer without restriction, whereas Microsft Exchange will only run on a server.
There is not excessive redo generated, there is additional information logged into the online redo log during a hot backup the first time a block is modified in a tablespace that is in hot backup mode. in hot backup mode only 2 things are different: o the first time a block is changed in a datafile that is in hot backup mode, the ENTIRE BLOCK is written to the redo log files, not just the changed bytes. Normally only the changed bytes (a redo vector) is written. In hot backup mode, the entire block is logged the FIRST TIME. This is because you can get into a situation where the process copying the datafile and DBWR are working on the same block simultaneously. Lets say they are and the OS blocking read factor is 512bytes (the OS reads 512 bytes from disk at a time). The backup program goes to read an 8k Oracle block. The OS gives it 4k. Meanwhile -- DBWR has asked to rewrite this block. the OS schedules the DBWR write to occur right now. The entire 8k block is rewritten. The backup program starts running again (multi-tasking OS here) and reads the last 4k of the block. The backup program has now gotten an impossible block -- the head and tail are from two points in time. We cannot deal with that during recovery. Hence, we log the entire block image so that during recovery, this block is totally rewritten from redo and is consistent with itself at least. We can recover it from there. o the datafile headers which contain the SCN of the last completed checkpoint are NOT updated while a file is in hot backup mode. This lets the recovery process understand what archive redo log files might be needed to fully recover this file. To limit the effect of this additional logging, you should ensure you only place one tablepspace at a time in backup mode and bring the tablespace out of backup mode as soon as you have backed it up. This will reduce the number of blocks that may have to be logged to the minimum possible.
hot chale ray
Yes. 2 options: 1) Cold backup, pre-script to stop oracle, post script to start up oracle again. 2) Hot backup, use oracle agent for backup exec.
1GHZ - 2GHZ MHz processor (Intel Xeon Processor) 512 MB- 2 GBRAM memory 40- 120 gig IDE / SCSI Hot swappable disk drive 56k modem DVD Ram IDE drive 10-20 Backup Disks .net (2003)Operating System Battery Backup
backup site would require frequent testing to ensure a smooth switchover in the event of an emergency?
if it is hot.
Cold(offline) backup / Hot (Online) backup, Logical backups using Exp and imp client utilities, RMAN Backups.
hot site
radiation
A hot air balloon.
6. And then her backup