When you use the all asynchronous method, update copying to the remote site is performed using asynchronous copying. With asynchronous copy, there are no adverse effects on transaction performance at the main site because update processing at the main site is completed without waiting for update processing to be completed at the remote site.

However, updates at the main site in a file subject to update copying might not always be reflected at the remote site. This means that if HiRDB at the remote site is restarted after the HiRDB at the main site has experienced a failure due to a disaster or other calamity, the status in which HiRDB is restarted might differ from the status of HiRDB immediately preceding the failure. Therefore, resumption of uninterrupted service from the main site cannot be guaranteed when you use the all asynchronous method.

The following figure provides an overview of the all asynchronous method, and the table below it shows the processing method used with the all asynchronous method when update copying to the remote site is performed.

Figure 8-17 Overview of the all asynchronous method

Table 8-8 Processing method used when update copying to the remote site is performed (all asynchronous method)

Files that are copied to the remote site		Processing method used for update copying
Database files		Asynchronous copy
System files	System log files
	Synchronization point dump files
	Status files