MIMIX, by default, runs data protection reports according to the schedules set for each system. You can change a report schedule on a system or disable it from automatically running on certain systems. You can also manually run a report for a system at any time, even if the automatic schedule for that system has been disabled. Typically, you want to use the reports on each system where production activity occurs.
When changing the schedule for a report, consider the following:
- Which categories of objects do you need to replicate? If you do not need to replicate libraries, directories, or folders, you can disable schedules for the respective data protection report.
On which nodes do you need to check whether new libraries, directories, or folders are
protected by MIMIX replication? Data protection reports should be run on systems in your
production environment that are source systems for replication activity. You might want
to disable schedules for data protection reports on systems that are not source systems
or that can never become source systems for any application group or data group.
- How frequently are new libraries, directories, or folders created on a system? This affects how often the reports should be scheduled to run on that system to evaluate whether data is protected by MIMIX. Business requirements as well as time and system resources also need to be considered when determining scheduling frequency.
- What is the setting of the Directory depth policy? This policy determines the number of directory levels that are included in the directory data protection report. The value of this policy may influence how often or when you want to run the directory report.
- Does automatic scheduling conflict with regularly scheduled backups or times when a system has high processing loads?
- Does heavy creation, deletion, renaming, or locking activity associated with libraries, directories, or folders occur while data protection reports run which might affect the report results?