Unsolved
This post is more than 5 years old
9 Posts
1
17476
Avamar 6.1 backup for SQL 2008 server failing
The backup of SQL 2008 server is failing with the following error:
2012-12-05 22:00:02 avsql Info <5008>: Logging to C:\Program Files\avs\var\Data_Warehouse-DW_Databases-1354705201315-3006-SQL.log 2012-12-05 22:00:02 avsql Info <6673>: CTL listening on port 61060 2012-12-05 22:00:02 avsql Info <10684>: Setting ctl message version to 3 (from 1) 2012-12-05 22:00:02 avsql Info <16136>: Setting ctl max message size to 268435456 2012-12-05 22:00:02 avsql Info <7838>: - Adding user exclude "*/tempdb" 2012-12-05 22:00:07 avsql Error <15760>: No targets after expansion! 2012-12-05 22:00:07 avsql Info <7271>: Final summary generated subwork 0, cancelled/aborted 0, snapview 0, exitcode 536870919 2012-12-05 22:00:12 avsql Info <6451>: avsql returning with exitcode 536870919
The server is 2008 R2 64-bit and Avamar version 6.1.100-402. I am unable to find any more logs related to this. I am new to Avamar and not able to dig more. Please advice what needs to be done. Thanks in advance
ionthegeek
2K Posts
0
December 5th, 2012 06:00
I would recommend opening a service request for this issue.
fdxpilot
143 Posts
0
December 5th, 2012 20:00
Are the SQL Server Management Objects installed? Can you browse the databases on the server via Avamar (Backup & Restore option)?
shreiks
9 Posts
0
December 6th, 2012 05:00
The SQL Server Management Objects are not installed. I am not able to browse the databases from Server using Backup & Restore option.
fdxpilot
143 Posts
0
December 6th, 2012 05:00
You will need to install SQL SMO to use the the Avamar SQL agent since Avamar uses these objects to communicate with SQL. We found this out the hard way since this dependency doesn't appear to be documented anywhere I looked at the time.
shreiks
9 Posts
0
December 6th, 2012 07:00
Is this SQL SMO required for all SQL backups? Because there are other servers on which the SQL backups are running successfully. Because on that server also, SQL 2008 is running and backups are running successfully and i do not see SQL SMO installed.
fdxpilot
143 Posts
0
December 6th, 2012 14:00
I do believe SQL SMO is required to use the SQL Avamar plugin but I'm sure someone will correct me if that is wrong. Does the Avamar config checker report any errors on either the SQL server that is working or the one that is not working? It will check for the SMO DLLs that Avamar needs to function.
stewartk2
20 Posts
0
January 2nd, 2013 08:00
Does the SQL SMO need to be installed separately? We have the SQL Server Management Studio installed (which the SMO is included I think), and we are having the same problem.
The SQL backups worked fine unitl the last patch cycle. I've been running this fix:
mofcomp "%programfiles(x86)%\Microsoft\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
And it fixes the problem for one night, and then the issue reoccurs.
Kathy
niko.virta
51 Posts
0
January 22nd, 2013 05:00
I got few servers which declined to backup at all and few which backupped themselves for few weeks and then you needed to restart the Avamar agent.
Solved this by uninstalling 6.1.100-402 plugin and installed 6.0.1-66 plugin to these servers.
fdxpilot
143 Posts
0
January 23rd, 2013 09:00
You might want to be aware of this limitation (from the Avamar 6.1 SQL user guide):
Avamar plug-in and server version compatibility issues
If you upgrade the Avamar Plug-in for SQL Server to release 6.1, then you must also
upgrade the Avamar server software to release 6.1. Do not use a SQL Server plug-in
running release 6.0 or earlier to back up to or restore from an Avamar server running
release 6.1. Also, do not use a SQL Server plug-in running release 6.1 to back up to or
restore from an Avamar server running release 6.0 or earlier.
The user interface and underlying code for several features, including point-in-time restore
and redirected restore, has changed in release 6.1. The changes require release 6.1 on
both the client and server.
Mahmoud_Majed
1 Message
0
May 15th, 2017 00:00
hi,
In my case i started receiving this error after upgrading to avamar sql client version 7.3. But after installing the SQL SMO, i was able to browse the SQL from the avamar server and the backup worked fine.
thanks guys.