Are you in the initial stages of setting up the replication sessions? Or was this session already established and suddenly it is throwing the mentioned error?
Either way, the filesystems being paired up need not only to be the same size and the target filesystem mounted R/O (yes, we all know these points), but the features that are enabled on the source (that are inherent to the filesystem definition) needs to be set similarly between the two.
In this example, the error suggests either of the following requirements are not met:
1) The target filesystem (on the Celerra) is not set to R/O
2) The same FLR setting (enabled/disabled, FLR-C or FLR-E) is not configured on the target filesytem (on the Celerra)
1) If you are setting up the replication sessions, I'll assume you are attempting to use an existing target filesystem.
If so, then check for the following:
a) In the Mount options check to see if the target filesystem is set to R/W (or possibly even unmounted)
- set to R/O, if necessary
b) Verify in th filesystem properties that the target filesystem has the same FLR configuration (Compliance or Enterprise) as the source.
- If it is not enabled, this would require recreating the target filesystem if this needs to be changed as you can't modify it after filesystem creation.
- It is even possible that the target filesystem has FLR enabled but the source does not
This would require careful consideration as you would need to review that if set to FLR-C and for some reason there are locked files, you won't be able to delete the filesystem until all files have expired as is expected. On the other hand FLR-E can be forcibly destroyed even with locked files by supplying the -Force flag when deleting the filesystem with nas_fs)
2) Instead let the system create the target filesystem when setting up the replication mirrors
On the other hand, again if you are setting up the replication sessions, instead of using an existing filesystem, let the system create the target filesystem which will make sure it has the proper configuration (same size, mounted R/O, quotas, FLR, etc) for you.
Does this help you troubleshoot?
I think this post maybe closed but can you please suggest if the destination FS can be larger than the source filesystem? Or it have to be exactly the same. Also there is an option to "use and existing pool" Does it means "Storage Pool for File"?
If yes when i am trying to create a Storage Pool for file it is saying no Tempelate for Storage Pool for file available