Single Item Restore: Restore Scenarios

“bacula” Account on Redhat

All commands in this document use the “bacula” unix account to run.

On Redhat, the Unix “bacula” account is locked by default. It means that it’s not possible by default to execute a command such as su - bacula.

It is possible to unlock the “bacula” account, or to use sudo -u bacula to execute commands. For example:

bacula@storage# /opt/bacula/bin/bconsole

It can be run from the root account using the following command:

root@storage# sudo -u bacula /opt/bacula/bin/bconsole

It is also possible to start a shell session using:

root@storage# sudo -u bacula /bin/bash

or unlock the “bacula” unix account and use su - with a command such as:

root@storage# chsh -s /bin/bash bacula
root@storage# su - bacula
bacula@storage# whoami
bacula

Fuse FileSystem

If a restore session is not properly cleaned up, the mount command may show some directories mounted with the Bacula Fuse FileSystem.

baculafs on /opt/bacula/working/cat-ro type fuse.baculafs (ro,user=bacula)
backend0 on /opt/bacula/working/26-0 type fuse.backend0 (ro,user=bacula)
/dev/fuse on /opt/bacula/working/26 type fuse (rw,nosuid,nodev,user=bacula)

It is possible to unmount directories with the fusermount -u command.

bacula@storage# fusermount -z -u /opt/bacula/working/26
bacula@storage# fusermount -z -u /opt/bacula/working/26-0
bacula@storage# fusermount -z -u /opt/bacula/working/cat-ro

Cache Directory

To speed up future VMware Single Item restore sessions, some files that are generated during a restore session are kept in a cache directory.

bacula@storage# ls /opt/bacula/working/mount-cache
1-5-0.bmp  1-5-2.bmp    MyCatalog-2.idx  MyCatalog-5.idx  MyCatalog-8.idx
1-5-1.bmp  1-5.profile  MyCatalog-4.idx  MyCatalog-6.idx  MyCatalog-9.idx

It is possible to remove files in the cache after some time - they will be re-generated if needed.