Hi all,
We've got some filers, SRC (6.5.1R1P12) and DEST (6.5.2R1) which are doing snapvaults across a WAN. Someone deleted an active (I think) snapvault snapshot on the source filer to make space. At least they did delete a snapshot on the SRC filer which was our base snapshot for snapvault to the filer DEST.
Currently, I'm seeing the following on the secondary:
# rsh dest snapvault status -l /vol/vol2/src_vol3_proj Snapvault secondary is ON.
Source: src:/vol/vol3/proj Destination: dest:/vol/vol2/src_vol3_proj Status: Quiescing Progress: - State: Snapvaulted Lag: 11:59:33 Mirror Timestamp: Fri Feb 4 01:00:01 PST 2005 Base Snapshot: dest(0050404441)_vol2-base.0 Current Transfer Type: Update Current Transfer Error: base snapshot for transfer no longer exists on the source Contents: Replica Last Transfer Type: Update Last Transfer Size: 1137360 KB Last Transfer Duration: 00:43:47 Last Transfer From: src:/vol/vol3/proj
It's been hung like this for a while now, say 8 hours. The src filer now has a couple of hourly snapvault snapshots online:
# rsh src snap list vol3 Volume vol3 working...
%/used %/total date name ---------- ---------- ------------ -------- 0% ( 0%) 0% ( 0%) Feb 04 16:00 sv_hourly.0 0% ( 0%) 0% ( 0%) Feb 04 15:00 sv_hourly.1
Do I just need to wait for the secondary (an R200) to finish quiescing it's side of things before I can restart the snapvault process? Or do I need to re-do the entire base snapvault all over again?
Thanks, John John Stoffel - Senior Staff Systems Administrator - System LSI Group Toshiba America Electronic Components, Inc. - http://www.toshiba.com/taec john.stoffel@taec.toshiba.com - 508-486-1087