Take a look at page 18 of the Avamar SQL guide. If your SQL servers are Windows 2012 R2 or later, this might apply to you:
On Windows Server 2012 R2, the Avamar Plug-in for SQL Server supports storage of SQL Server databases and log files in an active/passive cluster on shared disks, clustered shared volumes (CSVs), and shared virtual hard disk (VHDX) files. Shared VHDX files must be located on either a CSV or on a Server Message Block (SMB) 3.0 file share.
I suspect it's asking for a path for any Shared VHDX files where your databases and logs could be stored.
As mentioned before, SQL2012 supports shared VHDX files on an SMB mount. Avamar is allowing you to put in that same information, if you're using them for your SQL instance. If not, you should be able to skip that field. Is this not the case?
Not sure if you got your answer, I also ran into the problem. So instead of using the new cluster configuration to create the SQL cluster, I used the old cluster configuration executable to create it.
Go to your primary SQL cluster server, and head to C:\program files\avs\bin instead of running "av_cluster_config_wizard.exe" use the old executable which is "AvamarClusterConfiguration.exe"
umichklewis
4 Apprentice
•
1190 Posts
998
1
Posted August 29th, 2016 08:00
Take a look at page 18 of the Avamar SQL guide. If your SQL servers are Windows 2012 R2 or later, this might apply to you:
On Windows Server 2012 R2, the Avamar Plug-in for SQL Server supports storage of SQL Server databases and log files in an active/passive cluster on shared disks, clustered shared volumes (CSVs), and shared virtual hard disk (VHDX) files. Shared VHDX files must be located on either a CSV or on a Server Message Block (SMB) 3.0 file share.
I suspect it's asking for a path for any Shared VHDX files where your databases and logs could be stored.
Let us know if that helps!
Karl