KB Logo

TOLIS Group Knowledge Base

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

Performing a Hardware Scan in BRU Server 2.0

Views: 17295
Votes: 1
Posted: 05 Aug, 2009

Running a Hardware Scan in BRU Server 2.0


When backing up to tape in with BRU Server v2.0, it checks a hardware signature to make sure that the hardware that was connected to the system during the last hardware scan is the same hardware that is currently connected.  The reason for the hardware scan is to ensure that BRU Server knows what tape drives are connected where, and what tape drives are associated to any libraries that may also be connected.  This ensure that the proper drive is used for backup operations.

When the hardware signature changes, BRU Server will need the system administrator to perform a Hardware Scan for BRU Server to re-associate all of the hardware correctly.  With BRU Server 2.0, if the tape hardware changes and the backup is going to disk, the backup will commence without interruption since the tape hardware is not being used for the disk-based backup.


ATTENTION: When running a hardware scan, there needs to be a tape in slot one (1).  This tape must be a data tape, it cannot be a cleaning tape. Additionally, when powering on a library while the BRU Server Server system is turned off, the library needs to become fully ready before you power on the BRU Server Server system. This means allowing the library to fully complete the power-up process and inventory. If the library is not in a ready state when the system boots, the library may not be seen and the system will need to be rebooted.

BRU Server Config - Linux - Hardware ScanThere are two ways that a Hardware Scan may be run on the BRU Server system.  For administrators with access to the BRU Server Config application, login to the BRU Server Config application (not the BRU Server Console ) and click on the "Hardware Scan" button.  From there, click the "Scan" button located in the bottom right-hand corner.  The hardware scan will commence.  When completed, the BRU Server server daemon will stop and restart automatically. When the daemon restart is complete the hardware scan is done.

If, however, you have only SSH or command line access to the BRU Server system, then the following steps may be performed:

You may copy-and-paste the commands if needed.  The examples provided here are from a Linux system with a stand-alone tape drive.  Mac users, instead of /dev/nst0, you'll see ntape0.

sudo /usr/local/bru-server/server --kill

After this command, you should see something like:

Sending signal to 1234

Where "1234" is the process number for the BRU Server daemon.  This number will always change so don't worry if you see a different number every time you run a hardware scan on the BRU Server Server.

Next run:

sudo /usr/local/bru-server/server --scan

Once you complete this command, you should see something similar to:

[user@bruapp user]$ sudo /usr/local/bru-server/server --scan
Starting hardware scan
  Scanning for tapes and changers
     Found tape at /dev/sg0 (/dev/nst0) SONY/SDX-900V

Ejecting all tapes
  Ejecting from /dev/nst0
No autoloaders detected

Saving settings...

[user@bruapp user]$

Mac users, you will see ntape0 instead of /dev/nst0 for the "Found tape at" and "Ejecting from" lines.

When this is completed (returns to a command prompt), run the following to restart the server daemon:

sudo /usr/local/bru-server/server

That's it!  The hardware scan is complete and the BRU Server backups should run without issue.  If you get any errors during this part, please contact TOLIS Group Technical Support for further assistance.

Others in this Category
document Suggested BRU Block & Write Cache/Buffer Sizes and Timeout Settings for Tape Backups
document Using USB Tape Drives on BRU Server for Linux
document Information About Inconsistent Tapes
document brufilter: [E145] Streaming Checksum Error at Block...
document Using Multiple Stage Destinations with BRU Server 2.x
» More Articles

Powered by KnowledgebasePublisher
Page Load Time: 0.035871 seconds / 35.871 milliseconds.
Page File Size: 27088 bytes.