Core Performance Degrades and Jobs only happen within a Short Window (4039505)

Core Performance Degrades and Jobs only happen within a Short Window

Overtime, you may have noticed that the Core performance in regards to snapshots, replication, and virtual standby have not been working to complete expectations. For example, historically jobs would run throughout the full hour interval, but eventually this degrades down to only a few jobs per hour even though the Core is normally scheduled to run throughout the full hour.

The Persist Dedupe Cache completion time could be a cause for this degraded performance. While the persist dedupe cache job is running, all Core functionality is halted to include snapshot transfers, incoming/outgoing replication, and restore operations. In most cases, and depending on the size of the dedupe cache and the storage location where it resides, this job should only take a few seconds to complete. Overtime, outdated firmware and drivers or failing storage can cause the persist dedupe cache job to go on much longer than previously performed.

In the Core Events page, search for the keyword "persist" to get a listing of all persisting dedupe cache job events. Verify the elapsed time for this job both presently and historically. Identify where the change happens and investigate the following variables:

1. Storage firmware and drivers
2. Failing physical storage of controllers
3. Storage location IOPS
4. Reboot the Core Server

After verify that these components are up to date and completed to satisfaction, the persist dedupe cache job should return to normal operational performance.

__________

Is your AppAssure or Rapid Recovery solution working as efficiently as possible? Learn more about our AppAssure and Rapid Recovery Health Check.