Skip to main content
NetApp Knowledge Base

SMO/SMSAP, during an unmount error from verification, aborts and deletes the backup

  1. Last updated
  2. Save as PDF
Views:
115
Visibility:
Public
Votes:
3
Category:
snapmanager-for-oracle
Specialty:
legacy
Last Updated:

Applies to

  • SnapManager for Oracle (SMO) 3.4.2 for Windows
  • SnapDrive for Windows (SDW) 7.1.5(Px)

Issue

When SnapManager uses SnapDrive to unmount the clone used to verify the backup, ocassionally the following error occurs:
[ERROR]: FLOW-11019: Failure in Disconnect: SD-00033: Error disconnecting filesystem(s) [<DISK_MOUNT_LIST>]":The service has returned a service-specific error code
 
Possibly followed by:
[DEBUG]: CON-00011: Not disconnecting C:\SnapManager_auto_mounts\H-20210106190739582_0 (File System) because it does not exist.
 
Despite this being an issue around verification of a healthy backup and healthy Oracle DBCC run on the clone, the backup is aborted and deleted:
[INFO ]: SMO-13039: Successfully aborted operation: Backup Create
[ERROR]: SMO-13048: Backup Create Operation Status: FAILED

 

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.