Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Backups in a testing environment Expand / Collapse
Author
Message
Posted Tuesday, January 18, 2011 11:18 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, August 10, 2014 6:32 PM
Points: 1, Visits: 389
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.
Post #1049811
Posted Tuesday, January 18, 2011 11:43 PM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, January 6, 2014 1:47 AM
Points: 292, Visits: 1,084
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
Post #1049814
Posted Wednesday, January 19, 2011 7:47 AM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Wednesday, May 14, 2014 7:13 AM
Points: 620, Visits: 864
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
Post #1050070
Posted Wednesday, January 19, 2011 8:01 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 9:25 AM
Points: 5,306, Visits: 9,686
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
Post #1050082
Posted Wednesday, January 19, 2011 10:46 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, August 11, 2014 7:00 AM
Points: 1,744, Visits: 1,323
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.
Post #1050211
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse