Backup of Wavestore
What's the best way to take a backup of a Wavestore Server? This depends on your requirements.
We can backup various items:
- There's little point in backing up the Wavestore system files, as they can be easily and quickly reinstalled. See wavestore.com/support/downloads for copies of the install files.
- The configuration file can be backed up using Setup > Configuration Editor > Save To File. You can save it to a file on another machine. This is recommended after installation or major upgrade, as a reinstall or replacement might be needed in case of hardware failure.
- If necessary, annotations can be backed up as well.
- Video footage is huge, and you'll need another Wavestore-sized machine to back it all up. It's so big that to back up 30 days' storage can take up to 30 days. If you need a spare copy of the video data, it's worth writing it at the same time as the main copy so it's always up to date.
So we need to consider carefully what backups are needed.
There are a variety of ways of backing up video footage:
- Use a RAID array on the local machine, thus ensuring a single disk failure does not cause all data to be lost. On a system with, say, 20 disks, a single redundant disk (N+1) will add only 5% to the storage cost. To cope with more than one disk failure, use two or three redundant disks (N+2 or N+3). Note that N+1 redundancy is sometimes known as RAID5, and N+2 is known as RAID6. There's no common name for N+3 or more. If the entire Wavestore Server fails, the video disks can be moved to another Wavestore Server and the footage will be accessible.
- To cope with a whole Wavestore Server failing, consider a failover group with a standby server. This does not provide backup of the video footage, merely a temporary place to record to when the main server is down, until the main server is up again.
If you really need to have an external backup of the video footage, there are possibilities:
- Continuous backup to another location can be achieved using the "Disk2" configuration option. Write the main copy to an internal disk, and also write another copy to an external iSCSI disk. It's possible to have a smaller external disk: for example, the external iSCSI (Disk E) might store only 7 days backup whereas the main disks (Disk D) might store 30 days footage. Generally external iSCSI disks are less reliable than internal disks (there's more to go wrong), so internal disks are recommended, but as an external backup iSCSI is a possibility.
- Continuous backup can also be achieved by restreaming video channels to another Wavestore Server. This allows much more flexibility, as we can configure only certain channels to restream, and we can record with different parameters if desired (for example, less storage might be available on the second server). This method can be combined with Failover if only two servers are configured (one main server and one standby/backup) in the Failover Group where the Standby server acts as Backup server until it needs to take over.
- The CopyTrack command can be used to copy video footage between Wavestore Servers for backup. This can be slow, but it can be triggered on event. It has been used to backup footage from stadiums after football matches, and proposed to back up footage from a bus when it enters the depot.
And of course:
- One-off copies, for example to send to the legal team after an incident, can be exported using the WaveView Export facility.
In summary: your backup policy will depend on your requirements and budget, but the Wavestore Server offers a variety of features to meet your requirements.