Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
bredinger
Starting Member
2 Posts |
 Posted - 2006-08-03 : 11:47:43
|
System Setup: - Windows Server 2003, SP1
- SQL Server 2000
- Veritas Backup Exec 9.0 w/ SQL Server Agent
- 73GB SCSI RAID-1 Array
- External FireWire Drive as removable backup device
I am planning on the FireWire drive going off-site on a daily basis.Questions: - What type of backup should be performed?
- What would be the best time for the backup of the SQL database backup to occur?
- Any other recommendations?
Thanks in advance to any suggestions made.---Brad |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-08-03 : 11:56:48
|
| Depends on the system - what it is used for, how much data, how critical, ...At least a full backup per week, per day if possible. All databases if possible - if not all weekly and user per day.With that use diff backups if possible if you don't have time for full backups as often as you would wish.Schedule these during periods of low activity.Consider log backups too - gives you extra securiuty put depends on systen==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
bredinger
Starting Member
2 Posts |
Posted - 2006-08-03 : 12:35:48
|
| Sorry about that, I knew I had left something out.The database is being used as our accounting and project management system. Vital to the business.---Brad |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2006-08-03 : 14:52:47
|
| 1) Either Full backup daily or Full backup weekly plus Differential backup daily.2) Take Transaction backups every 10 minutesMake sure that the backups are copied off the server as soon as they are made - e.g. to some other machine on the LAN - to safeguard against total failure of the server. Also make sure that they get onto tape "in reasonably short period of time" - once a day might be acceptable.Make sure that backups go off site, including having a policy for a 50 mile radius being evacuated.ALL database backups should be restored onto a spare server - to prove that the backups are restorable (See http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=69697 for story of a company with good backups, but a database corruption which had not been noticed for 2 months and spanned all recent backup files)As your data is mission-critical you could have a standby-server (onto which all backups are restored so that it is ready to take-over from the main server with only a few minutes data loss) which was remotely-located.You may get some further info from: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=55210&SearchTerms=How%20Backup%20works,What%20type%20of%20backup%20should%20I%20use,BackupKristen |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2006-08-03 : 14:54:21
|
| I missed a bit:"[Backup Exec 9.0]"Do NOT use the Tape Backup software to back up the database DIRECTLY to tape. Instead backup to disk, and then set up the tape backup software to backup the disk backup files AND to ignore the actual database files.Kristen |
|
|
|
|
|
|
|
|
SQL Server Backup Strategy [Backup Exec 9.0]