We are having a lot of trouble trying to get the Avamar client properly installed on our 2 node Windows 2012R2 cluster systems and hope somebody can provide a little more help. EMC Avamar Installation documentation has you install the Avamar client on both nodes and activate/register both with the Avamar administration server. Afterwards, on the active node, run the Cluster configuration tool from the desktop. This all goes as expected and appears that we have installed all correctly. We setup a new backup dataset, and new backup policy, with the Windows Cluster File Server plugin and added the 2 Windows 2012r2 cluster nodes. Backups run fine on the active node, but the secondary node always fails. When we compare the setup of a Windows 2012 cluster to the Windows 2008 cluster, it seems that we are missing the part where we add the cluster resource as a backup client? Does anybody know why the Avamar client installation is so different between the 2 versions of Windows clusters? Also, how are you getting past the secondary node backup failures? Shouldn't the secondary node just get bypassed during the backup? Thanks for any help!
I had issues with clusters when I first when to 7.2 and Windows 2012
1) you don't use the old cluster config (the gray one with one window that you fill out) use the new one you will find in All programs that has a bunch of screens to fill out. I think that is the one you said you ran.
2) and you need 2 different types of backups
a) first one is to get the C drive and system state of the physical nodes this can be done in one job with both servers
b) you need a backup policy for your "virtual" node(s) that specifies the resources(drives) of that node.
Reason is if Server1 is active it will always get all the drives, but none of the cluster resources on Server2
this makes it hard to do a restore because you might have to bounce between the two servers
if you do a new policy that uses the virtual node and its drives, it will always get those drive no matter what Server is Active.
what was hard for me was getting that cluster config setup correctly, by making sure I had it put the avamar files on the resources drive so when my policy that backed up the virtual node and just its drives, it could find avamar.
this does not seem to be your issue could you explain in more detail what you have done for your setup and just what the failure is?
J.H., Thank you for your reply. However, I have just found out that this is not correct. After spending time with support and going back and firth on this, you do use the older AvamarClusterConfiguration tool, with 2012 as well as 2008, to properly register and configure the Windows server cluster resource as in the Avamar system. The icon that is placed on the desktop did not work for us. It allowed us to backup the cluster files on which ever node had control of it, but then you had to browse both servers to find the files for a restore. With the older tool, it creates a cluster resource as a Avamar client, and then we used the correct datasets to backup the clustered files. A different dataset was used for the Windows cluster nodes.
Again, Thank you for your time and helpful answer.
I forgot that in 7.2 the “new” one did not work!
I had a ticket on that about not being able to do it for 2012, and you are correct, EMC had be go back and use the old way.
I have slept snice then and forgot about the R2 issue
AIX Systems Engineer, Technology – Infrastructure & Services
19001 Crescent Springs Drive | Mail Stop 1-5335 | Kingwood, Texas 77339
OFFICE: (281) 312-3538 | MOBILE: (281) 853-4098 | FAX: (281) 348-2838