Hello Jane, there are quite a few variables to consider; can you provide more details as to the specific operation you're attempting?
It sounds like you are trying to get around filesystem enumeration - which in general means a saveset recovery. This in turn means you will recover the entire saveset (or at least, read the entire saveset).
Do you want to recover the whole saveset, or for example, a single directory within the saveset?
Do you want to recover to the same or a different host?
The same or different path?
Overwriting files, renaming, or skipping?
Essentially your recover command should really be run on the target host something like:
recover -i[y|n|r] [-d (redirect path)] [-R (hostname... no need if run on target host, which is preferred)] -S (ssid - get this from NMC or mminfo) [internal path of saveset if full saveset not desired]
This disallows any sort of comprehensive browsing but also circumvents tedious file list walking - which sounds like what you're trying to avoid.
Please clarify if I've missing anything and test this first on a redirected path (-d) with a simple saveset.
jkernagh
35 Posts
0
March 15th, 2011 16:00
Hello Jane, there are quite a few variables to consider; can you provide more details as to the specific operation you're attempting?
It sounds like you are trying to get around filesystem enumeration - which in general means a saveset recovery. This in turn means you will recover the entire saveset (or at least, read the entire saveset).
Do you want to recover the whole saveset, or for example, a single directory within the saveset?
Do you want to recover to the same or a different host?
The same or different path?
Overwriting files, renaming, or skipping?
Essentially your recover command should really be run on the target host something like:
recover -i[y|n|r] [-d (redirect path)] [-R (hostname... no need if run on target host, which is preferred)] -S (ssid - get this from NMC or mminfo) [internal path of saveset if full saveset not desired]
This disallows any sort of comprehensive browsing but also circumvents tedious file list walking - which sounds like what you're trying to avoid.
Please clarify if I've missing anything and test this first on a redirected path (-d) with a simple saveset.
Cheers, James.
pheikens
96 Posts
0
March 16th, 2011 03:00
May be you just want to try the following on the server which owned the files:
recover [-d "new path"] -t "browsetime" -a "path you want to recover"
Peter