PhaseDetail1 = 0 DrTestPhaseDetail1 = 0 ActivePeerDomain = "rbRMHA" # 

Subsequent discoveries can be started by user or by the KSYS scheduler. You normally run a discovery command each time a change is made in your environment. By default, the KSYS scheduler starts a so called Deep Discovery  once in every 24 hours at midnight, as described in “Quick Discovery and Deep Discovery scheduling records” on page 72. You can change this setting, as shown in Example 2-57. 

# ksysmgr q system|grep auto_discovery_time auto_discovery_time: 00:00 hours # ksysmgr mod system auto_discovery_time -h  ksysmgr modify system [auto_discovery_time=<hh:mm>] hh - hour: 00 to 23 mm - minute: 00 to 59 ... # 

Deep Discovery means that discovery is followed by a complete verification step. Every hour, the system performs a Quick Discovery , which is discovery only with no verification. The KSYS subsystem scans the environment for any changes that occurred since the last discovery and adapts to the modified environment. Collected changes are saved persistently such that they survive any daemon or KSYS node crash or restart event. Any changes in the configuration or issues that are found during a discovery are reported to the user and related change or error records are written in log and trace files. 

A discovery must be completed successfully before running the first verification. The verification process ensures that the backup host can accommodate the VM. Verification consists of an LPM validate operation that is performed for every VM on all the available backup hosts on the host group. Any issues that are found during verification trigger a notification to registered users, and then are logged in to log files. 

Such verification can be started either for a host group, as shown in Example 2-58, or only for a host or VM, as shown in Example 2-59. 

# ksysmgr discover host_group <hg_name> verify=true # ksysmgr verify host_group <hg_name> 

In the case of a host or VM, we rather use LPM validation instead of verification. 

# ksysmgr lpm host <hostname|uuid> [to=<hostname|uuid>] action=validate # ksysmgr lpm vm <vm1[,vm2,...]> [to=<hostname|uuid>] action=validate 

