ADSM-L

Re: [ADSM-L] Upgrading BACLIENT to 7.1.2.2 broke TSM for VE ???

2015-07-28 15:49:10
Subject: Re: [ADSM-L] Upgrading BACLIENT to 7.1.2.2 broke TSM for VE ???
From: "Billaudeau, Pierre" <P.Billaudeau AT SAQ.QC DOT CA>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 28 Jul 2015 19:47:43 +0000
Hi ,
        After upgrading to VSPhere 6.0, we had to upgrade TSm client from 7.1.1 
to 7.1.2 and also have those 3 patches installed on VSPhere 6.0:

2116126
2116127
2116129

        They all are related to backup and CBT operations.

Pierre

-----Message d'origine-----
De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De la part de 
Gee, Norman
Envoyé : 28 juillet 2015 13:52
À : ADSM-L AT VM.MARIST DOT EDU
Objet : Re: [ADSM-L] Upgrading BACLIENT to 7.1.2.2 broke TSM for VE ???

I have just upgraded one of my servers from 7.1.1 to 7.1.2.2 because of the 
support needed for VSphere 6.0 and I am experiencing some of the same problems. 
I have open a PMR with IBM on this.  I was attempting the backups manually with 
Dsmc -asnode=datacenter Backup vm a -vmbackuptype=fullvm It appears to backup 
but does not.  It gave messages that hinted it did backup, but no statistical 
messages.

I also try
Dsmc -nodename=datacenter
Backup vm a -vmbackuptype=fullvm
It does backup, but this is not the correct way.

I am waiting for IBM for an answer on this.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Tom Alverson
Sent: Tuesday, July 28, 2015 10:41 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Upgrading BACLIENT to 7.1.2.2 broke TSM for VE ???

I saw that article and already had tried that.  I think I may have fixed it.  I 
found in swg21580462 a hint that you may need to do a custom install of the 
BACLIENT and enable the "VMWare Backup Tools" option to fix the issue.  In 
7.1.2.2 there is nothing called "VMware Backup Tools" but there was another 
VMware option that was not enabled and now that I have added that feature I am 
able to expand the list of VM's to backup in the GUI.  I will try a backup next 
and hopefully it will work (any maybe even fix my original problem)

Thanks for your input!

Tom

On Tue, Jul 28, 2015 at 1:34 PM, Billaudeau, Pierre <P.Billaudeau AT saq.qc DOT 
ca>
wrote:

> Hi Tom,
>         It looks like you are not connecting to the Vcenter. You can
> reset your Vcenter user password and try again.
>
>
> Pierre Billaudeau
> Administrateur de stockage
> Livraison des infra serveurs
> SAQ
>
> -----Message d'origine-----
> De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De la part
> de Tom Alverson Envoyé : 28 juillet 2015 13:28 À :
> ADSM-L AT VM.MARIST DOT EDU Objet : [ADSM-L] Upgrading BACLIENT to 7.1.2.2
> broke TSM for VE ???
>
> I had a backup issue with one particular VM (ANS9921E and ANS9919E)
> which I thought might be fixed (per a KB article) by upgrading the
> BACLIENT from
> 7.1.1.0 to 7.1.2.2.  Not only did this not fix the issue but now when
> I run the GUI and click the + to expand the list of VM's to back up I
> get this
> error:
>
> ANS1403E Error loading a required library: vixDiskLib.dll, Win32 rc=126 DLL
>    and
> ANS9266E Failure initializing virtual machine environment.  Can not
> find vcbMounter.exe command RC=-303
>
> So next I upgraded TSM for VE from 7.1.1.0 to 7.1.2.0 but I still get
> the same error.  I searched the entire disk for vcbMounter.exe but
> could not find it.  I then searched the entire disk of a different VBS
> server that was still working and did not find that command either.
> Does anyone know how to resolve this?  I asked someone on our backup
> team to open a ticket with IBM but I would like to fix what I have
> broken quickly if possible before a ton of backup failure tickets are
> created tonight when this backup does not work.
>
> Tom
>
> ------------------
>
>
> Information confidentielle : Le présent message, ainsi que tout
> fichier qui y est joint, est envoyé à l'intention exclusive de son ou
> de ses destinataires; il est de nature confidentielle et peut
> constituer une information privilégiée. Nous avertissons toute
> personne autre que le destinataire prévu que tout examen,
> réacheminement, impression, copie, distribution ou autre utilisation
> de ce message et de tout fichier qui y est joint est strictement
> interdit, à moins d'avoir obtenu le consentement du destinataire. Si
> vous n'êtes pas le destinataire prévu, veuillez en aviser
> immédiatement l'expéditeur par retour de courriel et supprimer ce message et 
> tout document joint de votre système. Merci.
>

------------------


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit, à moins 
d'avoir obtenu le consentement du destinataire. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et supprimer ce message et tout document joint de votre système. Merci.