ONTAP Hardware

Strange error on NetAPP when executing Reprotect task using SRA.

JURISKR
4,448 Views

Anybody can help with Storage Replication Adapter for VMWare SRM. I was successfully failover sites using Vmware SRM + SRA. But when I do reprotect task it fails. When SRM execute SRA functions on my NetAPP console I see following messages:

Tue Aug 12 09:42:22 GMT [riga-na-a:api_mpool_08:warning]: registry: Unexpected error in rollback in regx_commit - Error: No such file or directory (name=options.files.snapmirror.conf.riga-na-a:rdm)

Tue Aug 12 09:42:22 GMT [riga-na-a:api_mpool_04:warning]: registry: Unexpected error in rollback in regx_commit - Error: No such file or directory (name=options.files.snapmirror.conf.riga-na-a:rdm)

Tue Aug 12 09:42:23 GMT [riga-na-a:api_mpool_00:warning]: registry: Unexpected error in rollback in regx_commit - Error: No such file or directory (name=options.files.snapmirror.conf.riga-na-a:rdm)

Tue Aug 12 09:42:24 GMT [riga-na-a:api_mpool_06:warning]: registry: Unexpected error in rollback in regx_commit - Error: No such file or directory (name=options.files.snapmirror.conf.riga-na-a:rdm)

Tue Aug 12 09:42:24 GMT [riga-na-a:api_mpool_02:warning]: registry: Unexpected error in rollback in regx_commit - Error: No such file or directory (name=options.files.snapmirror.conf.riga-na-a:rdm)

Tue Aug 12 09:42:25 GMT [riga-na-a:api_mpool_08:warning]: registry: Unexpected error in rollback in regx_commit - Error: No such file or directory (name=options.files.snapmirror.conf.riga-na-a:rdm)

Tue Aug 12 09:42:26 GMT [riga-na-a:api_mpool_03:warning]: registry: Unexpected error in rollback in regx_commit - Error: No such file or directory (name=options.files.snapmirror.conf.riga-na-a:sqllog)

And this is the message I get from SRA "Error - Failed to reverse replication for failed over devices. SRA command 'prepareReverseReplication' failed. Address of the storage array is not reachable. Storage array might be down or IP address entered might be incorrect. Ensure that the storage array is up and running and the IP address of the storage array is reachable through the command line interface."

Have somebody experienced with behavior. I'm using SRA 2.1.

Thanks in advance.

4 REPLIES 4

VKALVEMULA
4,448 Views

send the o/p of "options httpd"

JURISKR
4,448 Views
httpd.access             legacy
httpd.admin.access       legacy
httpd.admin.enable       off

httpd.admin.hostsequiv.enable off

httpd.admin.max_connections  512

httpd.admin.ssl.enable   on

httpd.admin.top-page.authentication on

httpd.autoindex.enable   off

httpd.bypass_traverse_checking off

httpd.enable             off
httpd.ipv6.enable        off
httpd.log.format         common (value might be overwritten in takeover)
httpd.method.trace.enableoff
httpd.rootdir            /vol/vol0/home/http
httpd.timeout            300    (value might be overwritten in takeover)
httpd.timewait.enable    off    (value might be overwritten in takeover)

VKALVEMULA
4,448 Views

turn on httpd.enable to ON on all filers which are part of SRM / SRA.

" options httpd.enable on "

andylingley
4,448 Views

Hi Juriskr, you've not provided much detail of your environment or the servers that you're having issues with, so I don't know whether this will be of any assistance to you or not, but we had these errors when trying to reprotect one of our SQL servers.

The root cause of our issue was that we needed to update the vCenter server setting within SnapDrive to point to the vCenter on the recovery site, as we were using iSCSI RDM LUN's.  Without that update, SnapDrive wasn't able to enumerate the LUNS, even though they were connected to the server and therefore SMSQL couldn't start.  Once resolved that, were able to get the SMSQL service running and we were then able to reprotect the server with no problems.  We have also been able to replicate/prove this behavior with other servers as well.

Good Luck!

Public