You might need to restart a backup initiated by the dump command. The dump command sometimes does not finish because of such internal or external errors as tape write errors, power outages, accidental user interruptions, or internal inconsistency on the filer.
You might also choose to interrupt and restart a backup to avoid periods of heavy traffic on the filer or to avoid competition for other limited resources on the filer, such as a tape drive. A long backup can be interrupted and restarted later if a more urgent restore (or backup) requires the same tape drive. Restartable backups persist across reboots.
A failed backup to tape can be restarted if it has completed one tape that has ended in phase IV (file data and ACL data).
To find out whether a backup is proceeding as expected or has terminated, you can run the backup status command. For more information, see Checking the status of a dump command backup.
To restart a dump process that has been shown to be restartable, complete the following step.
Copyright © 1994-2003, Network Appliance, Inc. All rights
reserved.
Part No. 210-00325
File: dump37.htm
Last updated: 01/14/03 18:33:08