February 2, 2009 at 2:33 pm
I need to restore a production database file to a different server for development purposes. The production database is currently on a differential-backup daily\full-backup weekly schedule (we are limiting the number of full backups due to the database size.)
In order to restore on a different server, we would like to create a full production backup in the early morning after some batch updates take place, run a restore job on the development server to pull over the production backup file, and then delete the full backup on the production server (to save space.)
My question is, is it possible to use a maintenance job to create the full backup, but not include it in the backup set for future restores to the production database? Currently when I create a backup job, the backup is grouped into the backup set for restores and I don't want to break the integrity of the restore process.
I hope this makes sense...
February 2, 2009 at 2:53 pm
if this is a one off process sounds like you want a one off job rather than make it part of the maintenance plan,
If i understand your requirements properly you should use the 'copy only' clause in backup, see BOL.
---------------------------------------------------------------------
February 2, 2009 at 2:56 pm
You should Restore your database with COPY ONLY option. When this used it is independent of your regular backups and does not disturb your differential backup sets according to your requirement.
Check this out:
http://technet.microsoft.com/en-us/library/ms191495.aspx
or books online for more info.
February 2, 2009 at 3:03 pm
Thanks so much...after reading about this process I believe it is exactly what I needed. I may have to re-post if I run into trouble using the process but at least it gives me a place to start.
February 2, 2009 at 4:17 pm
Its our pleasure, please do post if you are in trouble anytime.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply