Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!sri-unix!sri-spam!mordor!lll-tis!ptsfa!dual!ucbvax!BIONET-20.ARPA!Liebschutz
From: Liebschutz@BIONET-20.ARPA (Rob Liebschutz)
Newsgroups: comp.os.vms
Subject: Re: BACKUP syntax Q
Message-ID: <12312307936.17.LIEBSCHUTZ@BIONET-20.ARPA>
Date: Sun, 21-Jun-87 13:27:29 EDT
Article-I.D.: BIONET-2.12312307936.17.LIEBSCHUTZ
Posted: Sun Jun 21 13:27:29 1987
Date-Received: Tue, 23-Jun-87 00:43:33 EDT
References: <12312167060.37.AWALKER@RED.RUTGERS.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 24

>> ...
>> However, BACKUP is being really stupid about allowing me to do this
>> the way I want:

>>	backup/since=<last_time_it_ran> dua0:<*...> dua1:<d0.*...>
>>	backup/since=<last_time_it_ran> dua2:<*...> dua1:<d2.*...>

>> In effect, I want to have two treeheads on the backup drive, <d1> and <d2>,
>> which have under them the directory structures of each disk.  Now, Backup
>> doesn't understand "<dir.*...>".  If I specify something like ...


I believe either of the following methods will work:

$ backup dua0:[*...] dua1:[d0...]

	or

$ set default dua1:[d0]
$ backup dua0:[*...] [...]


Rob 
-------