Unsolved
This post is more than 5 years old
2 Posts
0
726
February 26th, 2011 00:00
Does Anyone have 7.6.1 working with vSphere 4.1?
Summary of the environment:
NW 7.6.1 on W2003 R2 SP2 - also the storage node
VC W2008 64-bit
ESX 4.1
I have set the command host as the 32 bit NW server. NW discovers all 4 ESX hosts without a hitch. I get this failure in every vcb backup I try:
savegrp: suppressed 3 lines of output.
VC\ESX Host Name : 10.10.101.128
VC\ESX Port : 443
VC\ESX Username : XXXXXXXX@XXXXXXXX.com
Mount point : g:\\mnt\SLSAFLOK1
Flavor : file
Transport Mode : SAN
Snap policy : automatic
Max retry : 3
Max backoff time : 50
Performing a FULL File level backup.
No earlier Snapshot for VCB-BACKUP exists for the VM host: SLSAFLOK1.
Starting VCB mount operation..
Starting NetWorker save operation..
C:\Program Files\Legato\nsr\\bin\save.exe -s slbackup.silverlegacy.com -c SLSAFLOK1 -g SLSAFLOK -LL -b "Default" -m SLSAFLOK1 -o vss:*=off; -l full -q -W 78 -N VM:SLSAFLOK1.silverlegacy.com:ALLVMFS -x g:\\mnt\SLSAFLOK1\SLSAFLOK1\letters
Any help is appreciated.
Thanks
andreas.scht
2 Intern
•
219 Posts
0
March 1st, 2011 00:00
Hi,
I`m not sure but ESX 4.1 doesn`t support VCB anymore. You have to use VADP instead but this will be supported by 7.6.2 first. So the only way to backup your VMs is to manually install nsr client to all your VMs which were backed up by VCB.
See further esg112035 (VADP will be supported with NetWorker version 7.6.2):
https://solutions.emc.com/emcsolutionview.asp?id=esg112035
"Customer would like to install next release of vSphere which no longer supports VCB"
Regards,
Andreas
cmccall1
2 Posts
0
March 1st, 2011 09:00
My question was actually answered by support. And it is working now.
Part of the problem was that the NW agent needed to be installed on the VC server was a fixed version. NW User 7.6.1.3 Build 446. The previous agent's Remote Exec Services wouldn't stay started. With the new client version it did.
There were also a couple of parameter tweaks in Apps/Modules. the syntax I had wasn't correct; for the pre-existing mountpoint and snapshot parms I had 'delete' capitalised when it shouldn't have been. They also had me remove vmlookup and transport mode parms as apparently 'ipaddr' and 'SAN' are default now, so why enter them.
I think that was it. If there's anything else, I'll post here.
Thanks,
Charles