Skip to content

Latest commit

 

History

History
46 lines (35 loc) · 2.4 KB

scpivs44_back_up_resource_groups_on_demand.adoc

File metadata and controls

46 lines (35 loc) · 2.4 KB
Raw
sidebar permalink keywords summary
sidebar
scpivs44_back_up_resource_groups_on_demand.html
Backup operations are performed on all the resources defined in a resource group. If a resource group has a policy attached and a schedule configured, then backups occur automatically according to the schedule.

Back up resource groups on demand

Backup operations are performed on all the resources defined in a resource group. If a resource group has a policy attached and a schedule configured, then backups occur automatically according to the schedule.

Before you begin

You must have created a resource group with a policy attached.

Important
 Do not start an on-demand backup job when a job to back up the SnapCenter Plug-in for VMware vSphere MySQL database is already running. Use the maintenance console to see the configured backup schedule for the MySQL database.
About this task

In earlier releases of Virtual Storage Console (VSC), you could perform an on-demand backup without having a backup job configured for a VM or datastore. However, for the SnapCenter Plug-in for VMware vSphere, VMs and datastores must be in a resource group before you can perform backups.

Steps

  1. In the left navigator pane of the SCV plug-in, click Resource Groups, then select a resource group, and then select Play icon Run Now to start the backup.

  2. If the resource group has multiple policies configured, then in the Backup Now dialog box, select the policy you want to use for this backup operation.

  3. Click OK to start the backup.

  4. Optional: Monitor the operation progress by clicking Recent Tasks at the bottom of the window or on the dashboard Job Monitor for more details.
    .Result

If the quiesce operation fails for any of the VMs in the backup, then the backup completes with a warning and is marked as not VM consistent even if the selected policy has VM consistency selected. In this case, it is possible that some of the VMs were successfully quiesced. In the job monitor, the failed VM details will show the quiesce as failed.