Skip to main content

I have the following situation:

1 or more Hyper-V clusters (MA + VSA installed on every node)

1 domain service account configured on the Hyper-V instance (Client)

1 media agent server (fysical) not domain joined (with MA, VSA, CommandDevice and Raidmanager installed)

1 Hitachi VSP F700 storage Array with IntelliSnap integration on subclient.

 

First, the primary snap is doing great.

Second after the snapshot the backup copy must start and mount the snapshot (proxy redirected in the subclient) to the same media agent.

When the discovery starts CommVault tries to login on the media agent server and fails:

“Set pending cause (unable to connect to virtual machine host (mediaagent server) as user (domain\user) Please ensure that the access node is able to communicate with the host and the user en pw is correct :: client (mediaagentserver)”

 

Now, if I join the mediaagent server to the AD domain the backup copy works, the snapshot is mounted on the mediaagent server and the data is read from the snapshot to the disklibrary.

The media agent works as a remote media proxy server for Intellisnap/Hyper-V

The thing is I don't want to be joined to the domain for hardening reasons.. !!

For example VMware back-up in the same way (with IntelliSnap) does not have this issue which make sence.

Is there limitation or reason why this is not possible with Hyper-V??

And is there a way to work around this?

With Regards, Henk.

Hello @HenkR !

 

As of now, this can not be done. We require the VSA proxy doing the backup copy to be on the same domain.


With that being said, There is a CMR in place, CMR number 300828. You can ask your account rep to add you to this CMR so you can track the status of it on your cloud.commvault.com homepage.

An alternative could be to configure a Media Agent on the Hyper-V nodes along with VSA and then allow access to the library using dataserver-ip.

This is a completely proprietary commvault protocol and the OS wont be able to ‘see’ the data, which really limits exposure to threats - anyway, just wanted to throw another option out there for you.

https://documentation.commvault.com/11.24/expert/9391_sharing_mount_path_using_dataserver_ip.html

 

An alternative could be to configure a Media Agent on the Hyper-V nodes along with VSA and then allow access to the library using dataserver-ip.

This is a completely proprietary commvault protocol and the OS wont be able to ‘see’ the data, which really limits exposure to threats - anyway, just wanted to throw another option out there for you.

https://documentation.commvault.com/11.24/expert/9391_sharing_mount_path_using_dataserver_ip.html

 

Hi Damain,

Thanks for throwing this option, the only thing is that we cant bear to have back-up traffic over the LAN. We are offloading the snaps through SAN. With IP based traffic from Agent to Mediaagent this is just not an option.  Unless you see it differently.

Hello @HenkR !

 

As of now, this can not be done. We require the VSA proxy doing the backup copy to be on the same domain.


With that being said, There is a CMR in place, CMR number 300828. You can ask your account rep to add you to this CMR so you can track the status of it on your cloud.commvault.com homepage.

Thanks this explains a lot. I have now 2 ways : 1 follow the CMR and 2. Wait until environment converted to VMware (which could take a while but that also counts for the CMR)
 

Reply


Terms & ConditionsCookie settings