跳转到主内容

如果存储克隆失败,则 SCO 不会清理为编目而创建的数据库克隆

Views:
6
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

适用于

  • 适用于 Oracle 的 SnapCenter 插件( SCO )
  • Oracle Automatic Storage Management (ASM)

问题

在设置数据库和归档日志克隆以进行编目时,对数据库或归档日志文件系统进行 ONTAP 克隆失败,并出现 HTTP ( S )超时:

Critical SAL PID=[12468] TID=[8524] The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop:
      Connection to <SVM_FQDN> on port 443 for protocol HTTPS timed out.
      at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
      at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
      at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

Error SAL PID=[12468] TID=[8524] Failed to create volume clone

这会使克隆的卷(及其包含的 LUN )处于未映射状态,因为它们不会在失败的目录编制过程中被清理。

此外,在同一操作中,在失败之前成功执行的任何额外基于 LUN 的数据库或归档日志克隆仍会与备份主机上标记为现有 ASM 磁盘组的设备进行映射,从而可能会在下次备份时导致更多磁盘 /ASM 冲突。

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support