Hi toasters,
we have seen several times where a snapvault destination gets filled up to 100% while an update on the sv-relation was running.
Afterwards we see the snapvault relation in a quiescing mode. Doing some slow transfer:
source:/vol/exvs13_db/mb1_3_sg1 destination:/vol/pdbnab5_v002/mb2_3_sg1 Snapvaulted 82:41:00 Quiescing (27 GB done)
In the logs i see this:
snapvault: vol=pdbnab5_v002 snapshot= op=2, giving up on update of /vol/pdbnab5_v002/mb2_3_sg1: could not read from socket
When i abort the snapvault relation i see this:
nstore1> snapvault abort nstore1:/vol/pdbnab5_v002/mb2_3_sg1 nstore1> Tue Aug 26 09:31:50 CEST [worker_thread_729:notice]: snapmirror: Network communication error
And snapvault status shows the qtree in normal quiescing again, but it starts soon again to do a transfer.
Has anybody ever come across this and has a solution?
Regards and thanks in advance
Jochen