You must be careful when using Real Time SAN Replication at the same time as any of the facilities described in the following table. This table lists these facilities and provides related notes.

Table 8-1 Facilities that require special attention and related notes

Facility to be used	Notes
Inner replica facility	For notes on using the inner replica facility, see 8.2 Notes on using the inner replica facility.
HiRDB Datareplicator replication facility	Because the HiRDB Datareplicator environment cannot be inherited during a site switchover, the HiRDB Datareplicator replication facility cannot be used. To use the replication facility after you have switched the site for the source or target HiRDB, you must first initialize the HiRDB Datareplicator environment for both the source HiRDB and target HiRDB and then re-create the target HiRDB based on the source HiRDB.
System switchover facility	For notes on using the system switchover facility, see 8.3 Notes on using the system switchover facility.
Security audit facility	For notes on using the security audit facility, see 8.4 Notes on using the security audit facility.
Automatic log unloading facility	For notes on using the automatic log unloading facility, see 8.5 Notes on using the automatic log unloading facility.
System reconfiguration command	Note the following when using the system reconfiguration command (pdchgconf command): Execute the system reconfiguration command when HiRDB is running at the main site. You cannot use the system reconfiguration command to change the system definition at the remote site. You must change the system definition at the remote site manually after the system reconfiguration command has terminated normally at the main site. Unlike with the pdconfchk command, the pdrisechk command cannot check the post-changed configuration before the system configuration is changed. Therefore, use the pdrisechk command to check the configuration of Real Time SAN Replication after the system reconfiguration command has been executed.
Statistical information collection	When the system is switched over from the main site to the remote site, the type of statistical information collected at the main site and statistics logs cannot be passed onto the remote site. Therefore, you must restart statistical information collection at the remote site.
Facility for monitoring free area for system log file	For notes on using the facility for monitoring free area for system log files, see 8.6 Notes on using the facility for monitoring the free area for system log files.
Automatic extension of RDAREAs (applicable only to the hybrid method)	When the hybrid method is used, the system waits to perform synchronization of the database at the remote site while automatic extension is being performed. An overhead of at least two seconds may occur each time automatic extension is performed. For details about how to recover the database at the remote site when a pended synchronization of the database at the remote site fails, see 6. Error Handling.
Shared table (applicable only to the hybrid method)	For notes on using a shared table, see 8.7 Notes on using a shared table (applicable only to the hybrid method).