Disaster Recovery, High Availability and Backup Within a VNA
There are other requirements like Disaster Recovery, High Availability and Backup that might be part of a VNA. However, by themselves they do not create a true VNA. This description introduces you to these requirements and provides an in-depth look at what constitutes each one.
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 http://www.vnait.org.For information about TeraMedica, visit: http://www.teramedica.com