{"id":16,"date":"2014-08-27T10:54:15","date_gmt":"2014-08-27T10:54:15","guid":{"rendered":"http:\/\/sqlity.dev.lbdesign.eu\/?page_id=16"},"modified":"2014-11-09T15:13:35","modified_gmt":"2014-11-09T20:13:35","slug":"disaster-recovery","status":"publish","type":"page","link":"https:\/\/sqlity.net\/en\/services\/disaster-recovery\/","title":{"rendered":"Disaster Recovery"},"content":{"rendered":"

SQL Server Disaster Recovery Audit<\/h2>\n

\nNot Having a SQL Server Disaster Recovery Plan Can Cost You.<\/strong>\n<\/p>\n

\nMost companies have a backup process - you probably take regular backups and store them in a safe place, maybe even off site. But here\u2019s the problem. When have you last looked at your backups or even tried to restore them? If you\u2019re like most companies, you don\u2019t look at them regularly to see if they\u2019re working.\n<\/p>\n

\nAs the DBA, your job could be on the line if you\u2019re not able to recover your company\u2019s database after a disaster. There are many reasons for a backup not to work. They reach from corrupted drives to broken log chains.\n<\/p>\n

\nAfter<\/span> the production database went down is not the time to discover that you cannot restore any of your backups. It is also not the time to search through the manual to figure out how exactly the restore sequence has to be.\n<\/p>\n

\nThe only way to know that your backups are good is to restore them. The only way to be confident that you can restore your database(s) in the shortest possible time is to automate that process.\n<\/p>\n

\nCall us at 832-377-5489 or email us<\/a>\u00a0today and let\u2019s discuss your disaster recovery needs.<\/strong>\n<\/p>\n

Your SQL Server Disaster Recovery Plan<\/h2>\n

\nIt\u2019s not enough to take backups. It\u2019s not enough to have a \u201ctheory\u201d and \u201cknow\u201d how you can restore your database, if needed. You need to practice<\/em> the recovery, like every other type of disaster recovery team practices.\n<\/p>\n

\nThink about it.\n<\/p>\n

\nFirefighters don\u2019t whip out the \u201chow to fight a fire\u201d handbook when there\u2019s a fire. They practice by having fire drills. They time their movements and their coordination and make sure they know how to handle the fire truck, improve how fast they can get into their gear and practice how to safely go into a burning building. Some airports even have a full-sized airplane model to practice extinguishing airplane fires (e.g. in O\u2019Hare, Chicago you can see one during approach, depending on the airstrip you are on).\n<\/p>\n

\nThat way, when there is a real emergency they\u2019re prepared.\n<\/p>\n

\nThink \u201cit\u2019ll never happen<\/em>\u201d?\n<\/p>\n

\nThat\u2019s what the emergency personnel in Sioux City, Iowa thought when the Mayor insisted they train for a plane crash.\n<\/p>\n

\nEveryone thought \u201cit would never happen\u201d at their tiny airport, but it did just a few months later. Because they were ready, they were able to save the lives of most of the people involved in the crash. (See United Flight 232 Lecture by Capt. Al Haynes<\/a> starting at minute 21.)\n<\/p>\n

\nBut this page is not about burning buildings or crashing planes, it is about data - your data.<\/p>\n

Your Business is at Stake<\/h2>\n

What will happen to your business if you lose all your data, or even only the last two days' worth of data? What happens if you can recover, but it takes a week?\n<\/p>\n

\nAre you prepared? Do you have a SQL Server disaster recovery plan<\/strong> in place? Remember, without your data, your business is at stake.\n<\/p>\n

Here are Two Important Objectives for Your Backups:<\/h2>\n