メインコンテンツまでスキップ

SnapManager for Microsoft SQL Backup では、検証クローン DB がアンマウントされません

Views:
16
Visibility:
Public
Votes:
1
Category:
snapmanager-for-microsoft-sql-server<a>SnapManager</a><a>2008869503</a><a>(翻訳用</a>
Specialty:
snapx
Last Updated:

環境

  • SnapManager for Microsoft SQL

問題

  • 検証を有効にした SnapManager for Microsoft SQL のバックアップジョブで、古いクローンがマウントされたままになります。
  • データベース接続後、以降のタスクはログに記録されません。 

ログ

[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

 

  • DBCC CHECKDB タスク中に終了します。

ログ

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.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.