Results 1 to 7 of 7

Thread: Amanda FreeBSD 7.0-RELEASE

  1. #1

    Default Amanda FreeBSD 7.0-RELEASE

    Hello!

    I can't correctly configure amanda-server-2.5.1p3_5,1 on my FreeBSD 7.0 box. Also, i have ch0: <DELL PV-124T 0031> Removable Changer SCSI-2 device as a changer and sa0: <IBM ULTRIUM-TD3 5BG2> Removable Sequential Access SCSI-3 device. Library consist of 10 tapes and 1 clean tape.

    There is my skipped in some way .conf file:

    ...
    runtapes 1 # number of tapes to be used in a single run of amdump
    #tpchanger "chg-manual" # the tape-changer glue script
    tpchanger "chg-chio"
    tapedev "/dev/nsa0" # the no-rewind tape device to be used
    rawtapedev "/dev/null" # the raw device to be used (ftape only)
    #changerfile "/usr/local/etc/amanda/freebsd/changer"
    #changerfile "/usr/local/etc/amanda/freebsd/changer-status"
    changerfile "/usr/local/etc/amanda/freebsd/changer.conf"
    #changerdev "/dev/null"
    changerdev "/dev/ch0"
    ...
    define tapetype DELL-LTO3-400 {
    comment "Dell PV124T LTO3 (hardware compression off)"
    length 402432 mbytes
    filemark 0 kbytes
    speed 71189 kps
    }


    define tapetype ULTRIUM-TD3 {
    comment "IBM ULTRIUM-TD3 with Sony LTO3 media (hardware compression off)"
    length 402432 mbytes
    filemark 0 kbytes
    speed 69766 kps
    }

    and there is a changer.conf file:

    changerdev=/dev/ch0
    firstslot=0
    lastslot=9
    cleanslot=10
    autoclean=0
    havereader=0
    offline_before_unload=0
    poll_drive_ready=10
    max_drive_wait=120
    unloadpause=20
    driveslot=0

    I can't run even amcheck cause the scsi error. I think, that i use wrong dev names. Which is right names for my system? What i'm doing wrong? Help, please.

    Any additional info from me can be send if need.

  2. #2

    Default This cause not Amanda problem

    After some issues i discover that Dell PowevVault not suppoted under FreeBSD. No command successful at console: mtx, chio. This changer supported under Linux officialy by Dell.

  3. #3
    Join Date
    Aug 2008
    Posts
    184

    Default

    Did you try Dell PowerVault 124T with Linux or any other OS? If yes, were you able to use it with Amanda?

    thanks

  4. #4

    Default

    No, i didn't try Amanda on the other platforms. On W2K3 i use the Symantec backup.

  5. #5
    Join Date
    Aug 2008
    Posts
    184

    Default

    So did you land up hooking the PowerVault to a Windows system?

    Did you get Amanda working on FreeBSD with the Ultrium?

    thanks

  6. #6

    Default

    Quote Originally Posted by zbackup View Post
    So did you land up hooking the PowerVault to a Windows system?
    Yes, cause need a backup solution today... Not tomorrow...

    Quote Originally Posted by zbackup View Post
    Did you get Amanda working on FreeBSD with the Ulthrium?
    No, unfortunately. Power Vault changer didn't run any commands.

    P.S. I've got many error messages at the console, and even a scsi card restart.

  7. #7
    Join Date
    May 2008
    Posts
    45

    Default

    # uname -a
    FreeBSD balder.glz.hidden-powers.com 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Wed Oct 8 12:06:03 CEST 2008 [email]root@midgard.glz.hidden-powers.com[/email]:/usr/obj/usr/src/sys/BALDER amd64

    # camcontrol devlist
    <DELL PV-122T K17r> at scbus0 target 5 lun 0 (pass0,ch0)
    <IBM ULTRIUM-TD2 53Y3> at scbus0 target 6 lun 0 (sa0,pass1)

    # cat /var/adm/amanda/lule2/changer.conf
    # Changer config for Dell 122T Loader
    firstslot=1 #### First storage slot (element) -- required
    lastslot=7 #### Last storage slot (element) -- required
    cleanslot=8 #### Slot with cleaner tape -- default is "-1"
    # #### Set negative to indicate no cleaner available
    driveslot=0 #### Drive slot number. Defaults to 0
    # #### Use the 'Data Transfer Element' you want
    #
    # # Do you want to clean the drive after a certain number of accesses?
    # # NOTE - This is unreliable, since 'accesses' aren't 'uses', and we
    # # have no reliable way to count this. A single amcheck could
    # # generate as many accesses as slots you have, plus 1.
    # # ALSO NOTE - many modern tape loaders handle this automatically.
    #
    autoclean=0 #### Set to '1' or greater to enable
    #
    # autocleancount=99 #### Number of access before a clean.
    #
    havereader=0 #### If you have a barcode reader, set to 1.
    #
    offline_before_unload=0 #### Does your robot require an
    # #### 'mt offline' before mtx unload?
    #
    # poll_drive_ready=NN #### Time (seconds) between tests to see if
    # #### the tape drive has gone ready (default: 3).
    #
    # max_drive_wait=NN #### Maximum time (seconds) to wait for the
    # #### tape drive to become ready (default: 120).
    #
    # initial_poll_delay=NN #### initial delay after load before polling for
    # #### readiness
    ####

    From amada.conf:
    -----
    runtapes 6 # number of tapes to be used in a single run of amdump
    tpchanger "chg-zd-mtx" # the tape-changer glue script
    tapedev "tape:/dev/nsa0" # the no-rewind tape device to be used
    changerfile "/var/adm/amanda/lule2/changer"
    changerdev "/dev/pass0"

    maxdumpsize -1 # Maximum number of bytes the planner will schedule
    # for a run (default: runtapes * tape_length).
    tapetype IBM-LTO2 # what kind of tape it is (see tapetypes below)
    # IBM-LTO1 GLZ02001-GLZ02005
    # IBM-LTO2 GLZ03001-GLZ03022
    # Lable: locale (glz) set (0-99) tape (001-999)
    labelstr "^GLZ[0-9][0-9][0-9][0-9][0-9]$"
    -------

    Works alike a charm. Have tested ch also but am more comfortable with mtx as we use it with HP and Tandbergs to.

    /glz

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •