Re: Stupid restore question

[On 16 May, @15:05, James wrote in "[hdup-user] Stupid restore que ..."]
> 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.

this is fix (must still test it though).

> 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.

the remote hdup gets the 'scheme' REMOTE. When doing the actual remote
operation a header is sent with the real scheme (RESTORE, MONTLY,
WEEKLY or DAILY). At that point we're way past the point of executing
any prerun scripts.

Are you saying you don't won't any prerun script run when doing to
REMOTE operation (that may not be desireble for other people). Or is
my explanation sufficient?

grtz Miek