vCloud v 5.1 comes with two types of storage profiles: including backup and without backup
Storage profile including backup
Choosing this storage profile means that you choose the vCloud backup provided by Cloudmore. Cloudmore performs daily backups of Customer data and the backup copy retention time is thirty (30) days.
NOTE! The backup provided by Cloudmore is not application aware and it is crash-consistent*! Cloudmore can restore the Customer data from the most recent successful backup for a fee according to the provided price list. Cloudmore is not responsible for data loss resulting from the failure or loss of backup media.
Storage profile without backup
Choosing this storage profile means that you take responsibility for backing your Customer data. Cloudmore recommends that vCloud servers are routinely backed up by a 3rd party service such as the Cloudmore LiveVault Server backup service.
Check the Cloudmore price list to get the latest LiveVault price information.
NOTE! The LiveVault service requires you to be LiveVault certified in order to be able to use and re-sell the service. Still not LiveVault certified? Go to the LiveVault certification video.
*Non-application aware backup - the main reason why we use backup is in order to be able to restore our data when needed. A non-application aware backup is also called an application inconsistent backup. So, if a backup starts and if any file is changed after it was backed up but before the job completed then the result is an inconsistent backup. Simply it means that there might occur a mismatch in the files contained in the backup job. Usually this kind of backup is acceptable for simple file servers and data that rarely change.
Crash-consistent backup up - the most important to know about this kind of backup is that all data is captured in one and the same time and the data is restored at its entirety. This type of backup is mainly used for disaster recovery and not for file-level backup and recovery. So, if a file has been deleted and you would like to to restore this file only, then you should proceed with a restore of the whole server image.