KB Logo

TOLIS Group Knowledge Base

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



How do I backup the BRU Server environment, such as backup jobs, schedules, etc?

Views: 12849
Votes: 3
Posted: 02 Oct, 2007

Backing Up The BRU Server Server

In addition to backing up client systems and even data from the BRU Server server itself, it is also a good idea to backup the BRU Server server environment as a separate data set for ease in recovering the server should it crash.

The server environment consists of the BRU Server binary components, the database table files, and the catalogs directory.

Since the binary components will be recovered by a reinstallation of the BRU Server server , the only elements that should be protected specifically are the database tables and the catalogs directory. Starting with BRU Server release 1.2.0, all platforms provide access to these elements from within the /usr/local/bru-server path. The list of files that should be protected with their own backup are:

  • archives
  • backup
  • dest
  • devices
  • drives
  • history
  • license
  • machines
  • parm
  • schedule
  • tapes
  • upstage
  • user

Also be sure to include the catalogs directory and its contents in this backup.

Depending on your server system, there are a number of ways that you can protect these files. If you have a DVD burner (because the catalogs directory can get larger than a CD's capacity), it is possible to write them to a DVD (or two for safety). Additionally, you can define a single tape destination and backup these files as a special BRU Server backup job, or even manually load a tape and use the BRU standalone engine and back them up manually with a command line script such as:

#!/bin/sh

FILES1="archives backup dest devices drives history license"
FILES2="machines parm schedule tapes upstage user"
DIRS="catalogs"
LABEL="BRU Server environment backup"
DEV=/dev/nst0 cd /usr/local/bru-server sudo ./bru -cvf $ -L $ $ $ $

This will backup the specified files onto a tape that is loaded in the drive recognized by the system as /dev/nst0. For OS X users the device name will be something like ntape0. Of course, this simple script won't control your library, so you will need to manually load and unload the media to perform this backup. You could also change the DEV variable to point to a file on a locally mounted remote filesystem like this:


DEV="/Volumes/Remote RAID 1/Helena_HS_Server.bru"

This would create a BRU archive on the mounted filesystem "Remote RAID 1" called "Helena_HS_Server.bru." This file may then be copied to a rebuilt server and restored after the BRU Server software has been reinstalled. The commands to restore such an archive could look like this:


cd /usr/local/bru-server sudo ./bru -xvf $ -ua

This would restore all of the previous BRU Server data tables and return your BRU Server server environment to the state it was in at the time this backup was created. The "-ua" flag ensures that any existing data table files that were created during the installation will be overwritten by the backup copy.

Compatibility Notice: When moving your BRU Server Environment from one system to another, you must keep the same architecture in place.  Therefore, you cannot move BRU Server from a Mac OS X system to a Linux System and vise versa.  The same applies when trying to move from an Linux x86 to a Linux x86_64, it cannot be done due to the change in architecture of the systems.

If you do need to change architectures, please contact TOLIS Group Technical Support for assistance.

Others in this Category
document How to automatically disable Time Machine during a BRU Server backup.
document Suggested BRU Block & Write Cache/Buffer Sizes and Timeout Settings for Tape Backups
document Fix BRU Server Permissions
document Using Multiple Stage Destinations with BRU Server 2.x
document I can't stop the BRU Server Server daemon on 10.4.x/10.5.x systems...
» More Articles



RSS
Powered by KnowledgebasePublisher
Page Load Time: 0.035587 seconds / 35.587 milliseconds.
Page File Size: 26867 bytes.