Recent content by Rexxy

offical response..... "Pricing and Ordering Information NetWorker V7.4 and NetWorker Module for Oracle V4.5 will be available in the June release of Direct and Channel Express." That is, the software is not readily available yet.

have you entered the networker server into the /nsr/res/servers file ??

are there any firewalls in between that have specific ports open in both directions, if this is the case, get them to also check if there is a firewall timeout in place, and if so, change it to 24hours.... if the firewall ports have a timeout in place, the service ports will go stale and the...

from your networker server, if as you state the you can see the volumes in the media index, run an mminfo for the client and identify the savesets you need to restore, and take note of their ssid's... then as mentioned above, from the client system, run the recover command parsing the ssid...

hopefully it was just a typo from you both but the actual linking is as follows for x86 linux % ln -s /usr/lib/libnwora.so libobk.so Rexxy

Make sure your Networker Server has the Backup Interface as the Primary NIC and configure the Networker server as the Backup Server name...... Then configure all the client using their Backup Interface names, and if necessary also enter their Prod NIC name in as an alias.....but if they still...

sound slike that should work, i have done it like this in the past << /logf60 >> +skip: dir1 +skip: dir2 why not reverse engineer this and exclude the directories from root level, as the other way may be asking it to still "walk" the filesystem, but exclude everything inside. << / >> +skip...

does netbackup use the same TCP port range as networker, this is tunable so not a big issue, just curious.... would need to ensure Tape drvies were unique to each, also maybe use different NIC's on the system. my recommendation on this.....use Virtual systems..i.e. vmware. if you mean you...

just run "jbedit -s nsrsvr -ao" and it will ask you the necessary questions to perform this.

but networker user etc all use the /nsr/res/servers file, if there is more than one system listed you will also get this issue.

has the networker server name changed ? if so, then its most likely just the servers file on the clients that needs to be updated to reflect the new nsr server system name. bring up the dos prompt and run the following c:\> recover -s nsrservername does this work ?? if this is also failing...

most of the issues people have been logging were on v7.3 servers that had been upgraded..Those that had built their networker server from scratch using v7.3 seemed to have less issues.... if it was my choice, i would configure the new nsr server manually and start off with press client and...

i didnt mention, Commvault is a good backup solution, but if your backup env is large...then networker is your solution.... I like both.

We support both Networker & Commvault with many many support customers, and basically when asked what the difference is between them, its easy... Networker is an Enterprise solution, Commvault isn't.... Commvault may one day become a backup solution that can support Enterprise Environments...

manually load this tape in a drive, then use scanner to see if you can read the tape # scanner /dev/nst0 if you can read the tape and see the information you have 2 options.....scan the tape back into the media index, and then recover using the saveset id's, or just scan the tape and parse...