Best Practices: Stop jobs before performing bulk changes to a PeerGFS-monitored system
When using Robocopy or making other mass bulk changes (e.g. metadata changes, file seeding) to a file server being replicated by PeerGFS, the best practice is to disable jobs before using Robocopy or performing the mass bulk changes. Otherwise, if there are excessively high levels of data changes incurred by Robocopy, the Peer Agent may become overwhelmed trying to keep up with them. This can cause undesired behavior in the host server.
Steps
1. Stop all jobs that use the Agent that is the target of the Robocopy or bulk changes.
2. Perform the bulk changes.
3. Restart the jobs.