Author: Jim Weill <moondog AT ICSI.Berkeley DOT EDU>
Date: Wed, 31 Jul 2013 08:42:40 -0700
I hate to throw another wrench into the works, but I found that the best SQL backups are a combination of the SQL utilities and the backup software (like Networker, but also Symantec BE and others).
Author: Yaron Zabary <yaron AT ARISTO.TAU.AC DOT IL>
Date: Sun, 2 Jun 2013 15:07:07 +0300
Actually, this is a known bug with NW on RHEL6. With RHEL6 they switched from portmapper to rpcbind. The client has issues with registering itself with rpcbind, so rpcinfo -p doesn't show the service
Author: seanrthomas <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Mon, 3 Jun 2013 16:06:55 -0700
Good afternoon, all. I have a box that was updated in-place from Networker 7.6.2 to 8.0.1. Everything went smoothly for about a week until a system reboot (after some patches). After the reboot, the
Author: Mathew Harvest <Mathew.HARVEST AT COMMUNITIES.QLD.GOV DOT AU>
Date: Tue, 4 Jun 2013 10:30:25 +1000
Hey Sean, Sorry to hear, you seem to be in some strife ... Ok to set a few things straight .. Lgto_gst.db is the database for the management console, basically stores performance & reporting data for
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Mon, 3 Jun 2013 22:30:26 -0700
Hello Mathew, right now you should not be act too fast and keep cool. Otherwise you migt lose data. Here are some fundamental issues: - As already mentioned, you need to recover the media db which is
Author: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
Date: Tue, 4 Jun 2013 10:24:32 -0400
So I need to migrate my existing NW 7.6.2 server from Win2003 (32bit) to NW 7.6.2 on Win2008 R2. The new server will have the same name and IP as the old server. So I used the Networker Procedure Gen
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Tue, 4 Jun 2013 08:32:39 -0700
There is only one set of Windows enablers, no matter whether you use 32 or 64bit. You can easily verify that when you lookup the evaluation enablers in the Licensing Guide. So the enablers will be fi
Hi All; We have a Linux cluster (2 nodes) running oracle 11. NW 7.6 SP5 (Backup Server Solaris 10) NMDA (NetWorker Module for DB and Apps) version 1.2 We have the error: nsrdasv : The NSR /client res
Author: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
Date: Tue, 4 Jun 2013 14:56:48 -0400
transfer. My question is which is correct - TS who says this is a cross-platform migration, or the Procedure Guide, that says it is *not*? And therefore which directions do I follow?
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Tue, 4 Jun 2013 21:12:10 -0700
Michael, I will not tell you whom/what to believe or how somebody would name it. This could just lead to an endless fight. I am simply addressing the technical facts. Considering those, the PG is obv
Author: "Browning, David" <DBrown AT LSUHSC DOT EDU>
Date: Wed, 5 Jun 2013 11:56:18 +0000
The good news is that you have 45 days to work this out. After the upgrade, you will be able to use your Networker software for those 45 days, until you can get the new authorization codes. As for yo
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Wed, 5 Jun 2013 06:51:50 -0700
<< It's the differences in procedures (such as one uses mmrecov, and the other uses an export/import with "nsrmmdbasm", for example) that I am trying to account for.>> In general both are the same or
Author: Mike Borkowski <mikeb AT UWATERLOO DOT CA>
Date: Fri, 7 Jun 2013 16:45:52 +0000
HOST:index 98820:save: Unable to setup direct save with server BACKUP_SERVER: current save session has exceeded Networker server's parallelism. We see over 10 of these each night. Support is telling
Author: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
Date: Sat, 8 Jun 2013 04:17:53 -0700
Depending on your license(s) NW will only allow a certain number of parallel/simulteanous save sessions. If you try to start more backup processes at a time you will receive this message. This should
Author: "Roberts, Justin (GE, Appl & Light)" <Justin.Roberts2 AT GE DOT COM>
Date: Mon, 10 Jun 2013 03:21:01 +0000
I've seen this problem before. The physical nodes need to be configured clients on the server, and you should add the physical node names to the remote access list of the client config(something like
Author: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
Date: Tue, 11 Jun 2013 12:17:44 -0400
same. So I am about to start this. I have stopped NW on the old server, and am copying the \nsr folder tree to a temp folder on the new server. Then I will remove the old NW server from the Windows
Author: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
Date: Wed, 12 Jun 2013 10:59:56 -0400
I thought I would share my results of my doing a migration from a Win32 to Win64 server. I mostly followed the set of steps specified by the Procedure Generator. Mostly means: - After installing NW o
Author: "Greggs, Dana" <Greggsd AT LABCORP DOT COM>
Date: Wed, 12 Jun 2013 17:15:56 +0000
I did pretty much the same process to migrate form Windows 2003 to Windows 2008R2. The things you ran into are pretty normal. When you relicense your Servers you can add them all in bulk using nsradm