VMware QuickSpin backup sets allow you to back up VMware virtual machines frequently as well as restore in a matter of minutes. They cannot back up to the cloud, however, so if you want an off-site copy of the virtual machines you plan on protecting, you will need a VMware Standard backup set in addition to a VMware QuickSpin one. Intronis best practices are to put the QuickSpin backups on a different host than the one housing the virtual machines being backed up, but it is not a requirement for them to work. You should be able to run a VMware QuickSpin backup from any machine that can access and authenticate with the ESX/EXi host or vCenter machine managing the virtual machines you want to back up.
Log into the management portal and go to the computer account for which you want to add a VMware Standard backup set.
Click on the Backup tab and then hit the Add Backup Set button.
In the Create Backup Set wizard, select Virtual Machines from the left-hand side, select VMware then QuickSpin backup as the backup set type and give the backup set a name. Click Next when done.
The second page is where you add the virtual machines you want to back up to the backup set.
If those virtual machines' host is not already recognized, you will need to add the IP address of the ESX/ESXi or vCenter machine managing the virtual machines. If the software needs credentials to authenticate with the server you added, it should prompt you for them. After the host/vCenter has been added, a list of virtual machines available to be backed up should appear in a drop-down.
Select the virtual machines you want to back up and click Next.
After selecting which virtual machines to back up, choose which host the recovery virtual machine will live on (you may need to add a new server using the Add New Server... button at the bottom).
The recovery virtual machine is a clone of the original virtual machine; restoring the virtual machine involves either spinning up the clone or "rewinding" the clone and then spinning it up. You can specify exactly which resource pool, VM folder, and datastore the recovery virtual machines will use. Additionally, you can set the configuration for all recovery virtual machines at once by checking the Select all VM(s) option or, if you want to configure each recovery virtual machine individually, you can put a check next to only the virtual machine you want to change.
Hit Next to continue.
Note: When choosing where to put the recovery virtual machines, it is best practice to put them on a host different from the one the source virtual machines live on. This is to avoid a single point of failure.
On the Schedule page, you can choose to use either a recurring interval-based schedule or a calendar-based schedule. Since QuickSpin backups can usually run frequently, it is easier to use the recurring interval-based schedule to have the backup run multiple times a day.
If you use the calendar-based schedule, you can edit a scheduled backup job by double-clicking on it or by dragging the sticky note to another time or day. You can delete jobs by clicking on the sticky note and hitting the "Delete" key and can add jobs by double-clicking in empty space.
When you are done setting the schedule, click Next.
After creating the schedule, you will arrive at the Settings page. Here, you can specify how many versions of the backups you will retain.
When deciding the archiving rule, you may need to balance your client's recovery point objective (RPO) with the amount of storage you have to accommodate those incrementals. Incrementals will be stored at the location specified under Incremental version storage location.
Finally, the temp folder location is where temporary files will be kept during the backup job; for QuickSpin backups, you generally only need about 1-2 GB of free space for temporary files.
When you are finished, click Next.
At the last page, you will be given a summary of the backup set you just configured. Hit Create to finalize the backup set.
Important Note - After you run a QuickSpin backup and the recovery virtual machines are created, you must not start or alter those recovery virtual machines. Doing so may prevent subsequent backups and restores from working.