Re: Strange TSM for VE error

At one point I had exclusion with wildcards in the VM names and all of the sudden that stop working after the TDP got updated. My exclusion list now list all of the exact VM names. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tom

Re: Strange TSM for VE error

We don't have any VEEAM backups, only TSM for VE. On Thu, Jun 2, 2016 at 9:04 AM, Rick Adamson wrote: > Tom, > I think you need to look for the cause in either vCenter or Veeam. > The message *"The method is disabled by XXX" refers to vCenter > blocking backup

Re: Strange TSM for VE error

OK this is getting weirder and weirder - the server that was generating the vShield_SVM error was a vshield server that our vmware guys said should not be backed up. The options were set (by an exclusion option) to skip all of the server names that are used for vShield - except the exclusion was

Re: Strange TSM for VE error

Tom: I had an extremely similar problem, with this same string in my errors -- "ReconfigVM_USCORETask" This is the article I read that helped me to solve my problem. In short... vCenter permissions. http://www-01.ibm.com/support/docview.wss?uid=swg21497028 Good Luck Best regards, Mike Ryder

Re: Strange TSM for VE error

Tom, I think you need to look for the cause in either vCenter or Veeam. The message *"The method is disabled by XXX" refers to vCenter blocking backup tasks via the API, and vShield_SVM is specific to Veeam. There are known issues where a task such as vMotion runs, which sets a flag in

Re: TSM4VE 7.1.3 - Backup report for a specific VM?

Eric For a VM called VMNAME, you can try something like the following from a server command line and see if it meets your needs. select sub_entity as "VM",start_time as "Backup Start",end_time as "Backup End",successful as "Success?" from summary_extended where sub_entity='VMNAME' and

Re: ANR3619W

Hi guys! Thanks for all suggestions! We found the cause: in our case TSM is running on a cluster, controlled by Veritas. So TSM is started by the Veritas Cluster Services (VCS). Although the VCS executes the startup script through root, it uses its own environment. When you update environment