Last modified 11 years ago Last modified on 06/16/09 12:49:40

UABgrid Back Up

UABgrid has distributed infrastructure at its core. To facilitate distributed management, reliable operation, and flexible configuration we want leverage technologies that support large scale storage across operating domains. The REDDnet project is developing an infrastructure that should meet all of these demands. By exploring the this technology in the context of UABgrid Backup, we can build a service that meets our needs and provides measures for the ability to provide critical services. This effort relates to the StorageCity and ResearchStorageSystem.

At the moment, our backup is based primarily on a reliable disk infrastructure through traditional raid technologies.

The following diagram is the start of the planning for building our large scale backup infrastructure and provides an overview of what we hope to achieve.

UABgrid Back Up Sketch

@lab Infrastructure

Some notes on equipment in the @lab being used to help develop this solution.

LTO Tape System

For tape backup we have an aging Dell PowerVault 128T tape system (specs). This is sufficient for traditional local backup and archive needs. It facilities development of processes that will leverage back-end storage subsystems. It's only got 1 working HP Ultrium drive right now, the other one has a tape stuck in it, but Iran's LTO Hell has some nice documentation on how to extract it, which may bring the drive back to life.] At the moment this tape library is driven by a Win2k box running Veritas BackupExec?. Controlling the tape system is done with vnc://waltz, for VNC access to waltz from within the @lab. Until we can find a way to control the tape robot from Linux, our connection to the Linux world will be through their backup agents.

The tape system has a front-end display with minimal functionality but does have password protected admin and system areas. The admin password is known but the system password is not. The password reset procedure may require contacting Dell.

The network interface, called the RMC (Remote Management Console) is currently configured to DHCP and our network map doesn't assign it a stack IP. Looking at the front menu on the tape system (Main Menu -> Information -> View Configuration -> Network Access). It's currently accessible within the @lab at You need Java on in your browser to use it. (On the openSUSE @lab desktops you probably need to remove the default install of GNU java and install Sun's Java (and don't forget the "browser plugin" rpm yast -i java-1_5_0-sun-1.5.0_update18-0.1.1 java-1_5_0-sun-plugin-1.5.0_update18-0.1.1). You may need to add a symlink to the plugin (/usr/lib/jvm/java-1.5.0-sun-1.5.0/jre/plugin/i386/ns7/ to $HOME/.mozilla/plugins/ and restart firefox.


Bug: get tape out of drive (instructions)and possibly replace drive Bug: register LTO hostname in @lab DNS and assign static IP via DHCP Feature: find way to control tape library via Linux (request from 2002).