Description | After an FSE backup process is aborted or the FSE server is restarted due to power outage, new |
| FSE backup cannot be started. |
Explanation | The aborted FSE backup process did not remove the lock file backup.pid from the lock |
| directory. This file is used to prevent starting another backup process while the first backup |
| process is still running. |
Workaround | After verifying that no other FSE backup process is running at the moment, manually remove the |
| file backup.pid and start FSE backup once again. |
| For the exact path of the lock directory on a particular platform, see appendix ”Directory |
| layout”. |
Description | After you restore the FSE server from a tape medium that stores only one FSE backup image, |
| the status of the medium will be 'empty'. |
Explanation | At the time when the backup was started, the tape medium was empty. Since restore reverts the |
| complete FSE server state to the moment when the backup was initiated, the statuses of backup |
| media are also reverted. |
Workaround | As this situation will resolve automatically after a new backup image will be created on the |
| same medium, you can ignore the erroneous status. |
HP StorageWorks File System Extender Software user guide 267