Disaster Recovery and Backup Planning

Disaster recovery is all-too-often ignored and then all of a sudden the lights go out and it's too late. Is your Disaster Recovery Plan sufficient to ensure your organization's interests are protected? Would your valuable data be protected in the case of a fire, tornado, mechanical/system failure or the loss of data access from human error? A workable disaster recovery plan that minimizes data loss and downtime is essential to ensure the long-term survival of your business. We can help you prepare a disaster recovery plan to fit your budget that in the event of a disaster, you can get your business up and running quickly.

	Backup plans onsite and offsite -- Where is the plan located? Who has access to your confidential plan? Are your backup tapes stored on-site or off-site?
	Recovery Plan Development -- The actual steps to take and who to contact in the event of a disaster. We can help you build the plan and test it out.
	Database Maintenance Plans -- Are your databases and transaction logs regularly backed up and are the indexes properly maintained to prevent slow queries? Many of these routine tasks can be automated into a Maintenance Plan and schedule to periodically run.
	Database Mirroring -- Maintains a hot standby database (known as the mirror database) that can quickly assume client connections in the event of a principal database outage. Database mirroring involves two copies of a single database that reside on different computers and works by transferring and applying a stream of database log records from the principal database to the other copy of the database.
	Replication -- Copies and distributes data and database objects from one database to another and then synchronizing between databases to maintain consistency. Using replication, you can distribute data to different locations and to remote or mobile users over local and wide area networks, dial-up connections, wireless connections, and the Internet.
	Log Shipping -- Sends transaction logs from one database (the primary database) to another (the secondary database) on a constant basis. Continually backing up the transaction logs from a primary database and then copying and restoring them to a secondary database keeps the secondary database nearly synchronized with the primary database. This is similar to Database Mirroring but the data can be out of sync for a longer period.
	Failover Clustering -- Uses up to four computers to cover for each other if one crashes.