MS SQL
| Category | Exception | Description | Action | Severity |
|---|---|---|---|---|
| MS SQL | fault.mssql.dSource.validated_sync.failed | Validated sync for the dSource failed | Validated sync for dSource “{0}” failed with the error: | Review the error. Additional recommendation(s): |
| MS SQL | fault.mssql.source.backupfile.not_found | Backup file for the source database was not found in the backup locations | For dSource “{0}”, backup file “{1}” was not found in the backup locations [{2}]. |
Make sure the backup locations are correct and the user “{3}” has the required read privileges on them. |
| MS SQL | fault.mssql.source.logchainbreak | Source database has had a log chain break | Failed to ingest the transaction log backup with UUID “{0}” over the last restored backup with UUID “{1}” due to a log chain break on the source database “{2}”. Restore from a full or differential database backup is needed to continue. |
Perform a sync on the dSource to restore a full or differential database backup. |
| MS SQL | fault.mssql.source.next.backup.missing | Next backup to restore cannot be found | The next backup to be restored for dSource “{0}” was not found in the msdb.dbo.backupset table. |
Locate the missing backup file(s) between last restored backup (with first LSN: “{1}”, last LSN: “{2}”, UUID: “{3}”, start time: “{4}”, end time: “{5}”) and the next backup (with first LSN: “{6}”, last LSN: “{7}”, UUID: “{8}”, start time: “{9}”, end time: “{10}”). For each missing backup, run query “RESTORE VERIFYONLY FROM DISK = ‘ msdb.dbo.backupset and run the operation again. Otherwise perform a sync on the dSource to continue pulling new changes from the source database. |
| MS SQL | fault.mssql.source.recovery.fork.guid.changed | The recovery fork GUID of the source database has changed from “{0}” to “{1}” | Detected a change in recovery fork GUID for source database “{2}”. | Perform a manual sync on the dSource using a full or differential database backup from the new recovery fork GUID in order to resume validated sync. |
| MS SQL | fault.mssql.source.valid.backupfile.not_found | No valid database backup file for the source database was found in the backup locations |
For dSource “{0}”, no valid database backup file “{1}” was found in the backup locations [{2}]. Following invalid files were found: [{3}] |
Make sure the backup files are not corrupted, backup locations are correct and the user “{4}” has the required read privileges on them. Resolve the errors seen for the files and try the operation again. |
| MS SQL | fault.mssql.staging_host.litespeed.notfound | LiteSpeed installation was not found on the staging host | For dSource “{0}”, LiteSpeed version “{1}” or higher needs to be installed on the staging host “{2}” to restore source database backups taken with LiteSpeed. |
Install LiteSpeed on the host, refresh the environment, and try again. |
| MS SQL | fault.mssql.stagingdb.grant_permissions.failed | Granting user permissions on staging database files failed | Failed to grant user “{0}” permissions on directory “{1}” on the staging host “{2}”: |
Make sure that the user has permissions to access the staging database files on the staging host. |
| MS SQL | fault.mssql.stagingdb.restore.failed | Restore of source database backup failed | Restore of backup with UUID “{0}” for source “{1}” failed on the staging host “{2}”: {3}. |
Make sure that the backup is not corrupt, the backup locations for the dSource [{4}] are correct, the SQL Server instance “{5}” on the staging host is up and that user “{6}” has privileges to restore a database on the host. If the problem does not resolve, perform a sync on the dSource to restore a full database backup. |
| MS SQL | fault.mssql.vdb.status.nonoperational | VDB “{0}”, was found to be nonoperational | The VDB is not able to access its storage. Reads and writes to the VDB might fail. | Make sure that the environment on which this VDB is provisioned does not report critical faults. Make sure that the network between the host “{1}” and the Delphix Engine is stable and start the VDB. If starting the VDB fails, try restarting the SQL Server instance and starting the VDB again. Otherwise contact Delphix Support. |