fbackup fail

[SDC]

If fbackup comes across a full filesystem or gets killed it leaves a lot of mounted filesystems on the disk. fbackup -R will not restart the backup to finish and clean the temporary volumes. What is the best way to return to a stable state?

[Steven Schweda]

> [...] comes across a full filesystem [...]

What does this mean?

> [...] it leaves a lot of mounted
> filesystems on the disk.

For example, ...?

This is harmful, because ...?

> What is the best way to return to a stable
> state?

What's not "stable"? Define "stable".

[SDC]

Well,

an fbackup was started from a script, there was as it happens a full filesystem on the disk. The fbackup session was killed for some reason, I assumed it was because of the full volume. This killed fbackup session left a lot of temporary volumes on the filesystem and will not start again using fbackup -R. The original filesystem is still present and working so stability is not the problem. The issue is that I cannot restart or finish the backup.

[Johnson Punniyalingam]

>>The issue is that I cannot restart or finish the backup.<<

In this case I would like to fine tune your "fbackup script" inorder to avoid the full file system issue.

The Best Solution -> HP Data Proctector .

Thanks,
Johnson