Comments
Sort by recent activity
Thanks James. Not that we are currently backing up to the network but we will now move to 6.3 rather than 6.2.
Is Eddie looking at my last comment in http://www.red-gate.com/messageboard/vi ... hp?t=10008 about migrating to 6.? from 5.4 and not having a THREADCOUNT = parameter?
Thanks
Chris / comments
Thanks James. Not that we are currently backing up to the network but we will now move to 6.3 rather than 6.2.
Is Eddie looking at my last comment in http://www.red-gate.com/messageboard/vi ... hp?...
James,
So what was the pressing reason to release 6.3 after you said it was not coming out this quickly?
Thanks
Chris / comments
James,
So what was the pressing reason to release 6.3 after you said it was not coming out this quickly?
Thanks
Chris
Glad to hear that this is fixed in 6.3.
There seems to be some confusing information coming from Red Gate over 6.2 and 6.3. Only last month James Moore suggested that 6.3 wasn't going to come out for quite sometime http://www.red-gate.com/messageboard/vi ... php?t=9871 Now 6.3 has been released and as I am upgrading from 5.4 I want to know what would push me to 6.3 rather than 6.2 other than this is the newest version. I am partially thru the upgrade process and would need a good reason to start again.
Can someone give a good reason for going to 6.3, either in this item or in http://www.red-gate.com/messageboard/vi ... php?t=9871
Thanks
Chris / comments
Glad to hear that this is fixed in 6.3.
There seems to be some confusing information coming from Red Gate over 6.2 and 6.3. Only last month James Moore suggested that 6.3 wasn't going to come out f...
Robin,
Version 6.3 was promised soon in a post from August. Is bug SB-4359 part of 6.3 and is it still coming soon?
Thanks
Chris / comments
Robin,
Version 6.3 was promised soon in a post from August. Is bug SB-4359 part of 6.3 and is it still coming soon?
Thanks
Chris
Have you read http://www.red-gate.com/supportcenter/C ... 000250.htm
Also you may be low on VAS so you might need to look at using the -g switch at startup.
Chris / comments
Have you read http://www.red-gate.com/supportcenter/C ... 000250.htm
Also you may be low on VAS so you might need to look at using the -g switch at startup.
Chris
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 ...