Recovery time objective (RTO)

Recovery time objective (RTO) is the time taken to convert secondary fileset into active primary fileset and move applications to that site, when a disaster occurs at the primary site.

Whenever a disaster occurs at the primary site, the secondary site becomes the acting primary by running the mmafmctl failoverToSecondary command. --norestore is set by default. The secondary fileset is converted to acting primary but avoids restoration of data from the last RPO snapshot and maintains the existing data. As an administrator, you can run the mmafmctl failoverToSecondary command with --restore option to clean the existing data at the secondary fileset and restore all data from the last RPO snapshot.

RTO can be estimated if the administrator knows the volume of data generated in an RPO interval. The volume of data that must be restored from the last snapshot depends on the number of files that have changed in an RPO interval as a snapshot restore requires a complete scan of the snapshot to determine which files have changed. Fail over time is one of the components that an administrator should use to calculate the RTO for the application.