The table below shows how the unload log file to be used is inherited after switching sites. This varies depending on the type of the output destination directory for the unload log file that is specified in the pd_log_auto_unload_path operand.

Table 8-5 How the unload log file is inherited after switching sites

Operation	Type of output destination directory for the unload log file
	UNIX file system	HiRDB file system area
		Unpaired paired logical volume group	Paired paired logical volume group#
The unload log file created at the main site is passed to the remote site	N	N	Y
The system log file unloaded at the main site is uploaded at the remote site	N	N	N

Legend:

Y: Can be executed.

N: Cannot be executed.

#

During pairing, specify either data or never for the fence level, depending on the protection mode you are using.