Skip to main content
NetApp Knowledge Base

How to configure SMO clone to destination where interactive password entry is not required

Last Updated:

Applies to

SnapManager for Oracle (SMO)


When cloning to remote secondary host workflows are processed by command line batch jobs, SMO will prompt for the destination host's password.  To avoid the interactive session, the secondary host password can be cached to the primary host, and allows batch jobs to proceed without interuption.


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.
Scan to view the article on your device