Re: Stupid restore question

[On 16 May, @15:05, James wrote in "[hdup-user] Stupid restore que ..."]
> Trying to affect a restore. This is run from a host called "arwen" (my
> backup server), the backup is from a host called "simon" and I am
> trying to restore it to a third host called "simonback"=192.168.1.222
> (which has the same hdup.conf as "simon")
> 
> hdup -c /etc/hdup/hdup.conf restore simon 2004-05-16 /home/restore @jamie-Q0ErXNX1Rubxw0KMbGF/[email protected]
> hdup: simon: STARTING RESTORE.
> jamie-Q0ErXNX1Rubxw0KMbGF/[email protected]'s password:
> /usr/local/sbin/hdup: simon: STARTING BACKUP.
> mkdir: cannot create directory `/backup/toarchive/mysql': No such file or directory
> 
> .. so it appears to begin restoring, and then it says "starting
> backup" and the prerun.sh script fails since it doesn't make sense for
> this restore. prerun.sh starts with:
> 
> #!/bin/sh
> if [ "$1" == "restore" ]; then exit 1; fi
> 
> How come it thinks its backing up once hdup runs on simonback, instead of
> restoring? I figure I must be doing something very basic wrong here.

I can only say: "Huh?"

Let me check this out myself. The "STARTING BACKUP" remark from hdup,
is clearly wrong. 

grtz,
--Miek

--
today's fortune:
Now I am depressed ...