I have a Celerra NX4 with AX4-5F8 backend at both my production site and DR site.

One of the filesystems stopped replicating over the weekend because the storage pool was filled up and savvol could not extend.  I was able to reclaim a lot of space on this storage pool and there is now plenty of free, unalocated space for it to expand to.

However I cannot get this replication restarted again.  It is stopped on the destination side and errored out on the source side.

Source Status                  = Info 26045317429: Stopped

Network Status                 = OK

Destination Status             = Info 26045317495: Replication session state is not accessible.

In the GUI if I try to start I get this: No common base exists for the source and destination version sets.

I read a primus article that said to try the -overwrite_destination flag so in CLI I tried this but got the same result:

nas_replicate -start vm3-sas-replication -overwrite_destion

Error 13160416232: No common base exists for the source and destination.

This has replicated before, I believe last Friday it completed a replication and during it's second transfter over the weekend that's when it failed.  I know the data is there and good until last friday at the DR site.  Is there any way to get this restarted without resorting to a desructive full copy?  Taking 2 TB over a 30mbps wan with other traffic going over it will mean the replicated filesystem won't be available for a good month.  Since I know there is data already there on the destination, I want to just replicate from this point on (last friday).

I'm runing 6.0.51-6 on the front end.