Re: recursive copy in VMS
- From: koehler@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx (Bob Koehler)
- Date: 5 Dec 2006 08:18:55 -0600
In article <8764cq3kbb.fsf@xxxxxxxxxxxxxxxxxxx>, prep@xxxxxxxxxxxxxxxx writes:
JF Mezei <jfmezei.spamnot@xxxxxxxxxxxx> writes:
Due to the disk space growing at a faster rate than tape drives (in my
case anyways), I have often employed the SET FILE/NOBACKUP for files
that I know are copies of stuff than can be obtained elsewhere.
For instance, when I backup a mac to my vax, all those files are
then marked /NOBACKUP so that they don't take up huge amounts of
space on a tape (and slow the backup process). Similarly, large
patches that can be downloadeed from the HP site get marked
/NOBACKUP.
You are aware that you will get those files restored but with a big
load of zero as content? So they will LOOK ok, but be useless for
anything except getting you to delete the other copy.
This is NOT a good idea!
I think that's exactly what he wants. He's satisfied that he won't
lose his Mac's disk and his VMS system's disk at the same time, just
like I'm satisfied that I won't lose my VMS systems' disks and their
tape backups at the same time.
.
- Follow-Ups:
- Re: recursive copy in VMS
- From: jls
- Re: recursive copy in VMS
- From: prep
- Re: recursive copy in VMS
- References:
- recursive copy in VMS
- From: thick_guy_9
- Re: recursive copy in VMS
- From: Joseph Huber
- Re: recursive copy in VMS
- From: prep
- recursive copy in VMS
- Prev by Date: Re: terrorists threaten cyber attacks on US banks ...
- Next by Date: Re: Novice's questions
- Previous by thread: Re: recursive copy in VMS
- Next by thread: Re: recursive copy in VMS
- Index(es):
Relevant Pages
|