How do backup copy health checks work in conjunction with a WAN accelerator environment? Should they be disabled in that situation due to performance considerations?
Scenario: Backup jobs are run locally in a remote site and the output is stored on a local repository in that site. Backup copy jobs use those backups as their source and write their output via WAN accelerator to a remote site repository over an extremely low bandwidth connection. Health checks are scheduled to occur weekly on the backup copy jobs.
I'm concerned that the health checks will take massive times to complete.