Comments
Sort by recent activity
In the GUI under Tools/Options or Server Options have you set anything under the delete from backup log history and backup history?
Chris / comments
In the GUI under Tools/Options or Server Options have you set anything under the delete from backup log history and backup history?
Chris
Brian,
I am just relating that from my limited experience with 6.2 that the level 4 does a wonderfull job of super comression but it comes with a high elapsed time penalty. My other results show that 6.2 has not increased the elapsed times of level 2 and level 3 backups as you expressed.
Thanks
Chris / comments
Brian,
I am just relating that from my limited experience with 6.2 that the level 4 does a wonderfull job of super comression but it comes with a high elapsed time penalty. My other results show th...
Thanks for the update James.
I am going to retest with the full and NORECOVERY. If I get the permissions error I will try making my SQL login a db_creator and try again.
Chris / comments
Thanks for the update James.
I am going to retest with the full and NORECOVERY. If I get the permissions error I will try making my SQL login a db_creator and try again.
Chris
James,
Making the SQL login a dbcreator fixes the intermediate problem of restoring the full backup but still being in recovery mode and then applying the differential.
Thanks for your insight. Now to get permission to make this change to our environment.
Chris / comments
James,
Making the SQL login a dbcreator fixes the intermediate problem of restoring the full backup but still being in recovery mode and then applying the differential.
Thanks for your insight. Now...
Not sure if this is good news or not. In testing 6.2 I ran 2 benchmark tests running 5.4 to backup a 230Gb DB with compression level 2 and then level 3. I wanted to see the differences in size and time taken. Both backups went to the same folder with a filetype of sqb. I then upgraded to 6.2.0.134 and ran another backup of compression level 2 to the same folder but with a filetype of sq6. I am now trying to fill the disk and watch the retries but suprisingly the old sqb backups were deleted by my 6.2 backup as they were older than the erasefiles value. I wasn't expecting this.
This is a W2K3 R2 SP2 cluster running SQL2005 SP2 build 3330 running a backup with VERIFY.
Maybe no need for the 6.2.0.1000 version after all.
Chris / comments
Not sure if this is good news or not. In testing 6.2 I ran 2 benchmark tests running 5.4 to backup a 230Gb DB with compression level 2 and then level 3. I wanted to see the differences in size and ...
Eddie,
Will this patch become the new 6.2 download version when you run Check for Upgrades? If not I suppose it will be included in 6.3.
Thanks
Chris / comments
Eddie,
Will this patch become the new 6.2 download version when you run Check for Upgrades? If not I suppose it will be included in 6.3.
Thanks
Chris
Thanks for the reply Eddie. Any ideas when 6.3 might appear?
Chris / comments
Thanks for the reply Eddie. Any ideas when 6.3 might appear?
Chris
One further question Eddie. We have decided to give our V 6 backups the filetype of sq6 rather than sqb so we know it was a V 6 backup or a V 5 backup. Will 6.2.1000.0 be able to delete sqb files when we have set our backups to write sq6 files?
Thanks
Chris / comments
One further question Eddie. We have decided to give our V 6 backups the filetype of sq6 rather than sqb so we know it was a V 6 backup or a V 5 backup. Will 6.2.1000.0 be able to delete sqb files w...
Look at this previous post
Delete existing backup not working
It mentions that V 6 will not delete V 5 backups.
Chris / comments
Look at this previous post
Delete existing backup not working
It mentions that V 6 will not delete V 5 backups.
Chris
Thanks Petey.
Now I will adjst my T-SQL scripts that we have in our SQL Agent jobs when we upgrade to 6.2.
Chris / comments
Thanks Petey.
Now I will adjst my T-SQL scripts that we have in our SQL Agent jobs when we upgrade to 6.2.
Chris