March 18, 2014 at 5:03 am
We have a Server where every night we do a restore of our database from snapshot using the following command
ALTER DATABASE PRODUCTION_UPGRADE SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
RESTORE DATABASE PRODUCTION_UPGRADE FROM DATABASE_SNAPSHOT = 'PRODUCTION_UPGRADE_SS';
ALTER DATABASE PRODUCTION_UPGRADE SET MULTI_USER WITH ROLLBACK IMMEDIATE;
Every week we have restore on the source database of the snapshot from production.
The issue is randomly we are getting this message on the second to sixth day.It works fine on the first day after the restore from production.and we don't have any other snapshot for the server
Error: Database cannot be reverted. Either the primary or the snapshot names are improperly specified, all other snapshots have not been dropped, or there are missing files.
RESTORE DATABASE is terminating abnormally.
do we need to create a snapshot again after we restore source DB from the snapshot?
March 20, 2014 at 3:32 am
Any Help
March 20, 2014 at 10:49 am
Yeah, you need to take a new snapshot after the restore .
--
SQLBuddy
March 20, 2014 at 11:03 am
We use snapshots in much the same way - create a snapshot prior to the start of testing, then use that snapshot to revert the database and run the testing again. Where we have run into trouble, though, is when the snapshot goes through several of these iterations. There is a KB article that addresses this if you are using Windows server 2008 (and may be earlier versions). I don't have that handy, but the problem with the file system cannot continue to log the changes to the sparse file(s) that make up the snapshot and that will eventually lead to a corrupted snapshot database that can no longer be used. We got around this by recreating the snapshot following the successful restores so that the files will start fresh.
March 21, 2014 at 2:48 am
richard.bowles (3/20/2014)
We use snapshots in much the same way - create a snapshot prior to the start of testing, then use that snapshot to revert the database and run the testing again. Where we have run into trouble, though, is when the snapshot goes through several of these iterations. There is a KB article that addresses this if you are using Windows server 2008 (and may be earlier versions). I don't have that handy, but the problem with the file system cannot continue to log the changes to the sparse file(s) that make up the snapshot and that will eventually lead to a corrupted snapshot database that can no longer be used. We got around this by recreating the snapshot following the successful restores so that the files will start fresh.
Thanks guys !!
ya that is what we have decided as of now richard if you have the link to the KB article it will be of help 🙂 we are using 2008 now
March 21, 2014 at 7:44 am
Just had to remember the right search terms: http://support.microsoft.com/kb/2002606/es.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply