Hey William,
I'm sort of ok with the scenario as it is - problem we had with the AC issue over the weekend was that the environment was down for 3 days (we could have done a migration to another server in that period of time and gotten it up and running earlier had we had everything in place - the snapshot being the biggest problem). Anyways, we've studied the procedures from MS on MSDN and will be implementing all of those maintenance tasks around the backups (we don't handle the backups or restores though). What I'm looking for at this point is really a config file of sorts that'll help with getting a new instance up and running fast - tfs must use something, but I'm suspecting that it's registry locked, though I'm not sure. Brian Madsen Microsoft MVP Visual Developer ASP.Net Senior Application Specialist Fujitsu Australia Limited 410 Murray Street, Perth, WA 6000, Australia [email protected] <mailto:[email protected]> +61 08 9268 1586 +61 0433 814 756 au.fujitsu.com <http://au.fujitsu.com> ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of William Bartholomew Sent: Thursday, 26 February 2009 7:36 AM To: [email protected] Subject: Re: Backing up TFS instance Hi Brian, Our backup strategy is basically: * Weekly snapshots of the virtual machine * Nightly full database backups (stored on NAS) * Hourly transaction log backups (stored on NAS) The NAS is then backed up nightly and taken off site. Your strategy does sound reasonable as long as you're comfortable with your backups not being hardware agnostic. Regards, William On Thu, Feb 26, 2009 at 8:30 AM, Madsen, Brian < [email protected]> wrote: Hey Guys, We just had a bit of scare this week, which saw our data centre (at my client) shut down due to a massive failure in the aircon. All servers (well, production level ones) has been migrated to another site/location but dev boxes and environments will be left (for the time being) in the old data centre. This has naturally brought some concern to us as we don't just rely on the database to be backeup but also the instances of the our TFS environment. We run a multi-server setup for our TFS and we did have the following set up: 1) virtual image snapshot of all servers done (not incrementally done, but one off) 2) databases backed up Naturally I would like to find a way to back up/restore the TFS server as well. We do have, as mentioned, a virtual image snapshot of the server but would like to know if there's a better way to do this (the snapshot isn't hardware agnostic so we'd have to rely on same hardware - next version of our back up software, for the virtual snapshots will be hardware agnostic). Preferably it'd be nice it we could somehow back up TFS's configuration files (so the configuration aspect is at least taken care of) - the install of TFS itself isn't a concern at this point. Any great ideas on how to back up our whole TFS environment as well for a rapid recovery (time == $$$)? Brian Madsen Microsoft MVP Visual Developer ASP.Net Senior Application Specialist Fujitsu Australia Limited 410 Murray Street, Perth, WA 6000, Australia [email protected] <mailto:[email protected]> +61 08 9268 1586 +61 0433 814 756 au.fujitsu.com <http://au.fujitsu.com/> This is an email from Fujitsu Australia Limited, ABN 19 001 011 427. It is confidential to the ordinary user of the email address to which it was addressed and may contain copyright and/or legally privileged information. No one else may read, print, store, copy or forward all or any of it or its attachments. If you receive this email in error, please return to sender. Thank you. If you do not wish to receive commercial email messages from Fujitsu Australia Limited, please email [email protected] ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] <mailto:[email protected]> Subscribe: [email protected] <mailto:[email protected]> Unsubscribe: [email protected] <mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs <http://www.codify.com/lists/oztfs> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] <mailto:[email protected]> Subscribe: [email protected] <mailto:[email protected]> Unsubscribe: [email protected] <mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs <http://www.codify.com/lists/oztfs> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> -------------------------------------------------------------------------------- Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists
<<image001.gif>>
