VDP Backup Failed with error: cancelled by Administrator

Sometimes VDP backups failed with an error “Command cancelled by an user” or “Cancelled by Administrator”.

This issue occurs when a non-initial backup does not complete within the backup window.

Follow below steps to enable overtime option for the backups:

    1. Connect to the VDP Appliance using SSH.
    2. Find the Client name and full path by running this command:mccli client show –recursive

      For example:

      mccli client show –recursive

    3. List the Client details by running this command:mccli client show –name=domain_from_step_a/client_name_from_step_a

      You see output similar to:

      Overtime Option No overtime allowed

      For example:

      mccli client show –name=/vc.vmware.com/VirtualMachines/Win2K8

      0,23000,CLI command completed successfully.

      Attribute Value
      ———————— ————————————————————————-
      Client Name Win2K8
      Fully Qualified Name /vc.vmware.com/VirtualMachines/Win2K8_UDU9nLWL6BgGQaBh3Jeegg
      Client Type Virtual Machine
      Operating System windows7Server64Guest
      Paging No
      CID 86926f70dae8d1cbf8f062e32a87fc8b70a2cfcd
      CID Assigned <YYYY-MM-DD>T<TIME> PST
      Disabled No
      Agent Last Started <YYYY-MM-DD>T<TIME> PST
      Override Group Retention No
      Retention Policy Default Retention
      Overtime Option No overtime allowed
      <snip>

      Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

    4. Modify the overtime-optionto NEXT_SUCCESS by running this command:mccli client edit –overtime-option=NEXT_SUCCESS –name=domain_from_step_a/client_name_from_step_a

      For example:

      mccli client edit –overtime-option=NEXT_SUCCESS –name=/vc.vmware.com/VirtualMachines/Win2K8

      0,22211,Client was updated.

      Note: The overtime option is automatically set back to No overtime allowed after the first successful backup because subsequent backups are expected to be quicker.

      To always allow overtime, which is not recommended, use the following option: –overtime-option=ALWAYS

      To disable overtime, manually modify the preceding option with: –overtime-option=NEVER

    5. Verify the changes by running this command:mccli client show –name=domain_from_step_a/client_name_from_step_a

      You see output:

      Overtime Option Overtime until successful backup

      For example:

      mccli client show –name=/vc.vmware.com/VirtualMachines/Win2K8

      0,23000,CLI command completed successfully.
      Attribute Value
      ———————— ————————————————————————-
      Client Name Win2K8
      Fully Qualified Name /vc.vmware.com/VirtualMachines/Win2K8_UDU9nLWL6BgGQaBh3Jeegg
      Client Type Virtual Machine
      Operating System windows7Server64Guest
      Paging No
      CID 86926f70dae8d1cbf8f062e32a87fc8b70a2cfcd
      CID Assigned <YYYY-MM-DD>T<TIME> PST
      Disabled No
      Agent Last Started <YYYY-MM-DD>T<TIME> PST
      Override Group Retention No
      Retention Policy Default Retention
      Overtime Option Overtime until successful backup
      <snip>

      Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

      Note: To revert the –overtime-optionto default, run the command from step c. and replace –overtime-option=ALWAYS by –overtime-option=NEVER

  1. If the backup job is scheduled to run daily, modify the job to run on a weekly basis to prevent the job from starting and queued the next day:
    1. In the VMware vSphere Data Protection plug-in in the vSphere Web Client, click the Backup
    2. Select the backup job for the client.
    3. Click Backup job actionsEdit.
    4. In step 2, change the Backup schedule from Dailyto Weekly performed every and select the day you want the job to run.
    5. Leave the default parameters on the next steps and click Finish.
Advertisements

Tagged: , , , , ,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s

%d bloggers like this: