Details
With LanScope enabled, Online Backup logs errors, and the backup fails (Exit Code: -311).
--------------------------------------------------------------
ERROR: Selected writer 'SqlServerWriter' is in failed state!
- Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)
- Writer Failure code: 0x800423f4 (<Unknown error code>)
- Writer ID: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
- Instance ID: {43c23754-9acc-444e-8306-eaf1d8781abe}
--------------------------------------------------------------
An error related to SQL worker threads is recorded in the Windows application log.
--------------------------------------------------------------
Log Name: Application
Source: MSSQLSERVER
Event ID: 3627
Level: Error
Description:
Failed to start a new operation due to too many running in parallel. Increase available threads using the “max worker threads” setting or reduce parallel operations.
--------------------------------------------------------------
Log Name: Application
Source: SQLWRITER
Event ID: 24583
Level: Error
Description:
Sqllib Error: Backup failed due to an OLEDB error while executing ICommandText. Errors include abnormal database termination (Error 3013) and failure to create a worker thread (Error 3224).
--------------------------------------------------------------
* This error results from SQL Server and SQL Writer limitations and cannot be fixed by ActiveImage Protector.
Workaround
1) Workaround on LanScope:
With LanScope installed, SQL Server Express Edition is set up. An abnormal increase in databases raises the risk of issues. Consult the LanScope developer to reduce running databases. Microsoft recommends backing up fewer than 35 databases at once.
Microsoft's knowledge-base:
https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/backup-restore/error-when-you-create-a-snapshot
2) Workaround with ActiveImage Protector:
Set ActiveImage Protector to stop and restart SQL Server services and dependencies during backup.
Backup method for databases not supported by VSS
Remarks:
A high number of SQL Server databases or heavy I/O load can cause SQLWriter to hang or time out. Without LanScope, workarounds can help resolve related SQL errors.
(13451074064281)
Comments
0 comments
Please sign in to leave a comment.