B.5 Error Codes of Pre-/Post-processing Scripts

The table below lists the error codes of the pre-processing script and post-processing script.

Table B.5 Error Codes of Pre-processing and Post-processing Scripts
Error Code	Message	Explanation	Action Plan
1	System error	A system error occurred.	A system error occurred in the pre-processing or post-processing script. Possible causes of this error are as follows: The pre-processing or post-processing script does not have the execution privilege. A syntax error exists in the pre-processing or post-processing script. Check if the script file privilege is correct. Also check if a syntax error exists in the pre-processing or post-processing script.
2	Parameter error	A parameter error occurred.	The parameter to be passed to the pre-processing or post-processing script is invalid. Check if the customization of the pre-processing or post-processing script is correct.
3	Script file not found	The script file was not found.	The pre-processing or post-processing script file was not found. Stop all operations and then reinstall AdvancedCopy Manager.
4	Unknown exception	An unknown execution occurred.	The script terminated abnormally because an unknown exception occurred. Check if script customization is correct.
10	umount error	An attempt to unmount the volume has failed.	An attempt to unmount the volume has failed. The volume that you attempted to unmount may be in use. (*1) The output from the fuser command and ps command when the volume unmount failed is saved to the following files. Check if a user was accessing the volume that you attempted to unmount by referencing these files. Backup management: /var/opt/FJSVswsts/$SWSTGNODE/log/deviceName.fuser /var/opt/FJSVswsts/$SWSTGNODE/log/deviceName.ps Replication management: /var/opt/FJSVswsrp/$SWSTGNODE/log/deviceName.fuser /var/opt/FJSVswsrp/$SWSTGNODE/log/deviceName.ps The error messages of the umount command are also saved to the following files, so check the contents of these files and then take appropriate action. Backup management: /var/opt/FJSVswsts/$SWSTGNODE/log/deviceName.umount Replication management: /var/opt/FJSVswsrp/$SWSTGNODE/log/deviceName.umount
11	mount error	An attempt to mount the volume has failed.	An attempt to mount the volume has failed. Check if the mount point exists and also if the mount point is already being used. If the copy source volume is the RAW device and the copy destination volume is already mounted, an error occurs in the copy destination volume. In this case, unmount the copy destination volume first. The error messages of the mount command are saved to the following files, so check the contents of these files and then take appropriate action. Backup management: /var/opt/FJSVswsts/$SWSTGNODE/log/deviceName.mount Replication management: /var/opt/FJSVswsrp/$SWSTGNODE/log/deviceName.mount
12	fsck error	fsck failed.	An error was detected during the file system check. An error may have occurred in the file system on the copy source volume. Check the status of the file system on the copy source volume. The error messages of the fsck command are saved to the following files, so check the contents of these files and then take appropriate action. Backup management: /var/opt/FJSVswsts/$SWSTGNODE/log/deviceName.fsck Replication management: /var/opt/FJSVswsrp/$SWSTGNODE/log/deviceName.fsck
13	Illegal mount type	The mount type of the target disk is stack mount or bind mount.	The mount type of the target disk is either stack mount or bind mount. These mount formats are not supported. If the mount type is stack mount, unmount the copy source volume or unmount all the other volumes mounted on the mount point of the copy source volume, and then re-execute. If the mount type is bind mount, unmount all the directories mounted by the mount command with the --bind option on the copy source volume and then re-execute the command.
30	VG configuration file not fount error	The volume group configuration information file was not found.	The volume group configuration information file was not found. The standard pre-processing or post-processing script restores the configuration information from /etc/lvmount/volumeGroupName.conf file. Check the volume group configuration information file. If the configuration information is backed up to another file, customize the script.
31	vgcfgrestore error	vgcfgrestore failed.	An attempt to restore the volume group configuration information has failed. Check the volume group configuration information file and check if the pre-processing or post-processing script is customized correctly. The error messages of the vgcfgrestore command are saved to the following files, so check the contents of these files and then take appropriate action. Backup management: /var/opt/FJSVswsts/$SWSTGNODE/log/deviceName.vgcfgrestore Replication management: /var/opt/FJSVswsrp/$SWSTGNODE/log/deviceName.vgcfgrestore
50	varyoffvg error	varyoffvg failed.	An attempt to deactivate the volume group has failed. Check if the volume group is being used. Check that all the logical volumes on the destination volume can be unmounted. Also check that the pre-processing script is customized so that it unmounts all the logical volumes. If the logical volumes are mounted, you cannot deactivate the destination volume. The error messages of the varyoffvg command are saved to the following files, so check the contents of these files and then take appropriate action. Backup management: /var/opt/FJSVswsts/$SWSTGNODE/log/deviceName.varyoffvg Replication management: /var/opt/FJSVswsrp/$SWSTGNODE/log/deviceName.varyoffvg
51	varyonvg error	varyonvg failed.	An attempt to activate the volume group has failed. The error messages of the varyonvg command are saved to the following files, so check the contents of these files and then take appropriate action. Backup management: /var/opt/FJSVswsts/$SWSTGNODE/log/deviceName.varyonvg Replication management: /var/opt/FJSVswsrp/$SWSTGNODE/log/deviceName.varyonvg
52	chfs error	chfs failed.	An attempt to change a logical volume mount point has failed. Check if the pre-processing and post-processing scripts are correctly customized. The error messages of the chfs command are saved to the following files, so check the contents of these files and then take appropriate action. Backup management: /var/opt/FJSVswsts/$SWSTGNODE/log/deviceName.chfs Replication management: /var/opt/FJSVswsrp/$SWSTGNODE/log/deviceName.chfs
53	chdev error	chdev failed.	An attempt to clear PVID has failed. Check if the pre-processing and post-processing scripts are correctly customized. The error messages of the chdev command are saved to the following files, so check the contents of these files and then take appropriate action. Backup management: /var/opt/FJSVswsts/$SWSTGNODE/log/deviceName.chdev Replication management: /var/opt/FJSVswsrp/$SWSTGNODE/log/deviceName.chdev
54	exportvg error	exportvg failed.	An attempt to temporarily remove the volume group has failed. Check if the pre-processing and post-processing scripts are correctly customized. The destination volume may be active. Usually, this active status does not occur because the pre-processing script of the replication deactivates the destination volume. Check if the destination volume is manually activated. The error messages of the exportvg command are saved to the following files, so check the contents of these files and then take appropriate action. Backup management: /var/opt/FJSVswsts/$SWSTGNODE/log/deviceName.exportvg Replication management: /var/opt/FJSVswsrp/$SWSTGNODE/log/deviceName.exportvg
56	recreatevg error	recreatevg failed.	An attempt to recreate a volume group has failed. Check if the pre-processing and post-processing scripts are correctly customized. The post-processing script may have been incorrectly customized. Check the contents of the post-processing script. The error messages of the recreatevg command are saved to the following files, so check the contents of these files and then take appropriate action. Backup management: /var/opt/FJSVswsts/$SWSTGNODE/log/deviceName.recreatevg Replication management: /var/opt/FJSVswsrp/$SWSTGNODE/log/deviceName.recreatevg
99	Script not customize	The pre-processing and post-processing scripts are not customized.	The pre-processing and post-processing scripts are not yet customized. Customize these scripts according to "Pre-processing and Post-processing of Backup and Restoration" and "Preprocessing and Post-processing of replication" in the ETERNUS SF AdvancedCopy Manager Operation Guide, and re-execute.
Others	Other error	Some other error occurred.	An error other than on of the above errors occurred. Check if the customized part is correct.

*1:

For Solaris, Linux, HP-UX, or AIX:
If an error occurs when the volume is being unmounted, check that the target volume can be unmounted.
To suppress data access to guarantee data integrity, pre-processing unmounts the copy source volume. For this reason, if the target volume is being used when copy is run, an error occurs because the volume cannot be unmounted. Note the following points when the volume cannot be unmounted:

No other application is using the transaction volume. If any other application is using the transaction volume, temporarily exit the application.
No user is using the transaction volume. A user who is currently using the transaction volume must temporarily stop using it.
No other volume is mounted on the transaction volume. If any other volume is mounted, temporarily unmount it.
The transaction volume is not shared by NFS. If the transaction volume is shared by NFS, temporarily unshare it.

You may be able to investigate if a volume is in use by using the following commands. Refer to the operating system manuals for information on these commands.

For Solaris:
mount, fuser, pfiles, share
For Linux, HP-UX, or AIX:
mount, fuser