Skip to main content
NetApp adopts Microsoft’s Business-to-Customer (B2C) Identity Management
Effective December 3 - NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources. For accounts that did not pre-register (prior to Dec 3) access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity. To learn more, Read the FAQ and Watch the video. Need assistance? Complete this form and select “Registration Issue” as the Feedback Category. 
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

Views:
133
Visibility:
Public
Votes:
0
Category:
snapmanager-for-sap
Specialty:
snapx
Last Updated:

Applies to

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

Issue

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.

 

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