Skip to main content
NetApp Knowledge Base

BRBackup, smo backup, or smsap backup fails in SMO or SMSAP due to missing profile-to-repository mapping in the credential cache

Last Updated:

Applies to

  • SnapManager for SAP (SMSAP) 3.4.x
  • SnapManager for Oracle (SMO) 3.4.x


When attempting to run a backup through the BR*Tools SMSAP, or issuing a backup command with either SMSAP or SMO, it fails with the error:

[ERROR] SMSAP-20006: There is no profile->repository mapping defined for profile "<SM_PROFILE>" in credentials cache 
for OS user "<OS_USER>". If profile "<SM_PROFILE>" actually exists, run "profile sync" against the repository in 
which that profile is contained.


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.