Solved!
Go to SolutionSQL backup not working
Hello.
I've deployed a new Windows Server 2016 with SQL Server 2016. Just installed the Avamar client and SQL plugin v 7.1.102-21.
The client was successfully registered with the server. The client is showing on the Avamar Administrator.
When I browse the client for a manual backup on the Avamar Administrator, I can successfully list windows file system, but nothing shows under the Windows SQL node. It should list the SQL instance but nothing shows.
When I attempted a scheduled SQL backup, the avsql log ends with these errors:
2017-04-13 04:00:08 avsql Error <19498>: Unable to load any of SMO managed DLL files.
2017-04-13 04:00:08 avsql Error <15744>: Unable to load SMO managed DLL: (symbol SMO_New not found)
2017-04-13 04:00:08 avsql Error <15760>: No targets after expansion!
2017-04-13 04:00:08 avsql Error <15760>: No targets after expansion!
2017-04-13 04:00:08 avsql Info <7271>: Final summary generated subwork 0, cancelled/aborted 0, snapview 0, exitcode 536870919
2017-04-13 04:00:13 avsql Info <6451>: avsql returning with exitcode 536870919
Only thing I noted it could be wrong was the security at SQL for the System account which wasn't sysadmin, but I set it now and I still can't list the SQL instances on Avamar.
Do you have an idea on what could be wrong?
ShadySalama
18 Posts
12366
0
Posted April 13th, 2017 23:00
Hi Jeol,
SQL 2016 is not supported with Avamar plugin of version 7.1; it is supported with version 7.4.
Please upgrade the Avamar server and plugin to 7.4 to get full support of SQL 2016 on windows server 2016.
Appreciate your update and feedback if this was helpful to solve the problem; don't forget to mark the question as answered when the problem is solved.
Best Regards,
Shady Salama
Subject Matter Expert (SME), Avamar, Data Protection & Availability Solutions
Dell EMC | Technical Support Services
ptsysadmins
1 Message
4578
0
Posted March 11th, 2021 15:00
Greetings,
The same fix is applicable for SQL 2019?
Kind regards.
ShadySalama
18 Posts
12366
0
Posted April 17th, 2017 05:00
Unfortunately we can't even proceed with the catalogue upgrade because Avamar server 7.1 doesn't support client/plugin of version 7.4.
So, the only option is to upgrade the Avamar server itself then upgrade the client/plugin on the SQL server to be able to backup SQL 2016 DBs.
Another temporary option is to perform SQL backup using the SQL Native tools into dump files, then backup these dump files to Avamar using the windows file system plugin, however slow performance is expected for this backup operation; especially with the change rate expected from the DBs and logs.
Thanks,
Shady