The Why’s and How’s of Providing Disaster Recovery, High Availability and Backup Within a VNA

Disaster Recovery, High Availability and Backup Within a VNA

The requirement for disaster recovery and backup has always been good practice. Now, with the U.S. Federal HIPAA regulations they are no longer an option but a requirement. Disaster recovery and high availability are two separate requirements, although they both achieve the same result: Providing storage and retrieval of the information reliably, independent of hardware and software failures or disasters.

Disasters are typically caused by external circumstances, and might include lightning, floods, extreme weather, or even terrorist actions. Something that is often overlooked is the physical location of the devices. For example, some devices are located in the basement of a facility, an area that is prone to flooding.

High availability is typically used to identify the recovery from hardware and software failures. To provide high level availability, there are several approaches. One can write information to two identical archives, also called a mirrored approach. But, mirroring the data is not sufficient. There also needs to be a backup strategy. The reason for this is that the database could become corrupted through malicious software, a manufacturer software upgrade, or maintenance.

For more information about developing a Vendor Neutral Architecture, the VNA Institute of Technology, or to enroll for CPHIMS (CE) Continuing Education Hours, visit information about TeraMedica, visit:


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: