Catastrophic Loss of Server - Revision history

Mvanbeek at 18:46, 6 December 2009

2009-12-06T18:46:17Z

← Older revision		Revision as of 18:46, 6 December 2009
Line 6:		Line 6:

	At a point in the future we would replace the spare hardware with a new server. This would be scheduled and normally takes the same amount of time as our normal end-of-life server replacement, i.e two sets of 30 minutes downtime, a minimum of 2hrs apart (depending on the amount of data to transfer).		At a point in the future we would replace the spare hardware with a new server. This would be scheduled and normally takes the same amount of time as our normal end-of-life server replacement, i.e two sets of 30 minutes downtime, a minimum of 2hrs apart (depending on the amount of data to transfer).

			[[Category: Business Continuity]]

Mvanbeek at 18:23, 6 December 2009

2009-12-06T18:23:22Z

← Older revision		Revision as of 18:23, 6 December 2009
Line 5:		Line 5:
	There will be a point in the future where we could download the data to the server while we are transporting it, but mobile data technology is not robust enough yet for us to be able to make any guarantees.		There will be a point in the future where we could download the data to the server while we are transporting it, but mobile data technology is not robust enough yet for us to be able to make any guarantees.

	At ~~some~~ point we would replace the spare hardware with a new server. This would be scheduled and normally takes the same amount of time as our normal end-of-life server replacement, e.g two sets of 30 minutes, a minimum of 2hrs apart (~~depends~~ on the amount of data to transfer).		At a point in the future we would replace the spare hardware with a new server. This would be scheduled and normally takes the same amount of time as our normal end-of-life server replacement, i.e two sets of 30 minutes downtime, a minimum of 2hrs apart (depending on the amount of data to transfer).

Mvanbeek: Created page with 'In the event of complete server destruction, we would take one of our spare servers (we always have spare servers available in our office), and load it up with your network's con...'

2009-12-06T18:22:17Z

Created page with 'In the event of complete server destruction, we would take one of our spare servers (we always have spare servers available in our office), and load it up with your network's con...'

New page

In the event of complete server destruction, we would take one of our spare servers (we always have spare servers available in our office), and load it up with your network's configuration. To do this takes about 1hr from when we get to the office. After that there are two choices. We can transport the server to a new location, and then download the data, or we can download the data in our office, and then move the server. We can also provide a temporary home for the server at our office at no extra charge.

The reason for moving the server before downloading the backup data is because that way you can get your office back up are running as quickly as possible, and as we can prioritise the data recovery process, we can give you access to whatever you need first.

There will be a point in the future where we could download the data to the server while we are transporting it, but mobile data technology is not robust enough yet for us to be able to make any guarantees.

At some point we would replace the spare hardware with a new server. This would be scheduled and normally takes the same amount of time as our normal end-of-life server replacement, e.g two sets of 30 minutes, a minimum of 2hrs apart (depends on the amount of data to transfer).