Re: [ADSM-L] digging deeper with VE tagging support possible?
2017-03-15 10:44:37
Hi Stefan,
There is nothing obvious here except that you mention 'dsm.opt'. Not sure
if this is just a general name for the opt file but the datamover opt file
generally includes the datamover name. Is it possible that the dsm.opt
file that you changed is not the one being used by the datamover and
therefore may not have the vmtagdatamover option?
Del
----------------------------------------------------
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 03/15/2017
09:39:34 AM:
> From: Stefan Folkerts <stefan.folkerts AT GMAIL DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 03/15/2017 09:40 AM
> Subject: digging deeper with VE tagging support possible?
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Hi all,
>
> I'm having some issues running 8.1.0.1 and VMware tagging support.
> I keep getting the message "ANS9377E No virtual machine is specified on
the
> Back VM command or the virtual machine domain list could not be
processed"
>
> dsm.opt has "vmtagdatamover yes" set and can log into vCenter and see
all
> the VM's
> I can select the datamover and compatible schedule in vCenter webclient
> I attached the schedule to a folder that contains a VM that is not
excluded
> from this backup.
>
> I backup using the schedule created via the OC (attached to datamover)
> and a .cmd script on the datamover:
>
> dsmc backup vm -domain.vmfull="Schedule-Tag" -vmbackuptype=FULLVM
> -asnodename=<DCNODE> -MODE=IFINCR
>
> I can't get it to work and there is no log information that will help
me,
> has anybody seen this before?
>
> Thanks.
>
|
|
|