Re: vaulting problem

2001-08-03 Thread Alex Paschal
f [[ $1 = "-s" ]]; then if [[ ! -s $3 ]]; then print "unable to open file $3"; return 1; fi grep $2 $3 2>/dev/null if [[ ! $? -eq 0 ]]; then print "Unable to find pattern" return 1 fi elif [[ ! ( -s $2 && -s $3 ) ]]; then print &q

Re: vaulting problem

2001-08-03 Thread Robin Sharpe
>We will be assigned a range of slots. We tell them what tapes to put in >what slots, so it's under our control -- but we also have to keep track. I suppose it would be possible to write a basic script to manage that. It would have to keep its own database of course (although probably a single

Re: vaulting problem

2001-08-03 Thread Nicholas Cassimatis
Yes, you should feel comfortable with your vendor, but don't. The worst time to find out your inventory is off is when you are trying to recover from a disaster. I highly recommend (and this is from experience) that you audit your vault at least twice a year. Even with all the safeguards, probl

Re: vaulting problem

2001-08-02 Thread David Longo
I would look at getting another offsite vendor! Looks like they want you to do part of their work. You should be able to tell them "Send me tapes xxx, yyy and zzz tomorrow". This is introducing more manual steps in the process and more possibility of confusion (lost tapes, misplaced tapes, et

vaulting problem

2001-08-02 Thread Adam J. Boyer
Hi everyone, We have a small problem in that our vaulting company only references tapes by slot number, not by volume serial number. So, we'll need to keep some kind of database of what tapes are offsite and in which slots. We will be using DRM, and I was thinking we could update the database w

Re: vaulting problem

2001-08-02 Thread Adam J. Boyer
We will be assigned a range of slots. We tell them what tapes to put in what slots, so it's under our control -- but we also have to keep track. David Longo cc: Sent by: "ADSM: DistSubject: Re