Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Backups in a testing environment


Backups in a testing environment

Author
Message
wosabi
wosabi
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 457
Hi,

Does anyone perform backups in their testing environments? We do, not for recovery purposes, but more to emulate our production environment as much as possible. I have exactly the same maintenance plans setup in the test environment as the production environment.

I had been discussing this with my DBA colleague and he suggested getting rid of our backups in the test environment altogether as it just causes more work and does not provide any benefit. However my argument against this was that it was creating one more point of difference between our test and production environment. I admit although config wise the two environments are identical, their hardware is not, with test being on a VM and production on Physical.

I was wondering if anybody else was (or wasn't) doing this? I know where he is coming from, but at the same time it feels wrong!

Any thoughts?

Regards,

Warren.
Satnam Singh
Satnam Singh
Old Hand
Old Hand (300 reputation)Old Hand (300 reputation)Old Hand (300 reputation)Old Hand (300 reputation)Old Hand (300 reputation)Old Hand (300 reputation)Old Hand (300 reputation)Old Hand (300 reputation)

Group: General Forum Members
Points: 300 Visits: 1084
Backing up a test environment is always good. What u can do is that perform a full backup on a daily basis and dont take copies of those on tape or some other location. Test environment backups can be kept on the test server iself and the retention period can be specified as a day or two.

Cheers,
Satnam
RP_DBA
RP_DBA
Right there with Babe
Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)

Group: General Forum Members
Points: 767 Visits: 1068
We back up and copy our beta environment to a local NAS. If there are problems, it's quicker to recover this way than pulling down a prod copy from the remote hosting site and applying DDL/DML changes.

_____________________________________________________________________
- Nate

@nate_hughes
John Mitchell-245523
John Mitchell-245523
SSCertifiable
SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)

Group: General Forum Members
Points: 7422 Visits: 15114
Warren

My view is that you should back up everything (within reason) and then it's there if you need it. Just because you can't think of a reason why a backup of a particular database might be needed, it doesn't mean there isn't one.

Your point about making test environments as close as possible to live is not one I'd considered before in the context of backups, but it's a good one. I shall use it when arguing for backups of test in my office!

John
Meet George Jetson
Meet George Jetson
SSCrazy
SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)

Group: General Forum Members
Points: 2635 Visits: 1393
We perform a Full Backup weekly and a Differential Backup nightly on our Development AND QA SQL Servers. Partially as a way to mimic the Production environment, partially to allow for recovery should a particular task/job/modification/etc. is a simple issue that a restore would save time with.

Chris Powell

George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search