How to handle incremental backup failures after a system reboot.

 

revision 1/16/2014

 

If you have enabled the [Change Tracking persistent],this products snapshot driver startup and shutdown is handled by system startup/shutdown scripts (/etc/rc.d/rc.sysinit and /etc/rc.d/init.d/halt). The installer will apply the appropriate patch by checking the version of initscripts.rpm ※ 1 in the package distributor provides.

If a newer (than the release date of the product installer) initscripts.rpm is installed on the system , the patch may not be applied automatically. Follow the procedures below to add the appropriate descriptor, or apply the appropriate patch to the system startup/shutdown script. When this situation occurs even if the [Change Tracking Persistent] is enabled, incremental backups may fail.

※1:/etc/rc.d/rc.sysinit and/etc/rc.d/init.d/halt are files included in initscripts.rpm

When not using customized /etc/rc.d/rc.sysinit or /etc/rc.d/init.d/halt script.

Run the following command from the console to verify the presence or absence of a patch from the server.

# aipmng --modupdate --patches

※ An internet connection is required to get a patch from the server.

An appropriate patch exists on the server

The patch will be applied to the local system. If it is successful the message "Successfully applied." will be displayed.

At system start up (shutdown) the snapshot driver will also be able to start up (shutdown) and backups should function normally.

An appropriate patch doesn't exists on the server

The message "No patch files found for this system." will be displayed.

In this case an appropriate patch does not yet exist, please contact technical support.

When using a customized /etc/rc.d/rc.sysinit or /etc/rc.d/init.d/halt script.

If your environment has customized /etc/rc.d/rc.sysinit or /etc/rc.d/init.d/halt scripts, you cannot add descriptions to the start p shutdown scripts through the patch file provided by us.Please add the descriptions on your own using the following information.

Overwriting /etc/rc.d/rc.sysinit

    After the initialization of related device mappers is complete and before the repair mode integrity check (fsck) is run on all file systems, including the root ("/") add the following red items.

if [ -f /etc/crypttab ]; then
    init_crypto 0
fi

# start tracking
if [ -f /etc/aipsnap -a ! -f /.aipsnap_dirty ]; then
            /etc/aipsnap start --tracking
fi


if [ -f /fastboot ] || strstr "$cmdline" fastboot ; then
            fastboot=yes
fi

 

Overwriting /etc/rc.d/init.d/halt

    After all the file systems are re-mounted as read only add the following read items.

# Remount read only anything that's left mounted.
# echo $"Remounting remaining filesystems readonly"
mount | awk '{ print $1,$3 }' | while read dev dir; do
    fstab-decode mount -n -o ro,remount $dev $dir
done

# now clear dirty flag on tracking table
[ -f /etc/aipsnap ] && /etc/aipsnap clear_dirtyflag

# If we left mdmon's running wait for the raidsets to become clean
if [ -n "$OMITARGS" ]; then
    mdadm --wait-clean --scan
fi

 

Please refer to sample patch files installed with this product in /opt/NetJapan/patch(rc.sysinit-sample.patch、halt-sample.patch).

If you have questions regarding your specific system please contact technical support.

 

Back to Index