These are qtree snapmirrors, yeah? What are you trying to do? Make the targets r/w? Or resync?
On Wed, Mar 25, 2015 at 7:51 PM, Iluhes iluhes@yahoo.com wrote:
From source files XXX (XXX-repl is the replicatin IP)
Source Destination State Lag Status XXX:/vol/zzz/vol06 YYY:/vol/zzz/vol06 Source 151:17:27 Idle XXX:/vol/zzz/vol52 YYY:/vol/zzz/vol52 Source 151:17:30 Idle XXX:/vol/zzz/vol53 YYY:/vol/zzz/vol53 Source 151:17:30 Idle XXX:/vol/zzz/vol56 YYY:/vol/zzz/vol56 Source 151:17:28 Idle XXX:/vol/zzz/vol58 YYY:/vol/zzz/vol58 Source 151:17:30 Idle XXX:/vol/zzz/vol60 YYY:/vol/zzz/vol60 Source 151:17:29 Idle XXX:/vol/zzz/vol62 YYY:/vol/zzz/vol62 Source 151:17:27 Idle XXX:/vol/zzz/vol64 YYY:/vol/zzz/vol64 Source 151:17:28 Idle XXX:/vol/zzz/vol66 YYY:/vol/zzz/vol66 Source 151:17:29 Idle XXX:/vol/zzz/vol68 YYY:/vol/zzz/vol68 Source 151:17:29 Idle XXX:/vol/test1/test1_q YYY:/vol/test1/test1_q Source 00:00:30 Idle XXX:/vol/vol1/yyy YYY:/vol/vol1/yyy Source 00:17:30 Idle
Destination YYY (notice that some of the existing once are still in sync)
Source Destination State Lag Status XXX-rep.fnfis.com:/vol/zzz/vol06 YYY:/vol/zzz/vol06 Snapmirrored 151:16:34 Pending XXX-rep.fnfis.com:/vol/zzz/vol52 YYY:/vol/zzz/vol52 Snapmirrored 151:16:37 Pending XXX-rep.fnfis.com:/vol/zzz/vol53 YYY:/vol/zzz/vol53 Snapmirrored 151:16:37 Pending XXX-rep.fnfis.com:/vol/zzz/vol56 YYY:/vol/zzz/vol56 Snapmirrored 151:16:35 Pending XXX-rep.fnfis.com:/vol/zzz/vol58 YYY:/vol/zzz/vol58 Snapmirrored 151:16:37 Pending XXX-rep.fnfis.com:/vol/zzz/vol60 YYY:/vol/zzz/vol60 Snapmirrored 151:16:36 Pending XXX-rep.fnfis.com:/vol/zzz/vol62 YYY:/vol/zzz/vol62 Snapmirrored 151:16:34 Pending XXX-rep.fnfis.com:/vol/zzz/vol64 YYY:/vol/zzz/vol64 Snapmirrored 151:16:35 Pending XXX-rep.fnfis.com:/vol/zzz/vol66 YYY:/vol/zzz/vol66 Snapmirrored 151:16:36 Transferring XXX-rep.fnfis.com:/vol/zzz/vol68 YYY:/vol/zzz/vol68 Snapmirrored 151:16:36 Pending XXX-rep.fnfis.com:/vol/test1/test1_q YYY:/vol/test1/test1_q Snapmirrored 00:00:37 Idle XXX-rep.fnfis.com:/vol/vol1/yyy YYY:/vol/vol1/yyy Snapmirrored 00:16:37 Idle XXX-rep.fnfis.com:/vol/vol1/nnn YYY:/vol/vol1/nnn Snapmirrored 151:16:37 Idle
On Wednesday, March 25, 2015 6:44 PM, Basil basilberntsen@gmail.com wrote:
Please output the results of snapmirror status (on both filers) as well as snap list volname for a volume you can't break.
On Wed, Mar 25, 2015 at 7:22 PM, Jeff Bryer bryer@sfu.ca wrote:
We have had similar issues with SnapVault (7-mode). Some times we could work around it by disabling SnapVault and aborting the process. Other times we had to create a new relationship and a new baseline.
We haven't seen any issues so far on c-mode, and we have lost connectivity between the cluster peers.
----- Original Message ----- From: "Iluhes" iluhes@yahoo.com To: "Toasters" toasters@teaparty.net Sent: Wednesday, March 25, 2015 3:25:52 PM Subject: snapmirror can notquiesced or broken
snapmirror quiesce: cannot connect to source filer
I can clearly connect to source filer and network connectivity is restored but snapmirrors are stuck and cannot be broken or anything done to them What do I do
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Yes, qtree they were r/w and we tried to put them back in sync, and they are not syncing anymore...it is totaly stuckSource: xxxxDestination: yyyyStatus: PendingProgress: -State: SnapmirroredLag: 150:43:14Mirror Timestamp: Thu Mar 19 11:30:02 CDT 2015Base Snapshot: yyyy(2017123113)_Current Transfer Type: RetryCurrent Transfer Error: cannot connect to source filerContents: TransitioningLast Transfer Type: ScheduledLast Transfer Size: 8 KBLast Transfer Duration: 00:00:02Last Transfer From: xxxxx
On Wednesday, March 25, 2015 7:00 PM, Basil basilberntsen@gmail.com wrote:
These are qtree snapmirrors, yeah? What are you trying to do? Make the targets r/w? Or resync? On Wed, Mar 25, 2015 at 7:51 PM, Iluhes iluhes@yahoo.com wrote:
From source files XXX (XXX-repl is the replicatin IP)
Source Destination State Lag StatusXXX:/vol/zzz/vol06 YYY:/vol/zzz/vol06 Source 151:17:27 IdleXXX:/vol/zzz/vol52 YYY:/vol/zzz/vol52 Source 151:17:30 IdleXXX:/vol/zzz/vol53 YYY:/vol/zzz/vol53 Source 151:17:30 IdleXXX:/vol/zzz/vol56 YYY:/vol/zzz/vol56 Source 151:17:28 IdleXXX:/vol/zzz/vol58 YYY:/vol/zzz/vol58 Source 151:17:30 IdleXXX:/vol/zzz/vol60 YYY:/vol/zzz/vol60 Source 151:17:29 IdleXXX:/vol/zzz/vol62 YYY:/vol/zzz/vol62 Source 151:17:27 IdleXXX:/vol/zzz/vol64 YYY:/vol/zzz/vol64 Source 151:17:28 IdleXXX:/vol/zzz/vol66 YYY:/vol/zzz/vol66 Source 151:17:29 IdleXXX:/vol/zzz/vol68 YYY:/vol/zzz/vol68 Source 151:17:29 IdleXXX:/vol/test1/test1_q YYY:/vol/test1/test1_q Source 00:00:30 IdleXXX:/vol/vol1/yyy YYY:/vol/vol1/yyy Source 00:17:30 Idle Destination YYY (notice that some of the existing once are still in sync) Source Destination State Lag StatusXXX-rep.fnfis.com:/vol/zzz/vol06 YYY:/vol/zzz/vol06 Snapmirrored 151:16:34 PendingXXX-rep.fnfis.com:/vol/zzz/vol52 YYY:/vol/zzz/vol52 Snapmirrored 151:16:37 PendingXXX-rep.fnfis.com:/vol/zzz/vol53 YYY:/vol/zzz/vol53 Snapmirrored 151:16:37 PendingXXX-rep.fnfis.com:/vol/zzz/vol56 YYY:/vol/zzz/vol56 Snapmirrored 151:16:35 PendingXXX-rep.fnfis.com:/vol/zzz/vol58 YYY:/vol/zzz/vol58 Snapmirrored 151:16:37 PendingXXX-rep.fnfis.com:/vol/zzz/vol60 YYY:/vol/zzz/vol60 Snapmirrored 151:16:36 PendingXXX-rep.fnfis.com:/vol/zzz/vol62 YYY:/vol/zzz/vol62 Snapmirrored 151:16:34 PendingXXX-rep.fnfis.com:/vol/zzz/vol64 YYY:/vol/zzz/vol64 Snapmirrored 151:16:35 PendingXXX-rep.fnfis.com:/vol/zzz/vol66 YYY:/vol/zzz/vol66 Snapmirrored 151:16:36 TransferringXXX-rep.fnfis.com:/vol/zzz/vol68 YYY:/vol/zzz/vol68 Snapmirrored 151:16:36 PendingXXX-rep.fnfis.com:/vol/test1/test1_q YYY:/vol/test1/test1_q Snapmirrored 00:00:37 IdleXXX-rep.fnfis.com:/vol/vol1/yyy YYY:/vol/vol1/yyy Snapmirrored 00:16:37 IdleXXX-rep.fnfis.com:/vol/vol1/nnn YYY:/vol/vol1/nnn Snapmirrored 151:16:37 Idle
On Wednesday, March 25, 2015 6:44 PM, Basil basilberntsen@gmail.com wrote:
Please output the results of snapmirror status (on both filers) as well as snap list volname for a volume you can't break. On Wed, Mar 25, 2015 at 7:22 PM, Jeff Bryer bryer@sfu.ca wrote:
We have had similar issues with SnapVault (7-mode). Some times we could work around it by disabling SnapVault and aborting the process. Other times we had to create a new relationship and a new baseline.
We haven't seen any issues so far on c-mode, and we have lost connectivity between the cluster peers.
----- Original Message ----- From: "Iluhes" iluhes@yahoo.com To: "Toasters" toasters@teaparty.net Sent: Wednesday, March 25, 2015 3:25:52 PM Subject: snapmirror can notquiesced or broken
snapmirror quiesce: cannot connect to source filer
I can clearly connect to source filer and network connectivity is restored but snapmirrors are stuck and cannot be broken or anything done to them What do I do
_______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Is there anything in the snapmirror log that might explain what it's stuck on? What's the status of that base snapshot on the primary volume?
On Wed, Mar 25, 2015 at 8:03 PM, Iluhes iluhes@yahoo.com wrote:
Yes, qtree they were r/w and we tried to put them back in sync, and they are not syncing anymore... it is totaly stuck Source: xxxx Destination: yyyy Status: Pending Progress: - State: Snapmirrored Lag: 150:43:14 Mirror Timestamp: Thu Mar 19 11:30:02 CDT 2015 Base Snapshot: yyyy(2017123113)_ Current Transfer Type: Retry Current Transfer Error: cannot connect to source filer Contents: Transitioning Last Transfer Type: Scheduled Last Transfer Size: 8 KB Last Transfer Duration: 00:00:02 Last Transfer From: xxxxx
On Wednesday, March 25, 2015 7:00 PM, Basil basilberntsen@gmail.com wrote:
These are qtree snapmirrors, yeah? What are you trying to do? Make the targets r/w? Or resync?
On Wed, Mar 25, 2015 at 7:51 PM, Iluhes iluhes@yahoo.com wrote:
From source files XXX (XXX-repl is the replicatin IP)
Source Destination State Lag Status XXX:/vol/zzz/vol06 YYY:/vol/zzz/vol06 Source 151:17:27 Idle XXX:/vol/zzz/vol52 YYY:/vol/zzz/vol52 Source 151:17:30 Idle XXX:/vol/zzz/vol53 YYY:/vol/zzz/vol53 Source 151:17:30 Idle XXX:/vol/zzz/vol56 YYY:/vol/zzz/vol56 Source 151:17:28 Idle XXX:/vol/zzz/vol58 YYY:/vol/zzz/vol58 Source 151:17:30 Idle XXX:/vol/zzz/vol60 YYY:/vol/zzz/vol60 Source 151:17:29 Idle XXX:/vol/zzz/vol62 YYY:/vol/zzz/vol62 Source 151:17:27 Idle XXX:/vol/zzz/vol64 YYY:/vol/zzz/vol64 Source 151:17:28 Idle XXX:/vol/zzz/vol66 YYY:/vol/zzz/vol66 Source 151:17:29 Idle XXX:/vol/zzz/vol68 YYY:/vol/zzz/vol68 Source 151:17:29 Idle XXX:/vol/test1/test1_q YYY:/vol/test1/test1_q Source 00:00:30 Idle XXX:/vol/vol1/yyy YYY:/vol/vol1/yyy Source 00:17:30 Idle
Destination YYY (notice that some of the existing once are still in sync)
Source Destination State Lag Status XXX-rep.fnfis.com:/vol/zzz/vol06 YYY:/vol/zzz/vol06 Snapmirrored 151:16:34 Pending XXX-rep.fnfis.com:/vol/zzz/vol52 YYY:/vol/zzz/vol52 Snapmirrored 151:16:37 Pending XXX-rep.fnfis.com:/vol/zzz/vol53 YYY:/vol/zzz/vol53 Snapmirrored 151:16:37 Pending XXX-rep.fnfis.com:/vol/zzz/vol56 YYY:/vol/zzz/vol56 Snapmirrored 151:16:35 Pending XXX-rep.fnfis.com:/vol/zzz/vol58 YYY:/vol/zzz/vol58 Snapmirrored 151:16:37 Pending XXX-rep.fnfis.com:/vol/zzz/vol60 YYY:/vol/zzz/vol60 Snapmirrored 151:16:36 Pending XXX-rep.fnfis.com:/vol/zzz/vol62 YYY:/vol/zzz/vol62 Snapmirrored 151:16:34 Pending XXX-rep.fnfis.com:/vol/zzz/vol64 YYY:/vol/zzz/vol64 Snapmirrored 151:16:35 Pending XXX-rep.fnfis.com:/vol/zzz/vol66 YYY:/vol/zzz/vol66 Snapmirrored 151:16:36 Transferring XXX-rep.fnfis.com:/vol/zzz/vol68 YYY:/vol/zzz/vol68 Snapmirrored 151:16:36 Pending XXX-rep.fnfis.com:/vol/test1/test1_q YYY:/vol/test1/test1_q Snapmirrored 00:00:37 Idle XXX-rep.fnfis.com:/vol/vol1/yyy YYY:/vol/vol1/yyy Snapmirrored 00:16:37 Idle XXX-rep.fnfis.com:/vol/vol1/nnn YYY:/vol/vol1/nnn Snapmirrored 151:16:37 Idle
On Wednesday, March 25, 2015 6:44 PM, Basil basilberntsen@gmail.com wrote:
Please output the results of snapmirror status (on both filers) as well as snap list volname for a volume you can't break.
On Wed, Mar 25, 2015 at 7:22 PM, Jeff Bryer bryer@sfu.ca wrote:
We have had similar issues with SnapVault (7-mode). Some times we could work around it by disabling SnapVault and aborting the process. Other times we had to create a new relationship and a new baseline.
We haven't seen any issues so far on c-mode, and we have lost connectivity between the cluster peers.
----- Original Message ----- From: "Iluhes" iluhes@yahoo.com To: "Toasters" toasters@teaparty.net Sent: Wednesday, March 25, 2015 3:25:52 PM Subject: snapmirror can notquiesced or broken
snapmirror quiesce: cannot connect to source filer
I can clearly connect to source filer and network connectivity is restored but snapmirrors are stuck and cannot be broken or anything done to them What do I do
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Yes, /vol/vol0/etc/log/snapmirror
You should check our options snapmirror.access and if applicable, /etc/snapmirror.allow settings.
Is XXX in a different subnet than XXX-rep.fnfis.com? perhaps it is not routing the way you are expecting?
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Basil Sent: Wednesday, March 25, 2015 9:49 PM To: Iluhes Cc: toasters@teaparty.net Subject: Re: snapmirror can notquiesced or broken
Is there anything in the snapmirror log that might explain what it's stuck on? What's the status of that base snapshot on the primary volume?
On Wed, Mar 25, 2015 at 8:03 PM, Iluhes <iluhes@yahoo.commailto:iluhes@yahoo.com> wrote: Yes, qtree they were r/w and we tried to put them back in sync, and they are not syncing anymore... it is totaly stuck Source: xxxx Destination: yyyy Status: Pending Progress: - State: Snapmirrored Lag: 150:43:14 Mirror Timestamp: Thu Mar 19 11:30:02 CDT 2015 Base Snapshot: yyyy(2017123113tel:%282017123113)_ Current Transfer Type: Retry Current Transfer Error: cannot connect to source filer Contents: Transitioning Last Transfer Type: Scheduled Last Transfer Size: 8 KB Last Transfer Duration: 00:00:02 Last Transfer From: xxxxx
On Wednesday, March 25, 2015 7:00 PM, Basil <basilberntsen@gmail.commailto:basilberntsen@gmail.com> wrote:
These are qtree snapmirrors, yeah? What are you trying to do? Make the targets r/w? Or resync?
On Wed, Mar 25, 2015 at 7:51 PM, Iluhes <iluhes@yahoo.commailto:iluhes@yahoo.com> wrote: From source files XXX (XXX-repl is the replicatin IP)
Source Destination State Lag Status XXX:/vol/zzz/vol06 YYY:/vol/zzz/vol06 Source 151:17:27 Idle XXX:/vol/zzz/vol52 YYY:/vol/zzz/vol52 Source 151:17:30 Idle XXX:/vol/zzz/vol53 YYY:/vol/zzz/vol53 Source 151:17:30 Idle XXX:/vol/zzz/vol56 YYY:/vol/zzz/vol56 Source 151:17:28 Idle XXX:/vol/zzz/vol58 YYY:/vol/zzz/vol58 Source 151:17:30 Idle XXX:/vol/zzz/vol60 YYY:/vol/zzz/vol60 Source 151:17:29 Idle XXX:/vol/zzz/vol62 YYY:/vol/zzz/vol62 Source 151:17:27 Idle XXX:/vol/zzz/vol64 YYY:/vol/zzz/vol64 Source 151:17:28 Idle XXX:/vol/zzz/vol66 YYY:/vol/zzz/vol66 Source 151:17:29 Idle XXX:/vol/zzz/vol68 YYY:/vol/zzz/vol68 Source 151:17:29 Idle XXX:/vol/test1/test1_q YYY:/vol/test1/test1_q Source 00:00:30 Idle XXX:/vol/vol1/yyy YYY:/vol/vol1/yyy Source 00:17:30 Idle
Destination YYY (notice that some of the existing once are still in sync)
Source Destination State Lag Status XXX-rep.fnfis.com:/vol/zzz/vol06 YYY:/vol/zzz/vol06 Snapmirrored 151:16:34 Pending XXX-rep.fnfis.com:/vol/zzz/vol52 YYY:/vol/zzz/vol52 Snapmirrored 151:16:37 Pending XXX-rep.fnfis.com:/vol/zzz/vol53 YYY:/vol/zzz/vol53 Snapmirrored 151:16:37 Pending XXX-rep.fnfis.com:/vol/zzz/vol56 YYY:/vol/zzz/vol56 Snapmirrored 151:16:35 Pending XXX-rep.fnfis.com:/vol/zzz/vol58 YYY:/vol/zzz/vol58 Snapmirrored 151:16:37 Pending XXX-rep.fnfis.com:/vol/zzz/vol60 YYY:/vol/zzz/vol60 Snapmirrored 151:16:36 Pending XXX-rep.fnfis.com:/vol/zzz/vol62 YYY:/vol/zzz/vol62 Snapmirrored 151:16:34 Pending XXX-rep.fnfis.com:/vol/zzz/vol64 YYY:/vol/zzz/vol64 Snapmirrored 151:16:35 Pending XXX-rep.fnfis.com:/vol/zzz/vol66 YYY:/vol/zzz/vol66 Snapmirrored 151:16:36 Transferring XXX-rep.fnfis.com:/vol/zzz/vol68 YYY:/vol/zzz/vol68 Snapmirrored 151:16:36 Pending XXX-rep.fnfis.com:/vol/test1/test1_q YYY:/vol/test1/test1_q Snapmirrored 00:00:37 Idle XXX-rep.fnfis.com:/vol/vol1/yyy YYY:/vol/vol1/yyy Snapmirrored 00:16:37 Idle XXX-rep.fnfis.com:/vol/vol1/nnn YYY:/vol/vol1/nnn Snapmirrored 151:16:37 Idle
On Wednesday, March 25, 2015 6:44 PM, Basil <basilberntsen@gmail.commailto:basilberntsen@gmail.com> wrote:
Please output the results of snapmirror status (on both filers) as well as snap list volname for a volume you can't break.
On Wed, Mar 25, 2015 at 7:22 PM, Jeff Bryer <bryer@sfu.camailto:bryer@sfu.ca> wrote: We have had similar issues with SnapVault (7-mode). Some times we could work around it by disabling SnapVault and aborting the process. Other times we had to create a new relationship and a new baseline.
We haven't seen any issues so far on c-mode, and we have lost connectivity between the cluster peers.
----- Original Message ----- From: "Iluhes" <iluhes@yahoo.commailto:iluhes@yahoo.com> To: "Toasters" <toasters@teaparty.netmailto:toasters@teaparty.net> Sent: Wednesday, March 25, 2015 3:25:52 PM Subject: snapmirror can notquiesced or broken
snapmirror quiesce: cannot connect to source filer
I can clearly connect to source filer and network connectivity is restored but snapmirrors are stuck and cannot be broken or anything done to them What do I do
_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
I will check but so far the only error, cannot connect to source. But unbroken mirror continue to work to same array and network is there. Quisce command fails with the same error, it cannot connect to source
On Mar 25, 2015, at 8:48 PM, Basil basilberntsen@gmail.com wrote:
Is there anything in the snapmirror log that might explain what it's stuck on? What's the status of that base snapshot on the primary volume?
On Wed, Mar 25, 2015 at 8:03 PM, Iluhes iluhes@yahoo.com wrote: Yes, qtree they were r/w and we tried to put them back in sync, and they are not syncing anymore... it is totaly stuck Source: xxxx Destination: yyyy Status: Pending Progress: - State: Snapmirrored Lag: 150:43:14 Mirror Timestamp: Thu Mar 19 11:30:02 CDT 2015 Base Snapshot: yyyy(2017123113)_ Current Transfer Type: Retry Current Transfer Error: cannot connect to source filer Contents: Transitioning Last Transfer Type: Scheduled Last Transfer Size: 8 KB Last Transfer Duration: 00:00:02 Last Transfer From: xxxxx
On Wednesday, March 25, 2015 7:00 PM, Basil basilberntsen@gmail.com wrote:
These are qtree snapmirrors, yeah? What are you trying to do? Make the targets r/w? Or resync?
On Wed, Mar 25, 2015 at 7:51 PM, Iluhes iluhes@yahoo.com wrote: From source files XXX (XXX-repl is the replicatin IP)
Source Destination State Lag Status XXX:/vol/zzz/vol06 YYY:/vol/zzz/vol06 Source 151:17:27 Idle XXX:/vol/zzz/vol52 YYY:/vol/zzz/vol52 Source 151:17:30 Idle XXX:/vol/zzz/vol53 YYY:/vol/zzz/vol53 Source 151:17:30 Idle XXX:/vol/zzz/vol56 YYY:/vol/zzz/vol56 Source 151:17:28 Idle XXX:/vol/zzz/vol58 YYY:/vol/zzz/vol58 Source 151:17:30 Idle XXX:/vol/zzz/vol60 YYY:/vol/zzz/vol60 Source 151:17:29 Idle XXX:/vol/zzz/vol62 YYY:/vol/zzz/vol62 Source 151:17:27 Idle XXX:/vol/zzz/vol64 YYY:/vol/zzz/vol64 Source 151:17:28 Idle XXX:/vol/zzz/vol66 YYY:/vol/zzz/vol66 Source 151:17:29 Idle XXX:/vol/zzz/vol68 YYY:/vol/zzz/vol68 Source 151:17:29 Idle XXX:/vol/test1/test1_q YYY:/vol/test1/test1_q Source 00:00:30 Idle XXX:/vol/vol1/yyy YYY:/vol/vol1/yyy Source 00:17:30 Idle
Destination YYY (notice that some of the existing once are still in sync)
Source Destination State Lag Status XXX-rep.fnfis.com:/vol/zzz/vol06 YYY:/vol/zzz/vol06 Snapmirrored 151:16:34 Pending XXX-rep.fnfis.com:/vol/zzz/vol52 YYY:/vol/zzz/vol52 Snapmirrored 151:16:37 Pending XXX-rep.fnfis.com:/vol/zzz/vol53 YYY:/vol/zzz/vol53 Snapmirrored 151:16:37 Pending XXX-rep.fnfis.com:/vol/zzz/vol56 YYY:/vol/zzz/vol56 Snapmirrored 151:16:35 Pending XXX-rep.fnfis.com:/vol/zzz/vol58 YYY:/vol/zzz/vol58 Snapmirrored 151:16:37 Pending XXX-rep.fnfis.com:/vol/zzz/vol60 YYY:/vol/zzz/vol60 Snapmirrored 151:16:36 Pending XXX-rep.fnfis.com:/vol/zzz/vol62 YYY:/vol/zzz/vol62 Snapmirrored 151:16:34 Pending XXX-rep.fnfis.com:/vol/zzz/vol64 YYY:/vol/zzz/vol64 Snapmirrored 151:16:35 Pending XXX-rep.fnfis.com:/vol/zzz/vol66 YYY:/vol/zzz/vol66 Snapmirrored 151:16:36 Transferring XXX-rep.fnfis.com:/vol/zzz/vol68 YYY:/vol/zzz/vol68 Snapmirrored 151:16:36 Pending XXX-rep.fnfis.com:/vol/test1/test1_q YYY:/vol/test1/test1_q Snapmirrored 00:00:37 Idle XXX-rep.fnfis.com:/vol/vol1/yyy YYY:/vol/vol1/yyy Snapmirrored 00:16:37 Idle XXX-rep.fnfis.com:/vol/vol1/nnn YYY:/vol/vol1/nnn Snapmirrored 151:16:37 Idle
On Wednesday, March 25, 2015 6:44 PM, Basil basilberntsen@gmail.com wrote:
Please output the results of snapmirror status (on both filers) as well as snap list volname for a volume you can't break.
On Wed, Mar 25, 2015 at 7:22 PM, Jeff Bryer bryer@sfu.ca wrote: We have had similar issues with SnapVault (7-mode). Some times we could work around it by disabling SnapVault and aborting the process. Other times we had to create a new relationship and a new baseline.
We haven't seen any issues so far on c-mode, and we have lost connectivity between the cluster peers.
----- Original Message ----- From: "Iluhes" iluhes@yahoo.com To: "Toasters" toasters@teaparty.net Sent: Wednesday, March 25, 2015 3:25:52 PM Subject: snapmirror can notquiesced or broken
snapmirror quiesce: cannot connect to source filer
I can clearly connect to source filer and network connectivity is restored but snapmirrors are stuck and cannot be broken or anything done to them What do I do
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters