ADSM-L

Re: [ADSM-L] ANS4174E error

2015-03-05 11:49:37
Subject: Re: [ADSM-L] ANS4174E error
From: "Prather, Wanda" <Wanda.Prather AT ICFI DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 5 Mar 2015 16:48:15 +0000
Well, your Q CO shows that you have a management class VMDATA, and it has a 
valid backup copy group.
That makes me wonder if it's the domain that's incorrect?

When you run a backup with VE, you specify -ASNODE=dcenternode 
-optfile=optfilecontainingVMMC
If you do Q NODE dcenternode, does it show DOMAIN=VM_ACC?

Or if it's your dsmcad that still won't start,
that dsmcad points to a dsm.opt file
In that dsm.opt file there is a NODENAME
If you do Q NODE NODENAME, does it show DOMAIN=VM_ACC?



Wanda Prather
TSM Consultant
ICF International Enterprise and Cybersecurity Systems Division





-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
McWilliams, Eric
Sent: Thursday, March 05, 2015 10:53 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] ANS4174E error

Thanks.  I set it up close to yours.  Just tweaked some names for my 
environment.  However, when I try to run a backup I get this error message:

03/05/2015 09:37:53 ANS9388E The management class 'VMDATA' specified for the 
'VMMC' option is invalid, or does not have a backup copy group.

I know my management class is valid and it does have a backup copy group.

EAGLEROCK> q co vm_acc f=d

                 Policy Domain Name: VM_ACC
                    Policy Set Name: ACTIVE
                    Mgmt Class Name: VMCTL
                    Copy Group Name: STANDARD
                    Copy Group Type: Backup
               Versions Data Exists: 3
              Versions Data Deleted: 1
              Retain Extra Versions: 30
                Retain Only Version: 60
                          Copy Mode: Modified
                 Copy Serialization: Shared Static
                     Copy Frequency: 0
                   Copy Destination: VMCTLPOOL Table of Contents (TOC) 
Destination: 
     Last Update by (administrator): EMCWILLIAMS
              Last Update Date/Time: 2015-03-05, 09:18:16
                   Managing profile: 
                    Changes Pending: No

                 Policy Domain Name: VM_ACC
                    Policy Set Name: ACTIVE
                    Mgmt Class Name: VMDATA
                    Copy Group Name: STANDARD
                    Copy Group Type: Backup
               Versions Data Exists: 3
              Versions Data Deleted: 1
              Retain Extra Versions: 30
                Retain Only Version: 60
                          Copy Mode: Modified
                 Copy Serialization: Shared Static
                     Copy Frequency: 0
                   Copy Destination: BACKUPPOOL Table of Contents (TOC) 
Destination: 
     Last Update by (administrator): EMCWILLIAMS
              Last Update Date/Time: 2015-03-05, 09:19:04
                   Managing profile: 
                    Changes Pending: No


These are the options in my dsm.opt file:
VMMC                    VMDATA
VMCTLMC         VMCTL

Does anything jump out at you as being wrong?

Thanks for all your help.

Eric McWilliams
www.medsynergies.com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Rick Saylor
Sent: Thursday, March 05, 2015 9:04 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] ANS4174E error

Eric,

Yes, the data goes to the VMPOOL_DATA and the VM control information is sent to 
the VMPOOL_CTL pool(see below). Both management classes, VMDATA and VMCTL, fall 
under the same policy with VMDATA being the default class.

tsm: ADSM>q stg vm*

Storage         Device          Estimated       Pct       Pct
High     Low     Next Stora-
Pool Name       Class
Name       Capacity      Util      Migr      Mig     Mig     ge Pool
                                                                    Pct     Pct
-----------     ----------     ----------     -----     -----
----     ---     -----------
VMPOOL_CTL      DISK                200 G       0.9       0.9      100      99
VMPOOL_DATA     DISK              1,024
G      19.3      19.3       70       0     3584POOL6


Thanks,
Rick

