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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-07-30 : 14:00:24
|
| boysie writes "I am using a SQl Server 7.0 in an NT4 SP5 environment. I created a backup jobs for our databases directly in the JOBS under the MANAGEMENT folder of the SQL Enterprise Manager. The jobs are merely TSQL backup commands. The 1st job does a full db backup and runs once a day. The 2nd job executes every 6hrs. and does a differential backup. The last one is for a transaction log backup which runs every hour of the day. The created backup files are initially stored on a local drive (different physical disk) and are later transferred to a tape at the end of the day. The backup jobs produce three files on a disk, one per every job. When the next job runs, transaction backup for instance, it will 'internally' append the data to the existing file, thus, resulting the backup folder to contain three and only three files for the rest of the day; that is, 1 for full db, 1 for differential backup, and 1 for the transaction log backup. We have done a restoration process for this to test if the latest backup information is saved and it did.When I tried to use backup jobs created by the Maintenance Plan wizard, it creates multiple backup files, one backup file per every job run. Meaning to say, if the transaction log backup executes every hour for 20 hrs., my backup folder would contain 20 transaction log files. So, which of the two backup jobs is more reliable and advisable to use, the TSQL job or the one from the Maintenance Plan? Secondly, when I tried to redirect my TSQL job to a tape device, (replacing the destination from TO DISK to TO TAPE but leaving all the parameters as is), it would also produce multiple backup files. Why is it so? Lastly, does the TSQL's full db backup command automatically checks the integrity of the database and the indexes as well?Thank you in advance and more power!" |
|
|
|
|
|
|
|
SQL7 Backup Behavior