User's Manual

216 Troubleshooting
Backup, restore, and recovery problems
Description FSE backup is aborted, but the backup job hangs.
Explanation Backup uses an archiving tool, depending on the platform, to pack all data that needs to be
backed up. If the archiving tool has already been started and in the meantime the FSE backup
job is aborted, the job hangs until the tool completes the archiving. This may be time
consuming, especially if FSE implementation contains a lot of data to be backed up.
Linux specific
On Linux platform, the system native tool tar is used for archiving the backup data.
Windows specific
On Windows platform, a proprietary FSE tool fse-arch is used for archiving the backup
data.
Workaround You must clean up the FSE server after the abort command. To clean up the FSE server, proceed
as follows:
1. On the FSE server system, terminate the auxiliary processes that are involved in the backup
process.
Linux specific
Using the kill command, terminate all processes named fse-dd or tar.
Windows specific
Using Windows Task Manager, end all processes named fse-arch.
2. Run a script release_snap.py and follow the instructions it displays. The script will
remove obsolete volume snapshots.
The location of the script is platform-dependent.
Linux specific
On Linux platform, the script is located in the directory /opt/fse/sbin/tools.
Windows specific
On Windows platform, the script is located in the directory %InstallPath%\bin.
The value of %InstallPath% depends on the choice made in the FSE installation process.
It defaults to C:\Program Files\Hewlett-Packard\FSE.
Description Backup does not start because of another currently running backup job.
Explanation Any unfinished backups job will prevent a new backup from being started.
Workaround You must clean up the system using the procedure described in the problem FSE backup is
aborted, but the backup job hangs before a new backup job can be started.