At 08:41 AM 3/5/2015, McWilliams, Eric wrote:
>Rick,
>
>I did activate the policy set.  It appears I'm doing something else 
>wrong because the CAD won't even start after I put the VMMC and VMCTLMC 
>options in the dsm.opt file.
>
>I noticed on your copy destinations you have a VMPOOL_CTL and
>VMPOOL_DATA.   Is the VMPOOL_DATA where you are copying the actual VM backups?
>
>Thanks
>
>
>Eric McWilliams
>www.medsynergies.com
>
>
>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
>Of Rick Saylor
>Sent: Monday, March 02, 2015 3:46 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: [ADSM-L] ANS4174E error
>
>Did you activate the policyset?
>
>I recently struggled with this problem too. Setting up and configuring 
>TSM/VE is confusing. I've included the output from my domain, 
>policysets, mgmtclass and copy groups. I hope it will help you figure 
>out what is missing.
>
>Rick Saylor
>Austin Community College
>
>tsm: ADSM>q co  vm*
>
>Policy      Policy      Mgmt        Copy        Versions   Versions
>    Retain    Retain
>Domain      Set
>Name    Class       Group           Data       Data      Extra      Only
>Name                    Name        Name          Exists    Deleted
>Versions   Version
>---------   ---------   ---------   ---------   --------   --------
>--------   -------
>VM_ACC      ACTIVE      VMCTL       STANDARD           3          1
>        30        60
>VM_ACC      ACTIVE      VMDATA      STANDARD           3          1
>        30        60
>VM_ACC      STANDARD    VMCTL       STANDARD           3          1
>        30        60
>VM_ACC      STANDARD    VMDATA      STANDARD           3          1
>        30        60
>
>tsm: ADSM>q do vm_acc f=d
>
>                Policy Domain Name: VM_ACC
>              Activated Policy Set: STANDARD
>              Activation Date/Time: 02/18/15   09:01:03
>             Days Since Activation: 12
>      Activated Default Mgmt Class: VMDATA
>        Number of Registered Nodes: 10
>                       Description: TSM for VE - Domain
>   Backup Retention (Grace Period): 30
>Archive Retention (Grace Period): 365
>    Last Update by (administrator): RSAYLOR
>             Last Update Date/Time: 02/18/15   09:01:03
>                  Managing profile:
>                   Changes Pending: No
>             Active Data Pool List:
>
>tsm: ADSM>q po vm_acc f=d
>
>              Policy Domain Name: VM_ACC
>                 Policy Set Name: ACTIVE
>         Default Mgmt Class Name: VMDATA
>                     Description: TSM for VE - Policy Last Update by
> (administrator): RSAYLOR
>           Last Update Date/Time: 02/18/15   08:59:40
>                Managing profile:
>                 Changes Pending: No
>
>              Policy Domain Name: VM_ACC
>                 Policy Set Name: STANDARD
>         Default Mgmt Class Name: VMDATA
>                     Description: TSM for VE - Policy Last Update by
> (administrator): RSAYLOR
>           Last Update Date/Time: 02/18/15   08:59:40
>                Managing profile:
>                 Changes Pending: No
>
>tsm: ADSM>q mgmt vm_acc f=d
>
>              Policy Domain Name: VM_ACC
>                 Policy Set Name: ACTIVE
>                 Mgmt Class Name: VMCTL
>            Default Mgmt Class ?: No
>                     Description: TSM for VE - Control information 
> management class
>      Space Management Technique: None
>         Auto-Migrate on Non-Use: 0
>      Migration Requires Backup?: Yes
>           Migration Destination: SPACEMGPOOL Last Update by
> (administrator): RSAYLOR
>           Last Update Date/Time: 02/18/15   08:59:38
>                Managing profile:
>                 Changes Pending: No
>
>              Policy Domain Name: VM_ACC
>                 Policy Set Name: ACTIVE
>                 Mgmt Class Name: VMDATA
>            Default Mgmt Class ?: Yes
>                     Description: TSM for VE - Data management class
>      Space Management Technique: None
>         Auto-Migrate on Non-Use: 0
>      Migration Requires Backup?: Yes
>           Migration Destination: SPACEMGPOOL Last Update by
> (administrator): RSAYLOR
>           Last Update Date/Time: 02/18/15   08:59:37
>                Managing profile:
>                 Changes Pending: No
>
>              Policy Domain Name: VM_ACC
>                 Policy Set Name: STANDARD
>                 Mgmt Class Name: VMCTL
>            Default Mgmt Class ?: No
>                     Description: TSM for VE - Control information 
> management class
>      Space Management Technique: None
>         Auto-Migrate on Non-Use: 0
>      Migration Requires Backup?: Yes
>           Migration Destination: SPACEMGPOOL Last Update by
> (administrator): RSAYLOR
>         Auto-Migrate on Non-Use: 0
>      Migration Requires Backup?: Yes
>           Migration Destination: SPACEMGPOOL Last Update by
> (administrator): RSAYLOR
>           Last Update Date/Time: 02/18/15   08:59:37
>                Managing profile:
>                 Changes Pending: No
>
>              Policy Domain Name: VM_ACC
>                 Policy Set Name: STANDARD
>                 Mgmt Class Name: VMCTL
>            Default Mgmt Class ?: No
>                     Description: TSM for VE - Control information 
> management class
>      Space Management Technique: None
>         Auto-Migrate on Non-Use: 0
>      Migration Requires Backup?: Yes
>           Migration Destination: SPACEMGPOOL Last Update by
> (administrator): RSAYLOR
>           Last Update Date/Time: 02/18/15   08:59:38
>                Managing profile:
>                 Changes Pending: No
>
>              Policy Domain Name: VM_ACC
>                 Policy Set Name: STANDARD
>                 Mgmt Class Name: VMDATA
>            Default Mgmt Class ?: Yes
>                     Description: TSM for VE - Data management class
>      Space Management Technique: None
>         Auto-Migrate on Non-Use: 0
>      Migration Requires Backup?: Yes
>           Migration Destination: SPACEMGPOOL Last Update by
> (administrator): RSAYLOR
>           Last Update Date/Time: 02/18/15   08:59:37
>                Managing profile:
>                 Changes Pending: No
>
>tsm: ADSM>q co vm_acc f=d
>
>                   Policy Domain Name: VM_ACC
>                      Policy Set Name: ACTIVE
>                      Mgmt Class Name: VMCTL
>                      Copy Group Name: STANDARD
>                      Copy Group Type: Backup
>                 Versions Data Exists: 3
>
>                Versions Data Deleted: 1
>                Retain Extra Versions: 30
>                  Retain Only Version: 60
>                            Copy Mode: Modified
>                   Copy Serialization: Shared Static
>                       Copy Frequency: 0
>                     Copy Destination: VMPOOL_CTL Table of Contents
> (TOC) Destination:
>       Last Update by (administrator): RSAYLOR
>                Last Update Date/Time: 02/18/15   08:59:45
>                     Managing profile:
>                      Changes Pending: No
>
>                   Policy Domain Name: VM_ACC
>                      Policy Set Name: ACTIVE
>                      Mgmt Class Name: VMDATA
>                      Copy Group Name: STANDARD
>                      Copy Group Type: Backup
>                 Versions Data Exists: 3
>                Versions Data Deleted: 1
>                Retain Extra Versions: 30
>                  Retain Only Version: 60
>                            Copy Mode: Modified
>                   Copy Serialization: Shared Static
>                       Copy Frequency: 0
>                     Copy Destination: VMPOOL_DATA Table of Contents
> (TOC) Destination:
>       Last Update by (administrator): RSAYLOR
>                Last Update Date/Time: 02/18/15   08:59:42
>                     Managing profile:
>                      Changes Pending: No
>
>                   Policy Domain Name: VM_ACC
>                      Policy Set Name: STANDARD
>                      Mgmt Class Name: VMCTL
>                      Copy Group Name: STANDARD
>                      Copy Group Type: Backup
>                 Versions Data Exists: 3
>                Versions Data Deleted: 1
>                Retain Extra Versions: 30
>                  Retain Only Version: 60
>                            Copy Mode: Modified
>                   Copy Serialization: Shared Static
>                       Copy Frequency: 0
>                     Copy Destination: VMPOOL_CTL Table of Contents
> (TOC) Destination:
>       Last Update by (administrator): RSAYLOR
>                Last Update Date/Time: 02/18/15   08:59:45
>                     Managing profile:
>                      Changes Pending: No
>
>                   Policy Domain Name: VM_ACC
>                      Policy Set Name: STANDARD
>                      Mgmt Class Name: VMDATA
>                      Copy Group Name: STANDARD
>                      Copy Group Type: Backup
>                 Versions Data Exists: 3
>                Versions Data Deleted: 1
>                Retain Extra Versions: 30
>                  Retain Only Version: 60
>                            Copy Mode: Modified
>                   Copy Serialization: Shared Static
>                       Copy Frequency: 0
>                     Copy Destination: VMPOOL_DATA Table of Contents
> (TOC) Destination:
>       Last Update by (administrator): RSAYLOR
>                Last Update Date/Time: 02/18/15   08:59:42
>                     Managing profile:
>                      Changes Pending: No
>
>
>At 01:32 PM 3/2/2015, you wrote:
> >I've created a management class and added it to the dsm.opt file.
> >
> >VMCTLMC VMCTL_MC
> >
> >However, when I run the backups I get this error:
> >
> >03/02/2015 09:27:03 ANS9388E The management class 'VMCTL_MC'
> >specified for the 'VMCTLMC' option is invalid, or does not have a 
> >backup copy group.
> >03/02/2015 09:27:03 ANS1105E The management class for this file does 
> >not have a valid backup copy group.
> >This file will not be backed up.
> >
> >tsm: EAGLEROCK>q co vmctl vmctl_ps vmctl_mc t=b f=d
> >
> >                  Policy Domain Name: VMCTL
> >                     Policy Set Name: VMCTL_PS
> >                     Mgmt Class Name: VMCTL_MC
> >                     Copy Group Name: STANDARD
> >                     Copy Group Type: Backup
> >                Versions Data Exists: 5
> >               Versions Data Deleted: 2
> >               Retain Extra Versions: 30
> >                 Retain Only Version: 60
> >                           Copy Mode: Modified
> >                  Copy Serialization: Shared Static
> >                      Copy Frequency: 0
> >                    Copy Destination: VMCTLPOOL Table of Contents 
> >(TOC)
> >Destination:
> >      Last Update by (administrator): EMCWILLIAMS
> >               Last Update Date/Time: 03/02/2015 09:17:52
> >                    Managing profile:
> >                     Changes Pending: No
> >
> >I know the management class is valid and and when I query the copy 
> >group it is STANDARD.  Now, the documentation says that it must be 
> >STANDARD but this doesn't make much sense to me.
> >
> >Thanks,
> >Eric
> >
> >-----Original Message-----
> >From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> >Of Prather, Wanda
> >Sent: Wednesday, February 25, 2015 12:32 PM
> >To: ADSM-L AT VM.MARIST DOT EDU
> >Subject: Re: [ADSM-L] ANS4174E error
> >
> >Each backup session backs up some control information, and that 
> >information is restored for use during the next backup.  (You can see 
> >the restores happening if you watch the server during the backup, or 
> >if you look in the accounting info.)
> >
> >I'm just guessing, but I suspect  that the "data unavailable on server"
> >is because it can't restore that control info.
> >Perhaps some volumes in your disk pool are offline, or the control 
> >information has migrated off to tape?
> >
> >If the latter, you need to put these keywords in the dsm.opt on your
> >datamover:
> >
> >VMMC    your-mgmt-class-for-data-goes-here
> >VMCTLMC         your-mgmt-class-for-control-info-goes-here
> >
> >The control info mgmt. class should point to a small disk pool that 
> >can't migrate to tape.
> >
> >Wanda Prather
> >TSM Consultant
> >ICF International Enterprise and Cybersecurity Systems Division
> >
> >
> >
> >
> >
> >-----Original Message-----
> >From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> >Of McWilliams, Eric
> >Sent: Wednesday, February 25, 2015 11:16 AM
> >To: ADSM-L AT VM.MARIST DOT EDU
> >Subject: [ADSM-L] ANS4174E error
> >
> >I'm trying to back up some VM's using DP for VM 7.1.1.0 and am 
> >getting an error on some of the VM's and the backup is failing.  I've 
> >asked Uncle Google and can't find much.  I would contact IBM support 
> >but I get very little help from them as well.
> >
> >02/25/2015 09:35:07 ANS9351E Data was not available on server and
> was skipped.
> >02/25/2015 09:35:07 ANS4174E Full VM backup of VMware Virtual Machine 
> >'Hamilton' failed with RC=14 mode=Incremental Forever - Incremental, 
> >target node name='VCENTER_COTX', data mover node name='VCENTER_COTX_DM'
> >02/25/2015 09:35:08
> >02/25/2015 09:35:08 ANS1228E Sending of object 'Hamilton' failed.
> >02/25/2015 09:35:08 ANS1314E File data currently unavailable on 
> >server
> >
> >Any help would be greatly appreciated.
> >
> >Thanks,
> >
> >Eric
> >
> >*********************************************************************
> >*
> >*** CONFIDENTIALITY NOTICE ***
> >
> >  This message and any included attachments are from MedSynergies, Inc.
> > and are intended only for the addressee. The contents of this 
> > message contain confidential information belonging to the sender 
> > that is legally protected. Unauthorized forwarding, printing, 
> > copying, distribution, or use of such information is strictly 
> > prohibited and may be unlawful. If you are not the addressee, please 
> > promptly delete this message and notify the sender of the delivery 
> > error by e-mail or contact MedSynergies, Inc. at postmaster AT medsynergies 
> > DOT com.
>
>**********************************************************************
>*** CONFIDENTIALITY NOTICE ***
>
>  This message and any included attachments are from MedSynergies, Inc. 
> and are intended only for the addressee. The contents of this message 
> contain confidential information belonging to the sender that is 
> legally protected. Unauthorized forwarding, printing, copying, 
> distribution, or use of such information is strictly prohibited and 
> may be unlawful. If you are not the addressee, please promptly delete 
> this message and notify the sender of the delivery error by e-mail or 
> contact MedSynergies, Inc. at postmaster AT medsynergies DOT com.

**********************************************************************
*** CONFIDENTIALITY NOTICE *** 

 This message and any included attachments are from MedSynergies, Inc. and are 
intended only for the addressee. The contents of this message contain 
confidential information belonging to the sender that is legally protected. 
Unauthorized forwarding, printing, copying, distribution, or use of such 
information is strictly prohibited and may be unlawful. If you are not the 
addressee, please promptly delete this message and notify the sender of the 
delivery error by e-mail or contact MedSynergies, Inc. at postmaster AT 
medsynergies DOT com.

<Prev in Thread] Current Thread [Next in Thread>