Backing up Hyper-V with CloudBerry
For this article; we’ll be outlining how easy it is when backing up Hyper-V with CloudBerry. When backing up Hyper-V; there are a few basic settings and configuration steps to make the task a lot easier.
Creating a Backup Plan for Hyper-V
The process for creating a backup plan that protects your Hyper-V guest machines is a fairly simple process.
1. Launch the Hyper-V Backup Plan Wizard by clicking on Hyper-V on the navigation toolbar:
2. Select the type of backup destination to associate with the backup plan. There are two options:
Local or Cloud Backup
This selection allows for the backup to be written directly to either local media; or a cloud storage account.
Using this option means that the backup will be backed up to two separate destinations – a local device (NAS or hard drive) and cloud storage – during the one backup run.
3. Select the backup storage destination that will be used to store the backups.
NOTE: If you selected Hybrid Backup in step 2; you’ll be asked to provide the Local Backup Storage first and then the secondary/cloud storage second.
4. Name the backup plan to something that is easy to identify.
We also recommend ticking ‘Save backup plan configuration to the backup storage’ so that it’s easily recovered in future.
5. Select the Hyper-V guests to back up.
There are three different options available to choose from:
Back up all Virtual Machines
This will automatically select all virtual machines located on the Hyper-V host. Any additional VM’s created in the future will automatically be selected.
Backup only running Virtual Machines
This will only back up VM’s which are switched on and are running when the backup begins.
Backup selected Virtual Machines
Allows for complete user control. Specifically choose if each individual VM is to be backed up or not within this backup plan.
6. Choose to encrypt and compress the backup files.
Compressing the backup will reduce the overall storage space required for the backup and also decrease backup times due to smaller amounts of data being transferred to the backup destination.
Backups that are encrypted are done so using AES encryption. The various key lengths determines the strength of the encryption. The longer the key length; the hard it is to break. However there is also a trade off as it’ll take longer for the backup to complete.
NOTE: Encryption passwords can’t be recovered by our team. The password is required when performing data restores and recoveries.
7. Set the Retention Policy for the backup plan.
The page of the wizard allows for the user to set the version control on the files backed up. There are two different options to choose from:
This will use the global retention policy that’s already been set. To check these settings; click on the ‘options’ link provided.
Specify custom retention policy for backup plan
Allows a user to specify the retention policy for just the current backup plan. The options available are:
Delete versions older than
Configure how old the oldest version of a file should be. Tick the option ‘Always keep the last version’ if at least one copy of the file is required regardless of how old it is.
Keep number of versions (for each file)
This outlines how many individual copies of a file should be kept at one time. When the limit is exceeded; the oldest copy will be removed regardless of when it was created.
8. Schedule when the backup plan should run.
There are three main options available to indicate when a backup plan is executed.
No schedule (run manually)
Fairly straight forward. This will mean the user will need to start the backup for it to run.
Allows a user to indicate a specific date and time when the backup plan is executed. Great for meeting data compliance requirements.
Backup plan is executed automatically on a specific schedule. Can set frequency, start time and regularity the software runs the backup plan without user intervention.
There are additional options available which are applicable to all three scheduling options above. Set a hard run time for the backup until it’s forced to stop by the software and also to execute any missed backups.
9. Schedule a Full backup.
Similar to the recurring option in step 8; a user can force a full backup to be written to the backup destination. When using block-level backups; the only time a full copy of the data is made is during the first time a backup plan is run (by default).
There is also the option to force a full backup when a percentage of the total data set is being backed up due to it having changed (50% is default).
It’s recommended to run regular full backups to ensure that older versions of files are available on storage that’s being used for block level backups.
10. Set any pre and post backup actions.
In some instances; there may be some requirement for a script to be executed before or after a backup plan. There are three options available:
User can specify where the script file is located that to be run before the backup plan begins.
There is also a radio button option to either stop the backup if the pre-backup action fails or continue regardless of the pre-backup action outcome.
User can define a script or task that occurs once the backup plan has completed.
There is also a radio button option to run the post-backup action if the backup plan was successful or execute regardless of the backup result.
If running multiple backups plans within one CloudBerry Online Backup installation; a user can choose to automatically run the next expected backup plan once the current plan has finished.
As with the pre and post backup tasks; the option to only run when current backup completed successfully or continue regardless of its result are available.
11. Configure Backup Report Notifications.
CloudBerry Online Backup is able to send backup reports to a user defined e-mail address configured in the MBS console.
To receive notifications for this backup plan; tick I want to receive notification email when backup completes and select when to receive notifications by clicking the applicable radio button:
When backup fails
A notification will only be sent when a backup plan has encountered a warning or error.
In all cases
A notification report will be emailed each time the backup plan is run.
Add entry to Windows Event Log when plan completes
CloudBerry Online Backup can write an event into the Windows Event Log to notify when a backup completes and its result. The two options available are the same as above.
This is useful for those using RMM software to monitor and provide alerts when specific events on the system occur.
12. A Summary of all the settings configured within the wizard is now provided.
13. The backup plan is now successfully created.
Tick run backup now to execute the backup plan straight away.
Click Finish to complete the wizard.
That’s all you need to do when backing up Hyper-V with CloudBerry (other than running the backup plan). If you have any problems with the backup plan or any further questions then take a look at our complete Hyper-V Guide and contact our technical support team.
If this article helped you with Backing up Hyper-V with CloudBerry; don’t forget to share it on social media to spread the word on how easy backing up Hyper-V with CloudBerry really is!