Loading...
Loading...
On a scale setup with many file systems (approximately 125 FS) under replication session with snapshot configured on the file systems, when bulk delete of the file systems is attempted, it may fail and change the NasServerReplication session to failed state.
As part of the file system delete which is in the replication session, it includes deletion of the underlying block (nas_volume) replication session, followed by invocation of logic to sync up SDNAS database to CPDB. That may result in many commands to being triggered and eventually these commands are getting queued causing subsequent file system deletion to fail.
Workaround: Retry the delete of the file system which failed during the bulk delete operation, one file system at a time. This removes the FsReplication sessions that are in a failed state. Pause the associated NasServer replication session which was in a failed state. Resume the NasServer replication session which is paused in Step 2. Recommendation: Delete only one file system at a time, instead of doing a bulk deletion.
Click on a version to see all relevant bugs