AWalker@RED.RUTGERS.EDU (*Hobbit*) (06/21/87)
Normally I have no trouble at all with BACKUP, so this feels sort of weird. I have a 785 with three RA81's, one of which is the repository for files scooped up by an automatic backup process. Hitherto the process was simple: I was only using one drive for everything [call it 0] while the extra drive [call it 2] contained mostly static stuff that wouldn't change since I last rolled it off to tape. Thus the backup drive [call it 1] contained a mostly identical structure to 0, except for older files that weren't found by the backup/since=... command. This has changed, and now 0 and 2 have changeable data on them. Thus I need to incorporate 2 into the automatic backup picture. 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 dua0:<000000...> ---> dua1:<d2...> I get *subdirectories* from dua0:<*...> splattered all over dua1:<d2> for some reason [this feels like a bug!] and it still doesn't do the right thing. For the moment I've reverted to doing dua0:<*...> ---> dua2:<d2>d0.bck/save but this is much less than optimal since it re-creates the entire directory structure of 0 in the saveset whether it had anything to save or not -- creating a 300 block or so useless file. I tried a concealed logical like back2 = dua1:<d2.> but Backup had a lot of trouble with this -- something about logical name translation count [I forget]. How does one convince Backup to place files correctly in funny places??? _H* -------
Liebschutz@BIONET-20.ARPA (Rob Liebschutz) (06/21/87)
>> ... >> 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 -------