BE2012 HyperV Servers

[pgdave]

Hey All,

Upgraded to BE2012 and have had a few issues so far which I can't seem to find much help on:

1. I can't seem to install agents on other servers any more. I have HyperV host agents which installed fine, however I can't install agents on VMs from the server itself. I have since installed manually but wondered is this is by design or not.

2. I added the HyperV hosts and virtual servers. However quite a few servers are showing as physical machines even though they are virtual. I manually installed the RAWS running setupaofox64.

3. Part of the enviroment is HyperV cluster running on an equallogic PS6510 SAN and I get this error when backing up the cluster -

- Snapshot Technology: Initialization failure on: "VRTSRV::\\cluster.Domain.local\Hyper-V?HA?VM\Server". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11225 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology that you selected does not support snap technology for this volume. Select another snapshot technology, and then run the job again.

This happens on all VMs stored on CSVs. I am backing up the HyperV VMs, not the folders in C:\ClusterStorage. As stated the agent is on the VMs and running fine. For the time being I am just running normal backups at the server level.

4. I get a warning on some hosts about client side de-dupe being on but not able to be used, but I'm not sure why when all agents and hosts were  installed and set up exactly the same. Error is -

Client-side deduplication is enabled for this job, but it could not be used.  Please check this link for additional information:
http://entsupport.symantec.com/umi/V-79-18273

and the link seems to go nowhere and the 2010 info doesn't really help.

Thanks

[Riyaj_S]

1. I can't seem to install agents on other servers any more. I have HyperV host agents which installed fine, however I can't install agents on VMs from the server itself. I have since installed manually but wondered is this is by design or not.

--> http://www.symantec.com/docs/TECH179142 (How to install Backup Exec 2012 Agent for Windows.)

2. I added the HyperV hosts and virtual servers. However quite a few servers are showing as physical machines even though they are virtual. I manually installed the RAWS running setupaofox64.

--> The correct command to install remote agent is setupaa.cmd (for 32-bit OS) or setupaax64.cmd (for 64-bit OS) to install Agent for Windows. Please make sure that all the Remote agents are publishing and trust is established so that Virtual node can be seen in the selection

http://www.symantec.com/docs/TECH183038

http://www.symantec.com/docs/HOWTO73729

3. Part of the enviroment is HyperV cluster running on an equallogic PS6510 SAN and I get this error when backing up the cluster -

- Snapshot Technology: Initialization failure on: "VRTSRV::\\cluster.Domain.local\Hyper-V?HA?VM\Server". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11225 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology that you selected does not support snap technology for this volume. Select another snapshot technology, and then run the job again.

--> http://www.symantec.com/docs/HOWTO21795

Hope this helps.

[pgdave]

Thanks for the reply.

1. I've reinstalled BE2012 (prior was an upgeade) and can now install agents from within the software again. Not sure what happened with the upgrade but behaving correctly now.

2. I've always used setupaofox as in the past I've needed AOFO for whatever reason. Has this changed?Some machines are changing to virtual after a backup completes, some are not. Apart from the AOFO option not being installed does the regular setupaax64 do anything different? 

3. I resolved this by removing VHDmount (possibly not working correctly) and installing the Hyper-V role.

[pkh]

There is no more AOFO in BE 2012.