Stopping an Automatic or Manual Backup

Under normal conditions, backups complete relatively quickly (in less than 45 minutes). However, if no backup has been previously performed or if the previous backup was stopped before it completed, the next backup can take up to 4 hours.

It is advisable to allow a backup to complete. However, if you accidentally start a backup or need to stop the backup process, use the following procedure. You must log into both the active and standby servers to stop a backup.

Note that a backup cannot restart at the point where it was aborted because various lock files are created to prevent conflicting backups. To restart a manual backup, start the procedure from the beginning. See “Backing Up the LSMS Manually” if you need help.

If you need to restore data from a previously recorded backup, contact the My Oracle Support (MOS).

  1. Log in as root on active server.
  2. To find the process ID of the processes involved in backing up the databases, enter the following command:

    # ps -ef | egrep "rsync|netbackup|lsmsbkp" | grep -v grep

    The output from the above command includes the process ID (PID), also referred to as the job number, for each process that has the characters rsync, netbackup, or lsmsbkp in its name. Note the first PID (shown inbold text in the following example) displayed on the line for each process.

    root      5673 32428  0 13:43 pts/0    00:00:00 /bin/sh 
    /usr/TKLC/lsms/tools/lsmsbkp
    root      5759  5673  4 13:43 pts/0    00:00:00 /usr/bin/perl -T 
    /usr/TKLC/plat/bin/netbackup 
    --config=/usr/TKLC/plat/etc/BackupTK/plat.xml
    root      5942  5759 25 13:43 pts/0    00:00:00 /usr/bin/rsync --archive 
    --delete --delete-excluded --relative --sparse --files-from=- 
    --rsh=/usr/bin/ssh / 
    root@backupserver-lsmssec:/Volumes/LVstorage/lsmssec/00-Oct21_13:43
    root      5943  5942 12 13:43 pts/0    00:00:00 /usr/bin/ssh -l root 
    backupserver-lsmssec rsync --server -logDtpRS --delete-excluded . 
    /Volumes/LVstorage/lsmssec/00-Oct21_13:43
    

  3. To stop the backup, enter the following command:

    # kill <jobnumber1> <jobnumber2> ...

    where <jobnumber1> is the PID of the first process to stop and <jobnumber2> is the PID of the second process to stop. Enter a job number for each line that displays in step 2. For the example output in step 2, enter the following command:

    kill 5673 5759 5942 5943

  4. Verify that all relevant processes have been stopped by entering the following command and ensuring that no output appears:

    # ps -ef | egrep "rsync|netbackup|lsmsbkp" | grep -v grep

    If no output appears, the backup has been stopped.

  5. Clean up any remaining lock files by entering the following command:

    # rm -f /TOC

  6. Repeat steps 1 through 5 on the standby server to stop that server’s backup.
  7. To clear up any lingering lock files on the NAS, enter the following command on either server:

    # ssh backupserver /etc/rc3.d/S99TKLCclearlocks start

    When the OK in the following output displays, all lock files on the NAS have been cleared.

    Clearing backup locks:[  OK  ]