Results 1 to 5 of 5

Thread: vdisk and tpchanger

  1. #1
    Join Date
    Apr 2011
    Posts
    3

    Default vdisk and tpchanger

    Hi,
    New to amanda. Two questions if someone could please help.

    I'm using Amanda 3.1.0 on a Centos 5 system. Backing up not a large amount of data ~750G.

    I probably just don't understand the basics of how things work since I've little to no experience, and all of it now ancient, using tapes as a backup medium.

    1. What does a tape changer do when used with a vdisk ? Does it change to the next slot if the dump is too large ?

    If I include this in my configuration
    tpchanger "chg-disk:/path/to/vtapes"
    and set up the "slots" in this directory I thought that if the amdump was larger than the first slot, it would 'change the tape' to the next drive slot. But instead I just get an error message:
    FAILED [dump larger than available tape space

    2. Is there documentation more descriptive than the 15minute-pizza-and-backup walk through and geared to a relatively simple backup set up ?

    Thanks.
    Bob

  2. #2
    Join Date
    Apr 2011
    Posts
    3

    Default

    For those that follow re the Amanda Community Edition.

    Hmm.. 175 views and no responses in 2 weeks to a pretty basic question.

    So even if I get this poorly documented, highly complex beast to run, I'd be foolish to rely on getting questions answered if I had a problem on the restore end of things.

    I'm thinking the 15-minute-pizza-and-backup is classic bait and switch.

    OK back to using Lonetar or Backupedge for half the price of the Enterprise edition.

  3. #3
    Join Date
    Oct 2005
    Posts
    1,559

    Default

    Did you look at wiki.zmanda.com for Amanda documentation?

    What is the size of vtape configured in the amanda.conf?

  4. #4
    Join Date
    Apr 2011
    Posts
    3

    Default

    Hello Paddy,
    Thanks for your reply.

    I am actually less interested in solving this particular problem, and more concerned about being unable to figure out how things work. And yes, I've spent hours on the Wiki and poking through the [url]http://wiki.zmanda.com/man/[/url] files.

    But here goes. Using the 15 Setup outline, if I set up a 500 mbyte vdisk [small on purpose for testing] with multiple slots, I can successfully amdump the /var/log/amanda directory:

    From amandabackup@xxx Thu Apr 28 10:04:40 2011
    Date: Thu, 28 Apr 2011 10:04:39 -0700
    From: amandabackup@xxx
    To: drb@xxx
    Subject: DailySet1 AMANDA MAIL REPORT FOR April 28, 2011

    Hostname: xxx
    Org : DailySet1
    Config : DailySet1
    Date : April 28, 2011

    These dumps were to tape DailySet1-4.
    The next 5 tapes Amanda expects to use are: 5 new tapes.
    The next 5 new tapes already labelled are: DailySet1-5, DailySet1-6, DailySet1-7, DailySet1-8, DailySet1-9


    STATISTICS:
    Total Full Incr.
    -------- -------- --------
    Estimate Time (hrs:min) 0:00
    Run Time (hrs:min) 0:00
    Dump Time (hrs:min) 0:00 0:00 0:00
    Output Size (meg) 0.2 0.2 0.0
    Original Size (meg) 0.2 0.2 0.0
    Avg Compressed Size (%) 100.0 100.0 --
    Filesystems Dumped 1 1 0
    Avg Dump Rate (k/s) 275.6 275.6 --

    Tape Time (hrs:min) 0:00 0:00 0:00
    Tape Size (meg) 0.2 0.2 0.0
    Tape Used (%) 0.0 0.0 0.0
    Filesystems Taped 1 1 0
    Parts Taped 1 1 0
    Avg Tp Write Rate (k/s) 210.0 210.0 --

    USAGE BY TAPE:
    Label Time Size % Nb Nc
    DailySet1-4 0:00 0G 0.0 1 1

    NOTES:
    planner: Adding new disk localhost:/var/log/amanda.
    taper: tape DailySet1-4 kb 210 fm 1 [OK]


    DUMP SUMMARY:
    DUMPER STATS TAPER STATS
    HOSTNAME DISK L ORIG-GB OUT-GB COMP% MMM:SS KB/s MMM:SS KB/s
    -------------------------- ------------------------------------- -------------
    localhost -log/amanda 0 0 0 -- 0:01 275.4 0:01 210.0

    (brought to you by Amanda version 3.1.0)
    If I try to amdump the entire /var/log 6G, I get an error message:
    NOTES:
    planner: Last full dump of localhost:/var/log on tape DailySet1-1 overwritten in 1 run.
    planner: disk localhost:/var/log, full dump (6564750KB) will be larger than available tape space, you could
    define a splitsize
    driver: WARNING: got empty schedule from planner
    So back to my question, what does a tape-changer do with a vdisk ? Does it not change to the next slot ? Maybe I'm just not understanding the difference between slots and splitting -- it's pretty confusing.
    Bob

  5. #5
    Join Date
    Oct 2005
    Posts
    1,559

    Default

    Amanda vtapes is divided into slots. Each backup run can take one or more
    slots (depending on runtapes parameter in the amanda.conf). Each slot has a size. If sufficient size is not provided for a backup run (slot size * runtapes), the backups will
    be partial (backup as much as possible).

    Amanda does not reserve the disk space based on the slot size.

    If there a backup image (each DLE backup is a separate backup image) that does
    not fit in a slot, you will have split the image into parts using tape_splitsize parameter.

    For disks, it is easier to increase the size of slot (size of vtape).

Posting Permissions

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