Author: George Sinclair <george.sinclair AT NOAA DOT GOV>
Date: Tue, 13 Mar 2012 16:49:15 -0400
Is there a way to perform a save set recover (e.g. recover -s server -d location -S ssid/cloneid path1 path2 path3 ...) without having to pass all the desired paths on the command line? Let's suppose
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Tue, 13 Mar 2012 23:06:45 -0700
The only way i see is the possibility to run a partial save set recover (recover -d destination -S ssid[/cloneid] -a full_pathname). Be aware that you need to be precise about the exact path name. It
Author: George Sinclair <george.sinclair AT NOAA DOT GOV>
Date: Wed, 14 Mar 2012 14:45:24 -0400
I never used it without the -a option. I never tried whether this command accepts multiple path names. I also did not pay attention whether this will speed up the recovery (can/will NW not start read
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Wed, 14 Mar 2012 12:02:48 -0700
Sorry, but your statement: "The '-a' option checks the index without putting you in interactive mode. This won't help on a save set recover for a save set that is no longer browsable." is simply wron
Author: George Sinclair <george.sinclair AT NOAA DOT GOV>
Date: Wed, 14 Mar 2012 18:18:25 -0400
"The '-a' option checks the index without putting you in interactive mode. This won't help on a save set recover for a save set that is no longer browsable." is simply wrong. Instead it even works on
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Wed, 14 Mar 2012 16:02:53 -0700
I simply use it to run a partial recovery of a non-browsable save set. It saves an additional scan process. And it works on save set which will never enter the 'browsable' state. Of course it only he
Author: Tim Kimball <Tim.Kimball AT SUNGARD DOT COM>
Date: Thu, 15 Mar 2012 04:58:09 +0000
I'll start with my usual 'we mostly do stuff in csh here' disclaimer. :-) That said, my solution would be: 1) send list of paths to file (using /tmp/FILE here) 2) recover -d destination -S ssid[/clon
Author: George Sinclair <george.sinclair AT NOAA DOT GOV>
Date: Thu, 15 Mar 2012 12:01:15 -0400
If you are used to something you will use it forever. So far i never used the -I option. Thanks, bingo. I guess I'm just obtuse here, but I would do this. Let's say my non-browsable save set is /data
Hi George, as you said, option -a is not buying you anything on a saveset recovery. You are right. Actually it is not an option when using -S. Not sure why you would expect NW not to scan the saveset
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Mon, 19 Mar 2012 06:47:07 -0700
Sorry guys, this statement is not true. Let's assume the following scenario: - You have forgotten to switch on the 'Monitor Rap' option to log resource changes - You desperately need to recover an ol
Author: George Sinclair <george.sinclair AT NOAA DOT GOV>
Date: Mon, 19 Mar 2012 12:02:37 -0400
- You have forgotten to switch on the 'Monitor Rap' option to log resource changes - You desperately need to recover an older configuration or a single resource - You know that resources are stored w
That is wrong and actually very dangerous. recover wouldn't try to create the /nsr/res.R because that is only done by mmrecov. Both commands do very different things. The command: recover -S <your_bo
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Tue, 20 Mar 2012 15:37:13 -0700
I agree that we are not focused on the original subject any longer. I am just surprised about the different statements i have seen during the discussion. I have to agree that the option "-a" obviousl