Is anyone using Avamar to backup a SQL 2012 Always On configuration?
We have a 4 node SQL cluster running SQL 2012 Always On. The cluster is configured as follows:
Each application group is configured on 2 nodes and the storage is shared to only those 2 nodes, the other 2 nodes cannot see that application groups storage.
I have configured the application groups for backups using the Avamar Cluster Configuration Tool. The issue I am running into is that Avamar is basically unable to see any of the clustered drives for backup or restore, I can only see the local C and D drive to backup, none of the clustered drives.
I have tried pointing the Var folder to a seperate third party share outside of the nodes, this did not make a difference.
We have also tried using the SQL Plug in, however that only allows us to browse to the actual SQL databases, which we do not want to back up, we exclude SQL databases from our backups and only backup the backup, log, and transaction files. With the SQL plug in we still cannot browse to all cluster shared drives.
Has anyone run into this issue or something similar? Any suggestions or help is greatly appreciated.
Don't bother using the SQL plug in for Avamar on a MSCS Cluster. If it hasn' t corrupted a database or caused a failover failure yet, your extremely lucky. twice bitten!!!
Do you guys have any details regarding the issues you've seen when using the SQL plugin in a MSCS environment? It would be worth bringing these issues to the attention of support/engineering so they can get fixed. Marketing loves to brag about Avamar's tight integration with Microsoft products so if this isn't working, it should be fixed (since marketers would never stretch the truth! ). I believe one of the manager's of Microsoft plug-in development even posts here from time to time.
Okay pretty simple here. the plugin for a MSCS cluster plants itself in the cluster resources. it failed within an hour of installation, and the service won't restart, so the cluster goes down after a couple failovers. ( have it set to not continue to failover if it fails 3 times) there are no events logged anywhere so its just not something i can let sit in there and fail.
now on the other 2008 R2 MSCS cluster i didn't even know the backup people had installed it, took a little longer, a week, then it corrupted master and msdb as well as a biztalk database. biztalk database are continuously in use, so it just took some time for it to totally ruin my cluster. not willing to spend any time diagnosing a utility that has this kind of failure rate.
now i could have placed it in its own MSCS resource group and configured it to just stay failed and not restart. but after the corruption, i really don't have the extra time to correct corrupt system databases and applications databases every week. Just not the kind of software i want to experiment with.
Is this still a problem with the new avamar version 7.0... ? I'm looking to configure a backup for our 2 node SQL 2012 Always on cluster, but cannot affort to use a software that will corrupt my databases.
What best practise do you recommend as workaround?
after a problem with backing up a sharepoint farm with a clustered SQL, avamar tech find that avamar 7 is not compatible with SQL always on. We have to upgrade to 7.1
Sandeep_Sinha
307 Posts
996
0
Posted November 7th, 2012 23:00
Which Avamar plugin version are you running ?