Author: Librado Pamintuan <LPamintuan AT REGINA DOT CA>
Date: Mon, 31 Jan 2005 12:04:05 -0600
Is there a process or step I missed? I saved all the client indexes to a tape using savegroup -O 'TestGroup' I made sure that all clients are included in the TestGroup group. Printed out the latest b
Is that a problem? Then you should probably recover the indexes next. -- Darren Dunham ddunham AT taos DOT com Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco
Author: Librado Pamintuan <LPamintuan AT REGINA DOT CA>
Date: Mon, 31 Jan 2005 12:33:21 -0600
when Is that a problem? Yes. The clients and client configuration are not showing up, only the linux server is showing in the client list. volumes Then you should probably recover the indexes next.
Okay, so the nsrla.res file isn't the problem, it that the nsr.res file isn't populated with the clients. Do you have an /nsr/res.R directory? That should be the recovered one. You'd normally shutdo
Author: Librado Pamintuan <LPamintuan AT REGINA DOT CA>
Date: Mon, 31 Jan 2005 14:46:19 -0600
I already did that. I shutdown Networker and mv res.R to res and when I re-start Networker it creates the nsrla.res file still with just the Linux server as the only client configured. Might be a ver
Networker 7.1.x does not use the nsr.res and nsrjb.res any more. All relevant configuration information are under the directory res/nsrdb/*/*. The only leftover old type res file is nsrla.res that is
Author: Byron Servies <bservies AT PACANG DOT COM>
Date: Mon, 31 Jan 2005 13:13:47 -0800
I already did that. I shutdown Networker and mv res.R to res and when I re-start Networker it creates the nsrla.res file still with just the Linux server as the only client configured. nsrla.res is