KB Logo

TOLIS Group Knowledge Base

Browse KB by category:
Go to KB #:
Glossary
Email   Bookmark



BRU Server doesn't backup mounted volumes, why?

Views: 13044
Votes: 1
Posted: 27 Dec, 2007

By default, BRU Server will not automatically cross mount points.  Therefore, if you want to backup multiple volumes/drives, you need to explicitly select them for backup.  To find out what mount points you have on your system, simply run the following command:

Note: Mac OS X is a Unix based file system, so the Linux/Unix command will work as well.

Mac OS X :

 
# mount | grep local | grep -v devfs
 

Linux/Unix:

 
# df -h | grep -v tmpfs
 

Windows:

On Windows systems, mount points are referenced by drive letters.  The root volume is "C:\" and therefore, if you would like any other drive backed up, it must be explicitly selected in BRU Server .

The 'mount' command itself will work on both Unix and Linux systems. and provide a more detailed output for advanced users.

This command should result with something similar to:

Mac OS X:

# mount | grep local | grep -v devfs
/dev/disk0s3 on / (hfs, local, journaled)
/dev/disk1s10 on /Volumes/10.5 Clone (hfs, local, nodev, nosuid, journaled, noowners)
/dev/disk1s12 on /Volumes/OS X 10.4.3 (hfs, local, nodev, nosuid, journaled, noowners)
/dev/disk1s14 on /Volumes/10.4 Clone (hfs, local, nodev, nosuid, journaled, noowners)
/dev/disk1s16 on /Volumes/10.4 Server Clone (hfs, local, nodev, nosuid, journaled, noowners)
#

Linux/Unix:

# df -h | grep -v tmpfs
Filesystem Size  Used  Avail  Use%  Mounted on
/dev/sda3   20G  4.5G    14G   25%     /
/dev/sda2   39G  524M    37G    2%     /home
/dev/sda5   20G  4.8G    16G   24%     /suse
/dev/sda1  130M   18M   105M   15%     /boot
#

In the above examples, only the "/", or root volume, will be backed up. For Mac OS X, if you want "/Volumes/10.4 Clone" to be backed up as well, you'll need to explicitly select that volume in the BRU Server Console .  For Linux/Unix, if you want /home backed up, you will need to explicitly select /home in the BRU Server Console to be backed up.

There are a number of reasons why BRU Server does not cross mount points.  One is because if you have a publicly shared volumed, mounted on all of your client systems, BRU Server would backup that volume on each system on which it was mounted.  If it's only a few gigabytes, then there is not too much concern, however, if it's a 4 terabyte RAID, then you can see the problem with that setup.

The main reason for this is because of the restore process.  If you backup all mounted volumes, then if you have to restore from bare-metal, if the drives/voluemes are not mounted, BRU Server will create those mount points as directories with the contents that it backed up.  For this reason, it is strongly reccomened that each mounted volume be it's own backup job.  This will prevent this problem from arising and make a more controlled backup strategy.  For more information on this, the "How do logical backups simplify restores?" KB article.

Others in this Category
document How does BRU Server use the ports 14441 to 14450 for backup operations?
document What client system platforms are supported by BRU Server?
document What is the difference in a destination and a tape in BRU Server?
document Multiple Tape Devices, One BRU Server System. Can this be done?
document How do I control my tape library with the libctl (tm) command on Mac OS X?
» More Articles



RSS
Powered by KnowledgebasePublisher
Page Load Time: 0.030325 seconds / 30.325 milliseconds.
Page File Size: 24130 bytes.