Storage Replication Adapter (SRA): SRA commands run slower than

they did at initial setup

https://kb.netapp.com/mgmt/OTV/SRA/Storage_Replication_Adapter_(SRA)%3A_SRA_commands_run…
Updated: Fri, 10 Nov 2023 09:55:58 GMT

Applies to
• Storage Replication Adapter (SRA) 7.x
• Storage Replication Adapter 9.6x
• Storage Replication Adapter 9.7, 9.7P1
• VMware Site Recovery Manager (SRM)

Issue
• You are running a version of SRA that is susceptible to this issue
◦ SRA 7.x

'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 1
techniques herein is a customers responsibility and depends on the customers ability to evaluate and integrate them into the customers operational
environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this
document.'
 ◦ SRA 9.6x
◦ SRA 9.7, SRA 9.7P1
• SRA commands run slower over time.
• In SRM, you may see new errors like Timed out (300 seconds) while waiting for SRA to
complete <command> command.

Cause

The SRA database on one or both sites is filled with hosed items.

To confirm this, perform the following steps:

1. Logon to the SRA web CLI at https://<your SRA IP>:9083. When prompted for a login, use the
SRA administrator credentials.

Example:

2. Open the Inventory link.

3. Check the number of hosed items in the Hosed Items section of the Table of Contents.

Example:

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 2
 If the number of hosed items is several hundred or higher, proceed with the solution in this article.

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 3
 Solution

Enable the automatic deletion of hosed items.

Note: This feature was introduced in SRA 9.7P2. If you are running an earlier version of SRA, you must upgrade
the environment before following the steps below. If you cannot run SRA 9.7P2 at this time, follow the
workaround under the solution Manually clean out and repopulate the SRA database.

1. Logon to the SRA web CLI at https://<your SRA IP>:9083. When prompted for a login, use the
SRA administrator credentials.
2. Open the Web Based CLI Interface.
3. Run the command vp updateconfig -key=delete.hosed.entries -value=true to set the
automatic deletion flag.

Example:

4. Run the command vp reloadconfig to push the update.

Example:

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 4
 5. Run the command cluster rediscover to launch a rediscovery and clean up the hosed entries.

Example:

Manually clean out and repopulate the SRA database.

If you use VASA VVOLs or custom storage capability profiles, do not perform the following solution.
Additional steps are needed to restore VVOL metadata and custom storage capability profile entries. The
procedure for resetting the database and restoring metadata for VVOLs is outlined in How to reset VASA
Provider and SRA database

If you do not use VASA VVOLs or custom storage capability profiles and cannot upgrade to SRA 9.7P2, follow
the steps below.

1. Logon to the Unified Appliance (VSC/SRA/VASA) VM console as the maint user.

2. Open the Application Configuration menu.

Example:

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 5
 3. Hard reset the database with option 9.

Example:

4. Perform a rediscovery in VSC.

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 6
 Example:

Additional Information

For more information on adjusting SRM storage command timeouts, refer to the NetApp KB Storage Replication
Adapter (SRA): Operation timed out after 300 seconds.

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 7