Comments
Sort by recent activity
Chris,
Are all the fixes in 6.5.2.18 included in the new V 7?
Thanks
Chris / comments
Chris,
Are all the fixes in 6.5.2.18 included in the new V 7?
Thanks
Chris
Eddie,
I know that V 7 is just about to be released but the 6.5.2.18 fix sounds like it might help a situation we see on occasion. The backup hangs and then has to be cancelled. It appears that this is happening in the verify part of the job. I had upgraded to 6.5.2.9 with Pete Yeoh's help and added a VERIFYINTERVAL parameter but the issue still persists every so often.
Thanks
Chris / comments
Eddie,
I know that V 7 is just about to be released but the 6.5.2.18 fix sounds like it might help a situation we see on occasion. The backup hangs and then has to be cancelled. It appears that thi...
Not sure if this will help you but here is what we do currently.
We copy the latest backup across to another server and restore it there also running DBB CHECKDB with PHYSICAL_ONLY and DBCC LOGINFO to see how many log fragments there are and checking possible corruption.
Would this work for you?
Could you do this in your storage compress enviroment you were testing?
Chris / comments
Not sure if this will help you but here is what we do currently.
We copy the latest backup across to another server and restore it there also running DBB CHECKDB with PHYSICAL_ONLY and DBCC LOGINFO...
Yes based on the quantity of data this probably isn't appropriate. I think we currently move around 1Tb of databases (150Gb of compressed backups) from a number of servers to two test servers (SQL2005 and SQL2008R2).
Chris / comments
Yes based on the quantity of data this probably isn't appropriate. I think we currently move around 1Tb of databases (150Gb of compressed backups) from a number of servers to two test servers (SQL2...
Eddie,
We are running 6.5.2.9.
What fix were added to produce 6.5.2.18?
Thanks
Chris / comments
Eddie,
We are running 6.5.2.9.
What fix were added to produce 6.5.2.18?
Thanks
Chris
From the forum posts you must be the only one using SQL Storage Compress V 6 that has issues.
Chris / comments
From the forum posts you must be the only one using SQL Storage Compress V 6 that has issues.
Chris
Looks interesting. I had seen HyperBac at PASS a few years ago but had just recommended SQLBackup, which we use exclusively for SQL2005, and may still use for SQL2008R2 for split backups as a means to save on backups.
The technology looked good at that time with a compressed drive containing the SQL database.
Good luck with your tests and the move.
Chris / comments
Looks interesting. I had seen HyperBac at PASS a few years ago but had just recommended SQLBackup, which we use exclusively for SQL2005, and may still use for SQL2008R2 for split backups as a means...
Please explain SQL Storage Compress. I know its not database compression because you are not talking about SQL2008 on onwards.
Chris / comments
Please explain SQL Storage Compress. I know its not database compression because you are not talking about SQL2008 on onwards.
Chris
A solution I saw at PASS I believe in 2009 or 2010 in which a server was being upgraded from SQL2000 to a SQL2008 Cluster used the Full backup being recovered with NORECOVERY followed by Differentials with NORECOVERY followed by Logs with the last one with RECOVERY. It wasn't until the last log with RECOVERY that the database was upgraded. The new server had been created and setup previously so that jobs, users etc matched what was on the old server.
Now if this was a SAN then I believe that a detach followed by a UNPRESENT (hope this is the right term) from the old server followed by a PRESENT to the new server followed by an attach could work. Again this would need the new server to have the infrastructure to run the app already there.
We now separate our system databases from our application databases so this could work.
Just a thought.
Chris / comments
A solution I saw at PASS I believe in 2009 or 2010 in which a server was being upgraded from SQL2000 to a SQL2008 Cluster used the Full backup being recovered with NORECOVERY followed by Differenti...
Is this the only database of many on the old server moving to the new one? / comments
Is this the only database of many on the old server moving to the new one?