Unsolved

This post is more than 5 years old

34 Posts

4679

October 21st, 2014 08:00

Cannot add a VM to a protection policy

Whenever I attempt to add a particular VM to one of my protection policies I get an error that says the policy was saved, but one or more VMs could not be added.  The only thing interesting about this particular VM that I'm aware of is that it is the VCenter host.  Should that make a difference?

Networker 8.1.1.2 on Windows 2012

EBR 1.0.1.9

Vsphere 5.1

32 Posts

October 22nd, 2014 07:00

Hello Patrick,

What is the exact error message that you receive after adding the VM? Also is the EMC Backup & Recovery (EBR) Virtual Backup Appliance displayed in the vSphere Web client?

34 Posts

October 22nd, 2014 08:00

After selecting the VM and click OK, I get a popup which says:

Backup policy was edited successfully, but failed to add one or more clients to the job.  Please check the log viewer under the configuration tab for specific details

When I look at the log viewer, it has two spectacularly useless entries

10/22/2014 11:24:30 AM: The backup job named "VM DR Backups" was edited and saved successfully.

10/22/2014 11:24:28 AM: Unable to add client named "myclient" to the EBR appliance while creating/editing backup job named "VM DR Backups". (Full client path: /path/to/myclient)

I've rummaged through the nsr directory but haven't found anything useful in those logs.  I have several clients on this ESXi server backing up fine using this policy.  I'm also unable to add it to any other policy.

Edit to add... Yes, the VBA appears in the web client.

2 Intern

 • 

217 Posts

October 23rd, 2014 02:00

Hi Patrick,

First, if the Vm is your vcenter, it's maybe not a good idea to save it through VBA (or VADP) solution. During the remove of your Vmware snapshot, every other VBA Backup will freeze or failed. That's not occured if you are saving your vcenter with an agent. At least, that's what we have experienced.

For your Vm try that removing completely Vm from Appliance before to add it again:

In your Appliance (console):

  • Find details of client(name, domain):

    mccli client show --recursive=true | grep client-name


      Example: To find a client with name win2kx8 :  mccli client show --recursive=true | grep win2kx8
      0,23000,CLI command completed successfully.
      Client                   Domain                                  Client Type
      ------------------------ --------------------------------------- ------------------------------------
      win2kx8       /vcenter.abc.local/VirtualMachines Virtual Machine

  • mccli client retire --name=/vcenter.abc.local/VirtualMachines/win2kx8
    0,22512,Client was retired.

How to add restored VM to backup policy?

Hope it will help you

Greg


34 Posts

October 24th, 2014 06:00

I've installed an agent on the box.  Since the command you gave listed it as vcenter, rather than a virtual machine, it clearly sees it as different and I don't want to retire it for fear of screwing up the others.

2 Intern

 • 

217 Posts

October 25th, 2014 00:00

Hi,

I guess backing up the vCenter in a traditional way (Agent) is the best way to save it.

Greg

0 events found

No Events found!

Top