PLEAES DISREGARD MY ALL PREVIOUS MESSAGES. I DO NOT WANT ANY FEEDBACK
From: Uddhav Regmi [mailto:uregmi111@gmail.com]
Sent: Sunday, December 09, 2012 12:04 PM
To: 'Cruxrealm'; 'toasters@teaparty.net'
Subject: RE: snapmirror socket error :vfiler dr configure : 8.1
Here is the file
na021> rdfile /etc/snapmirror.conf
#Regenerated by registry Thu Dec 6 18:44:27 GMT 2012
na002-sm:vfdoleprd02_db201 na021:vfdoleprd02_db201 - 0-59/1 * * * na002-sm:vfdoleprd02root na021:vfdoleprd02root - 0-59/3 * * *
na021> snapmirror status
Snapmirror is on.
Source Destination State Lag S tatus
na002-sm:vfdoleprd02_db201 na021:vfdoleprd02_db201 Uninitialized - I dle
na002-sm:vfdoleprd02root na021:vfdoleprd02root Uninitialized - I dle
na021> snapmirror status
Snapmirror is on.
Source Destination State Lag Status
na002-sm:vfdoleprd02_db201 na021:vfdoleprd02_db201 Uninitialized - Idle
na002-sm:vfdoleprd02root na021:vfdoleprd02root Uninitialized - Idle
From: Cruxrealm [mailto:cruxrealm@aol.com]
Sent: Sunday, December 09, 2012 11:55 AM
To: Uddhav Regmi
Subject: Re: snapmirror socket error :vfiler dr configure : 8.1
Try to do a test replication snapmirror from your source and destination. If that works, then check your conf file.
Sent from my iPad
On Dec 9, 2012, at 8:28 AM, "Uddhav Regmi" <uregmi111@gmail.com> wrote:
snapmirror socket error
na002 - > na009 ( snapmirror now happening ) source - > dr
both are 8.1 ; mirror is happening every 30 min
vfiler in na009 is in stopped condition. Aggregate got full here, so we decided to move the dr volume to another filer
I did
vfiler dr configure command and vol got moved to another box na021
all looks good, vfiler got created. snapmirror was in unitialized state
when I start snapmirror : I'm getting this weired error
na021> vol restrict vfdoleprd02_db201
Thu Dec 6 15:57:24 EST [na021:vFiler.storageUnit.off:warning]: vFiler vfdoleprd02: storage unit /vol/vfdoleprd02_db201 now offline.
Volume 'vfdoleprd02_db201' is now restricted.
na021> snapmirror initialize -S na002-sm:vfdoleprd02_db201 na021:vfdoleprd02_db201
Transfer aborted: could not read from socket.
na021> Thu Dec 6 15:57:41 EST [na021:replication.dst.err:error]: SnapMirror: destination transfer from na002-sm:vfdoleprd02_db201 to vfdoleprd02_db201 : could not read from socket.
na021> snapmirror statusThu Dec 6 15:58:00 EST [na021:replication.dst.err:error]: SnapMirror: destination transfer from na002-sm:vfdoleprd02_db201 to vfdoleprd02_db201 : volume is not online; cannot execute operation.
Snapmirror is on.
Source Destination State Lag Status
na002-sm:vfdoleprd02_db201 na021:vfdoleprd02_db201 Unknown - Pending
na002-sm:vfdoleprd02root na021:vfdoleprd02root Uninitialized - Idle
na021> snapmirror status -l na021:vfdoleprd02_db201
Snapmirror is on.
Source: na002-sm:vfdoleprd02_db201
Destination: na021:vfdoleprd02_db201
Status: Pending
Progress: -
State: Unknown
Lag: -
Mirror Timestamp: -
Base Snapshot: -
Current Transfer Type: Scheduled
Current Transfer Error: volume is not online; cannot execute operation
Contents: -
Last Transfer Type: -
Last Transfer Size: -
Last Transfer Duration: -
Last Transfer From: -
na021>
any idea what is going on here ????
snapmirror.access list is fine
My thought is : do we need to break the original mirror ????? which was going from na002 to na009
_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters