SnapManager for Microsoft SQL Backup doesn't unmount the verification clone DB
- Views:
- 98
- Visibility:
- Public
- Votes:
- 0
- Category:
- snapmanager-for-microsoft-sql-server
- Specialty:
- snapx
- Last Updated:
Applies to
- SnapManager for Microsoft SQL
Issue
- SnapManager for Microsoft SQL backup job with verification enabled leaves stale clones mounted.
- Post database attach, no further task is logged.
Logs:
[06:59:06.117] [xxxx-x-xxxx] Attaching database [DB_xxx_Clone]...
[06:59:07.008] [xxxx-x-xxxx] Database attached.
[06:59:07.008] [xxxx-x-xxxx] DBCC CHECKDB (N'DB_xxx_Clone') WITH NO_INFOMSGS, PHYSICAL_ONLY
- During DBCC CHECKDB task, it gets terminated.
Logs:
2021-10-02 06:59:07.00 spid51 Setting database option AUTO_SHRINK to OFF for database 'DB_xxx_Clone'.
2021-10-02 06:59:40.43 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2021-10-02 06:59:44.37 spid58 DBCC CHECKDB (DB_xxx_Clone) WITH no_infomsgs, physical_only executed by domain\user terminated abnormally due to error state 6. Elapsed time: 0 hours 0 minutes 37 seconds.