Air Cleaner User Manual

Additionally, SysBack requires that reverse name resolution be the same on both
sides of the firewall. Let us assume the following information:
SystemB=fruit, 9.19.125.19
If you were logged on to System A:
root:systemB> host apple
apple is 9.19.125.19
root:systemB> host 9.19.125.19
apple.dfw.ibm.com is 9.19.125.19
SysBack will think that apple and apple.dfw.ibm.com are two different hosts.
Backup Return Code Processing
When non-fatal errors are returned from the underlying backup command but still
allow SysBack to continue, SysBack will exit with a return code one, or WARNING.
The non-fatal errors could vary depending on the operating environment since the
condition is usually predicated upon problems in AIX or from AIX commands.
Therefore, during the backup you might see an error like: 0511-089 unable to
open file xxxx out of memory
or other errors like:
File /somepath/somefile can not be found.
The later is often seen in environments that have ever changing temp file
generation. The /usr/sbin/backup command continues on even when these
conditions occur. These are considered soft errors because they don’t impact the
overall backup process.
When an error occurs that is unrecoverable, or threatens the completion of the over
all backup process, SysBack will exit with a return code 2, or ERROR.
Backups that have no warnings or errors will exit with a return code one, or
SUCCESS.
Therefore, the sysback, mkvgback, mkjfsback, mklvback, and mkdirback
commands have three possible return codes:
v 0 Success
v 1 Warning, or soft failure
v 2 Error, or hard failure
At the end of the backup process, a message like the below will be displayed
indicating the overall completion status of the backup process:
WARNING: Volume Group backup completed with non-fatal errors
It is always best to save stdout and stderr from all backup operations for review
when running the backup in the background. This will allow you to easily review
error conditions encountered should you receive a WARNING or ERROR message.
Chapter 4. Performing Backups 4-31