September 9, 2011 at 4:58 am
Hi
Would like to have your opinion on if the copy of Live database is on DEV environment and is 200 gb in size and appears to be backed up(maybe every day) - can we stop backup and/or remove unnecessary tables? if we stop back up, is there a possiblilty of anythinng that can be broken?
September 9, 2011 at 8:00 am
errrm.... are you serious :ermm:
Adam Zacks-------------------------------------------Be Nice, Or Leave
September 9, 2011 at 9:15 am
If it is a copy of production on a dev server, you will not "break" anything by stopping backups. Stopping backups means you cannot recover it if you need to, and would need to reload it from production.
Removing "unneccesary" tables will not "break" anything either, but removing neccesary tables probably will. How is the Dev copy being used ? Do you want to remove production data from the dev copy ? Better to leave the tables in place, but remove or alter the data.
What are you trying to accomplish ?
September 9, 2011 at 12:54 pm
If you are asking if you can stop taking backups of the database once it is on the DEV server, of course. However, I would highly recommend you either continue to perform Transaction Log backups OR set the database recovery to Simple.
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
September 10, 2011 at 9:16 am
Daily Backup is already taken of dev server but as it is 200GB, it occupies a lot space so I was wondering if we stop it , what will be the impact and will it break anything?
September 10, 2011 at 6:46 pm
meghna.bhargav (9/10/2011)
Daily Backup is already taken of dev server but as it is 200GB, it occupies a lot space so I was wondering if we stop it , what will be the impact and will it break anything?
No - it won't break anything. However, if you do this you will be back here within a couple of months asking how to recover all of your changes because you had a server crash, or SAN crash, or some other disaster that caused you to lose your database.
If there is development work being done on that database, you definitely want to be backing it up so your developers will not lose all of their work.
If the database is restored on a regular schedule from production, and your developers have a solid source/change control process in place - then maybe you could get away with it.
Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.
How to post questions to get better answers faster
Managing Transaction Logs
September 10, 2011 at 7:49 pm
You could take a full backup once a week, and a differential daily, and then possibly transaction logs, depending on activity and the importance of the dev data.
September 10, 2011 at 8:38 pm
One other option is to use SSIS on a daily base, that way you can select the tables to copy from PROD to DEV.
September 12, 2011 at 11:50 pm
homebrew01 (9/10/2011)
You could take a full backup once a week, and a differential daily, and then possibly transaction logs, depending on activity and the importance of the dev data.
Nice suggestion. Some nice softwares probably can help you do this job smoothly, like acronis or easeus.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply