Copyright © Acronis, Inc., 2000-2009 135You can run any of these backup tasks by selecting it from the list of tasks in the Backup plans andtasks section in the left pane.If you have also specified the retention rules in your backup scheme, the scheme will result in fourtasks: three backup tasks and one cleanup task.6.2.10. Archive validationSet up the validation task to check if the backed up data is recoverable. If the backup could not passthe validation successfully, the validation task fails and the backup plan gets the Error status.To set up validation, specify the following parameters1. When to validate – select when to perform the validation. As the validation is a resource-intensive operation, it makes sense to schedule the validation to the managed machine's off-peakperiod. On the other hand, if the validation is a major part of your data protection strategy andyou prefer to be immediately informed whether the backed up data is not corrupted and can besuccessfully recovered, think of starting the validation right after backup creation.2. What to validate – select either to validate the entire archive or the latest backup in the archive.Validation of a file backup imitates recovery of all files from the backup to a dummy destination.Validation of a volume backup calculates a checksum for every data block saved in the backup.Validation of the archive will validate all the archive’s backups and may take a long time and a lotof system resources.3. Validation schedule (appears only if you have selected the on schedule in step 1) - set theschedule of validation. For more information see the Scheduling (p. 87) section.6.2.11. Setting up regular conversion to a virtual machineWhen creating a backup plan (p. 117), you can set up regular conversion of a disk or volume backupto a virtual machine. This section provides information that helps you make the appropriate settings.6.2.11.1. Setting up a conversion scheduleA disk backup (p. 214) created while executing a backup plan can be converted to a virtual machineimmediately or on schedule or you can combine both methods.The conversion task will be created on the machine being backed up, and will use this machine's dateand time.As a result of the first conversion, a new virtual machine will be created. Every subsequent conversionwill re-create this machine from scratch. First, a new (temporary) virtual machine is created. If thisoperation succeeds, the old machine is replaced. If an error occurs during creation of the temporarymachine, the temporary machine is deleted. This way, the task always ends up with the singlemachine, but extra storage space is required during conversion to keep the temporary machine.The old virtual machine must be powered off by the time of conversion, otherwise it will not bepossible to delete it and the conversion task will fail. If this happens, you can restart the conversiontask manually after powering off the machine. Any changes made to the machine while it waspowered on, will be overwritten.
