Re: Strange RETRIEVE behaviour
2004-02-27 03:36:21
Is there no way to avoid specifying the entire source path?
The reason I want to do this is that I have to be able to retrieve files
(from several years ago) with an automated procedure, and I don't want to
get into the hasle by finding out the source path by issueing one or more
query commands from the client side.
Richard Sims <rbs AT BU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
26-02-2004 13:17
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Strange RETRIEVE behaviour
I've noticed some strange behaviour with RETRIEVE, which I haven't been
>able to explain yet.
>
>I've made an ARCHIVE with: dsmc archive -archmc=xyz *.txt -v2archive
>-filesonly -subdir=no -descr="XYZ"
>This archive was made from the directory /volume/a.
>
>When I do a dsmc retrieve "*" /temp/ -filesonly -descr="XYZ" when still
in
>/volume/a, all files are retrieved.
>When I do the same when switched to /volume/b (different filesystem)
>nothing is retrieved.
...
Observe the syntax of the Retrieve command:
"sourcefilespec
Specifies the path and file name that you want to retrieve. Use
wildcard
characters to specify a group of files or all the files in a
directory."
In the absence of an explicit path specification your request is relative
to
your current location: via the lone asterisk you are requesting all files
in
the current directory. You can observe the same thing at the Unix prompt
by entering the rudimentary command 'echo *'.
To retrieve your files from whatever directory location you happen to be
sitting in at the moment, you need to be explicit as to their origin.
Richard Sims http://people.bu.edu/rbs
|
|
|