Re: Advice on LTO tape storage

From: Bill Verzal (BVerzal_at_KOMATSUNA.COM)
Date: 11/10/03

  • Next message: John Jolet: "Re: Advice on LTO tape storage" 
    Date:         Mon, 10 Nov 2003 14:07:22 -0600
To: aix-l@Princeton.EDU

    I'm using Sysback, and I don't see an "-M" option for tar.

    Are you using "gnu" tar ?

    BV
    --------------------------------------------------------

    "If everything is coming your way, then you are in the wrong lane"

    Bill Verzal
    AIX Administrator, Komatsu America
    (847) 970-3726 - direct
    (847) 970-4184 - fax

                          John Jolet
                          <john.jolet@FXFN. To: aix-l@Princeton.EDU
                          COM> cc:
                          Sent by: IBM AIX Subject: Re: Advice on LTO tape storage
                          Discussion List
                          <aix-l@Princeton.
                          EDU>

                          11/10/2003 01:54
                          PM
                          Please respond to
                          IBM AIX
                          Discussion List

    what are you using to write to the tape? if you're using tar, use -M now.

    -----Original Message-----
    From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU]On Behalf Of
    Bill Verzal
    Sent: Monday, November 10, 2003 1:37 PM
    To: aix-l@Princeton.EDU
    Subject: Advice on LTO tape storage

    Hi *,

    Got a question for ya related to LTO tape storage.

    Currently, I have an LTO library (100 GB native, 200GB compressed). We do
    our own tape management via a small 100 byte header on each tape. This
    allows us to control tape retention.

    If the tape runs to EOT during a backup, the library will eject the tape
    and put the next one in. The backup will then continue and in this case,
    will overwrite our header.

    Currently, I limit myself to what amounts to about 145GB of data per tape.
    I am concerned about how close to the end of the tape I am.

    I back up a set amount of filesystems, eject the tape, then process the
    remaining filesystems.

    At what point should I stop "risking" the EOT condition and re-distribute
    my offloads to more tapes, thereby allowing more data per tape and more
    growth into the future ? Should I just stop risking it now and just make
    the change ?

    Thanks, Bill.

    --------------------------------------------------------

    "If everything is coming your way, then you are in the wrong lane"

    Bill Verzal
    AIX Administrator, Komatsu America
    (847) 970-3726 - direct
    (847) 970-4184 - fax

  • Next message: John Jolet: "Re: Advice on LTO tape storage"

    Relevant Pages

    • RE: redhat-list Digest, Vol 27, Issue 26
      ... The reason I was tarring a tar file to the tape I didn't want to backup a whole file system just to test the tape drive. ... I take that same tape and try to read it on the tape drive that is connected to the linux machine and it doesn't work. ... echo command as in windows ...
      (RedHat)
    • Re: problem with restore
      ... can tar be used to backup files on a machine with remote tape drive..?? ... the '-' on the tar command makes the 'f' go to stdout. ... Have you tried taking backup using tar utility instead of rdump. ... If you take backup and try restore using tar, ...
      (RedHat)
    • Re: Copying tar archives/tarballs to tape
      ... You may want to play about with the block size arguments in tar to find ... Some tape drives, when written to in ... Some apply error correction only on a per-block basis, ... for bzip2) flag when writing to tape, but bear in mind that compression uses CPU ...
      (uk.comp.os.linux)
    • RE: problem with restore
      ... Have you tried taking backup using tar utility instead of rdump. ... If you take backup and try restore using tar, ... Also you can verify the content of tape after backup using ...
      (RedHat)
    • Re: Example of tar incremental backup?
      ... Then type "man tar". ... write a rudimentary backup routine. ... Use tar to back up your filesystems, to tape, to disk, remotely, ...
      (comp.os.linux.misc)