User's Manual

218 Troubleshooting
Description Backup process fails and leaves snapshots of the backed-up file systems (and HSM file systems)
on the FSE server (and the FSE clients).
Explanation Backup failure prevents the clean-up code to unmount and remove the snapshots that were
created during backup. These snapshots occupy space on the FSE server (and the FSE clients),
and also prevent you from running subsequent backups.
Workaround On the consolidated FSE implementation or the FSE sever, run the release_snap.py script to
unmount and remove the snapshots that were created during the backup of the FSE
implementation.
CAUTION: The command lists all existing snapshots, not only the ones that were created
during the backup of the FSE implementation. Before removing a snapshot, the script asks for
confirmation. This way, you can preserve the snapshots that were not created by the FSE
implementation.
Linux specific
On Linux platform, run the following command to execute the script:
python /opt/fse/sbin/tools/release_snap.py
Windows specific
On Windows platform, run the following command to execute the script:
%PP%\python.exe %InstallPath%\bin\release_snap.py
Use the actual Python installation path in place of the %PP% string.
Note that the value of %InstallPath% depends on the choice made in the FSE installation
process. It defaults to C:\Program Files\Hewlett-Packard\FSE.
Description After restore of an HSM file system, files that were previously deleted from the HSM file system
are recreated, but online files that still existed are truncated (Windows FSE client-specific).
Explanation n/a
Workaround Delete the files from the HSM file system and start the restore again.