From: Jonathan Williams (jonathw@shubertorg.com)
Date: Mon Apr 14 2003 - 15:37:45 EDT
Ok. Thanks for all the emails people sent me. When I last wrote, I was having
a problem with a vdump script, in that it wouldn't prompt the user for the
second tape...it would just give a bunch of errors and then quit.
Most responses I received assumed I was running the script as a background job
(ie cron, etc), but this was not the case--I was just running the script from
the command line.
As I mentioned, my script had been using a symbolic link for the tape drive
"vdumptape". This was the problem. Apparently symbolic links are a no-no, or
so it seems. I replaced the symbolic link with the real tape device name, and
everything works as expected--prompts for next tape and everything. Thank you
to all the people that responded.
Jonathan Williams
Unix Systems Administrator
The Shubert Organization, Inc.
----- Original Message -----
From: "Jonathan Williams" <jonathw@shubertorg.com>
To: <tru64-unix-managers@ornl.gov>
Sent: Wednesday, April 09, 2003 4:20 PM
Subject: UPDATE: Vdump script
> Ok. I have received a bunch of emails (many telling me how crazy I am for
doing
> away with NetWorker) about a vdump script. Most of them were very involved,
> telling me how to get the autochanger to work, and have the whole thing nice
and
> automated. That is a nice project to work on, but is above and beyond our
> immediate goals.
> I want to keep this vdump script as simple and basic as possible. There will
be
> operators here to change tapes when vdump asks for them, so getting the robot
to
> work is not something I'm thinking about right now. I wrote a super-basic
> script which is just a bunch of vdump commands to execute one after the other
> (yes yes, I know I could put logic in the script to figure out for itself what
> to backup and all that).
> The problem I'm having is what happens when the tape fills up. I assumed it
> would sit at a prompt asking for a new tape, and then after mounting the tape,
> the operator would hit <enter> and the vdump would continue. This is not what
> happened.
>
> The system I ran the script on is an Alpha ES40, running Tru64 5.1a (no
> patches). All of the vdump commands went very well, until the tape got full,
> this is what it said:
>
> vdump: Status at Wed Apr 9 13:39:39 2003
> vdump: Dumped 81454142687 of 92140089441 bytes; 88.4% completed
> vdump: Dumped 31105 of 33238 directories; 93.6% completed
> vdump: Dumped 499050 of 540028 files; 92.4% completed
> vdump: Unload of tape 0001 failed; [25] Not a typewriter
>
> vdump: Change Tapes: Mount tape# 0002
> vdump: can't get dev info for writing; [25] Not a typewriter
>
> devget ioctl failed!
>
> mtiocget ioctl failed!
>
> So as you can see, it didn't sit at a prompt and wait for the tape to be
> changed. Is this because it is in a script, and for some reason can't prompt
> for user intervention? I'm sure there is a way around this, but what? And
like
> I said, I'm not interested in the robot in the tape changer automatically
> changing tapes for me...I want a user to be able to see that a second tape was
> requested, and manually change the tape, and then hit enter to continue the
> backup.
>
> Oh, and here is the little scriptlet that I ran:
> #!/bin/ksh
> cd /
> vdump -0uf vdumptape /
> vdump -0uf vdumptape /usr
> vdump -0uf vdumptape /star
> vdump -0uf vdumptape /ops
> vdump -0uf vdumptape /client
> vdump -0uf vdumptape /devel
>
> (vdumptape is a link to the actual tape device)
>
> So can anyone tell me what to change/add to get this thing to work how I want?
> Or at least point me in the right direction? I searched on the archives, and
> saw lots of similar questions, but no answers. TIA
>
>
>
> Jonathan Williams
> Unix Systems Administrator
> The Shubert Organization, Inc.
>
>
> ----- Original Message -----
> From: "Jonathan Williams" <jonathw@shubertorg.com>
> To: <tru64-unix-managers@ornl.gov>
> Sent: Thursday, April 03, 2003 2:11 PM
> Subject: Vdump script
>
>
> > Hi. I've got a bunch of servers here (ES40, ES45, all running Tru64 5.1a)
> that
> > each have only about 7 or so AdvFS filesets that need backing up. For the
> past
> > several years we have been using Legato NetWorker to backup all of our Alpha
> > servers. We have decided to move away from NetWorker, and use only vdump
and
> > vrestore to backup these systems. They are all connected to a TL895 tape
> > library that stores the backup tapes. We do not use the library in
> > auto-mode...the tapes are moved by an operator via the Control Panel on the
> > library.
> >
> > What I'm looking for is any nice scripts that some of you may have to do
these
> > backups as easily and straight-forward as possible (making the process
> "operator
> > proof"). One approach might be to run a script on each system one at a
time,
> > all backing up to the same tape(s). Another approach might be to have one
> > server to the whole thing, and after it finishes backing itself up, it would
> do
> > a remote connection to the other servers and back all of them up in turn (of
> > course, I'm not sure if that's even possible). But basically, if anyone has
> any
> > scripts for this purpose that they like, I would be interested in seeing
them.
> >
> > So to sum up. About half a dozen servers. All running 5.1a. Backing up
> AdvFS
> > filesets. All have access to the same tape drives (not at the same time of
> > course). There is an operator always here to take care of tape changes when
> > they are needed. TIA
> >
> > Jonathan Williams
> > Unix Systems Administrator
> > The Shubert Organization, Inc.
> >
> >
> >
> >
>
>
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:16 EDT