User's Manual

266 Troubleshooting
Description After the FSE restore process successfully completed, FSE processes cannot be started on the
consolidated FSE system or FSE server.
Explanation The most probable cause of this problem is that some files on the consolidated FSE system or
FSE server were either struck by disaster or accidentally deleted, and these files were not
backed up during the FSE backup process.
Note that FSE backup images do not include files from the FSE installation which are not
updated during FSE operation.
Linux specific
FSE backup configuration file backup.cfg is not backed up.
Workaround Before starting the FSE restore process, repair the FSE installation. The repair process will
replace corrupt or missing FSE installation files.
Linux specific
Proceed as follows:
1. Repair the installed FSE software by using the rpm -F command.
For details, see the FSE installation guide for Linux, chapter ”Installing FSE software”,
section ”Verifying and repairing the installed FSE software”.
2. Using the fserestore command, start the FSE restore process again.
3. Optionally, check and modify values in the FSE backup configuration file backup.cfg.
Windows specific
Proceed as follows:
1. Repair the installed FSE software by using the repair feature of the FSE installation wizard.
For details, see the FSE installation guide for Windows, chapter ”Installing FSE software”,
section ”Verifying and repairing the installed FSE software”.
2. Stop local FSE processes with the fse --stop command, as follows:
C:\>fse --stop
FSE Windows Service stopped.
3. Using the fserestore command, start the FSE restore process again.
Description The FSE backup process abnormally terminates with the fsebackup command reporting the
following errors in the terminal window:
ERROR: Checking backup size failed.
ERROR: SnapshotMgr error.
ERROR: Release snapshots failed: ...
(Windows Server 2003 specific)
Explanation This problem occurs because the Volume Shadow Copy service automatically removed the
existing disk volume snapshot, in order to prevent free space on the volume from running out
completely. Afterwards, the backup job could not calculate total size of files that would be
backed up.
This happens in circumstances, when the volume is already almost full at the time the snapshot
is created, and later the I/O traffic on the volume is high.
Workaround Free some space on disk volume that stores the directory %InstallPath%\var and start FSE
backup again.