Skip to main content

SQL Backup problem

Thread needs solution
Beginner
Posts: 3
Comments: 2

Hi we have a problem with backup on SQL machine. Details bellow

When running Acronis Backup for VMware 9.2.10535 on vCenter 6. Acronis Backup for Vmware Backup Agent is installed

Subject: Task 'Back up to 'SQL Rumba'' has failed on machine 'AcronisWieza'.

Backup has failed. Please check the log for additional information.
1    Information    3/30/16 10:34:51 AM    Task 'Back up to 'SQL Rumba'' was created.
2    Information    3/30/16 10:34:51 AM    Task 'Back up to 'SQL Rumba'' changed its state from 'idle' to 'running'.
3    Information    3/30/16 10:34:51 AM    Task 'Back up to 'SQL Rumba'' was started.
4    Information    3/30/16 10:34:51 AM    Backing up VM(s).
5    Information    3/30/16 10:34:51 AM    The archive 'SQLRumba' is missing. New archive is created.
6    Information    3/30/16 10:34:51 AM    Successfully connected to 'VMware vCenter Server 6.0.0 build-3339084'.
7    Information    3/30/16 10:34:51 AM    Successfully connected to 'VMware ESXi 6.0.0 build-3380124' through VMware vCenter Server.
8    Information    3/30/16 10:34:52 AM    Successfully connected to 'VMware ESXi 6.0.0 build-3380124' through VMware vCenter Server.
9    Information    3/30/16 10:34:52 AM    Successfully connected to 'VMware ESXi 6.0.0 build-3380124' through VMware vCenter Server.
10    Information    3/30/16 10:34:53 AM    Successfully connected to 'VMware vCenter Server 6.0.0 build-3339084'.
11    Information    3/30/16 10:34:55 AM    Successfully connected to 'VMware vCenter Server 6.0.0 build-3339084'.
12    Information    3/30/16 10:34:56 AM    Successfully connected to 'VMware ESXi 6.0.0 build-3380124' through VMware vCenter Server.
13    Error    3/30/16 10:35:48 AM    The operation has failed.
Additional info:
--------------------
Error code: 26
Module: 100
LineInfo: 48afbd3608a410ca
Fields:
Message: The operation has failed.
--------------------
Error code: 537
Module: 149
LineInfo: fc2924f06484b5f1
Fields:
Message: Meta collection during application-aware backup failed.
--------------------
Error code: 535
Module: 149
LineInfo: fc2924f06484b668
Fields:
Message: Application is not installed correctly
--------------------
14    Information    3/30/16 10:35:50 AM    Task 'Back up to 'SQL Rumba'' changed its state from 'running' to 'idle'.
15    Error    3/30/16 10:35:50 AM    Task 'Back up to 'SQL Rumba'' failed: 'Failed to create a backup.
Additional info:
--------------------
Error code: 3
Module: 435
LineInfo: 555b5abba0950340
Fields:
Message: Failed to create a backup.
--------------------
Error code: 32786
Module: 114
LineInfo: 28314c961de7d337
Fields:
Message: Failed to prepare for backing up.
--------------------
Error code: 353
Module: 149
LineInfo: a71592046cb2c5f6
Fields:
Message: Failed to back up the group.
--------------------
Error code: 2
Module: 218
LineInfo: 338a407ad20e0987
Fields:
Message: Error occurred while running the backup and recovery engine.
--------------------
Error code: 537
Module: 149
LineInfo: fc2924f06484b5f1
Fields:
Message: Meta collection during application-aware backup failed.
--------------------
Error code: 535
Module: 149
LineInfo: fc2924f06484b668
Fields:
Message: Application is not installed correctly --------------------'.

0 Users found this helpful
Acronis Program Manager
Posts: 22
Comments: 3742

Hi,

Such problems are related to specifics of installation of supported applications (SQL/AD/Exchange) inside the backed up VM when application-aware backup option is enabled. In some cases it's a problem with invalid vss writers registration and in others it may be something else, so there is no single general cause. You should contact our support team for further assistance.

Thank you.

--

Best regards,

Vasily

Acronis Virtualization Program Manager

Acronis Program Manager
Posts: 22
Comments: 3742

In addition to my previous comment here's a suggestion that may help (we've just confirmed that it helped another customer):

https://blogs.msdn.microsoft.com/batala/2011/08/01/sqlserverwriter-missing-when-vssadmin-list-writers-command-is-run/

The problem was in missing SQL VSS writer in "vssadmin list writers" output and it was caused by spaces in the SQL DB names, which should be removed as described at this link. Hope this helps.

Beginner
Posts: 3
Comments: 2

We found solution in reply to Your link.

"

Kenneth says:

July 15, 2014 at 4:05 am

Just wanted to add my solution. This post is old (from 2011) but i had similar problem on Windows 2012 R2 Server. I tried all abowe + other suggestions from other sites, and none eowrked. Then i decided to try some changes regarding accounts to see if it matter. The solution was very simple – I changed log in account on the SQL Server Witer Service from Local Service to administrator account. Restarted the service and then vvssadmin lis writers finnaly show the SQlSrvWriter as it should. And i can connect succesfully to SQL from Backup software.

"

Additional to he's solution about account change in SQL Server VSS Writer service we have add the same account sysadmin role in SQL Server Management Studio. Object Security\Logins.

Thaks for help Vasily.