﻿<?xml version="1.0" encoding="utf-8"?><rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="2.0"><channel><title>SQLServerCentral.com Content tagged Backup and Recovery, Administering, Availability</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Backup and Recovery, Administering, Availability posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Another Disaster (Almost)</title><description>Andy had a semi-disaster similar to the one he wrote about last year. Interesting to see the kinds of problems that happen to other people. This article raises some interesting points that are outside the scope of basic disaster recovery, looking at how/when to move databases to a different server and how to reduce the server load dynamically.
</description><guid>http://www.sqlservercentral.com/articles/Administering/anotherdisasteralmost/881/</guid><pubDate>2003/01/14</pubDate><link>http://www.sqlservercentral.com/articles/Administering/anotherdisasteralmost/881/</link></item><item><title>Disaster In The Real World - #2</title><description>Back in April Steve Jones wrote up a disaster at work. Andy had one this week and wrote up the story too. Copy cat! Pretty soon everyone will be having a disaster and writing a story about it! Give these guys credit for letting you see what happens when it ALL goes bad. Disaster recovery is hard to sell and hard to do, reading the article might give you an idea that will save you some time and/or data one day.
</description><guid>http://www.sqlservercentral.com/articles/Administering/disasterintherealworld2/747/</guid><pubDate>2002/07/31</pubDate><link>http://www.sqlservercentral.com/articles/Administering/disasterintherealworld2/747/</link></item></channel></rss>