[ThomasB]

We are changing our backup stratagey and will now need to use:

osql -E
backup database besmgmt to disk='c:\backup.bak'


1. Our database is about 100Meg and the backup ends up at about 12Meg.
We only have 8 users, is this reasonable.

2. The backup seems to append so that the fill grows by 12Meg each time.
Is there something I am missing.

I am sure it is something obvious I am missing and would appreciate any clues.

Tom

[jibi]

The database is automatically 100MB but when you export/back it up to a flat-file, the actual size is typically MUCH smaller than the default size. You may want to set up some sort of automated scheduling script to run a few hours after the download to zip up the .bak file, rename it to append the date to the .zip file and delete the original .bak file. It shouldn't append the database time and time again - you'd likely have a bad restore if it it came to that point.

[ThomasB]

Thanks!

I thought 100Meg was too big and 12Meg seemed more reasonable.

Is that normal for the backup to be appended?
If this is normal, I could just delete the previous backup just before running the scheduled job.


Thanks, Tom

[jibi]

Originally Posted by ThomasB

Thanks!

I thought 100Meg was too big and 12Meg seemed more reasonable.

Is that normal for the backup to be appended?
If this is normal, I could just delete the previous backup just before running the scheduled job.


Thanks, Tom

i'd say to keep copies of it for atleast a week or two. never good to delete last night's backup if tonight's is bad, ya know? i honestly do not use that method of backing up, so i'm not sure - within SQL 2000's maintenance, it actually names the .bak file with the date.

[Max_MBit]

Hi ThomasB,

Had the same problems you are encountering with the backup being appended.

I have solved the problem as follows:

1. Make a batch file with the following content:

osql -E -i backupbesmgmt.sql -o e:\sql_backup\backup.log

2. Create a text file called backupbesmgmt.sql containing the following:

backup database besmgmt to disk='E:\sql_backup\backup.bak' WITH INIT;

go

3. Schedule the task to run the batch at whatever interval required and you will have an backup which is almost identical in size to your productive DB. (You will have to modify the paths identified above to reflect those of your system)

[idontknow]

Default size of the BESMgmt db is 100 meg. I would not change this as its a perfectly reasonalbe size. When you have 100 users an a 10 gig transaction log, then you should be concerned.

More information on database backup maintenance: Shrink the transaction log
http://www.blackberry.com/knowledgec...?nodeid=832031

Again, with a db of only 100 meg, I would not worry at all.