Search results for query: *

Angsaskois, As you say quite a difference in size. -rwxr-xr-x 1 root bin 68790 Oct 27 10:20 Networker -r-xr-xr-x 1 root bin 815 Apr 3 2008 oldNetworker Replacing the smaller file has indeed resolved my issue and I will post back if I see any knock on effects with...

After upgrading to NW7.4.2, I had a need to manually label a tape. Unfortunately someone had kicked off an "nsrjb -I" on this jukebox with 30 unknown tapes just before me. So I killed the nsrjb process from the OS and normally this would give me control again to do my label, but in 7.4.2 it...

Yes, always make sure the NetWorker Server version is newer or the same as the client and it will work fine. I am also backing up 6.x clients to a 7.4.2 servr without any issues.

I have upgraded several NW servers now to 7.4.2, and before the upgrade I renamed the nwadmin binary and put it back afterwards so I could still access nwadmin as well as the java gui. But when I fire up the old nwadmin all I can get is a black/white GUI with drop down lists and speed bars if I...

Yes exactly, there are some small print comments (as below) and double check with the release notes for the relevant version but that should be the case. -- NMO supports all filesystems supported by NetWorker Client, Oracle and PowerSnap (if applicable) With Lotus Notes it actually says what...

- It's rman that does all the work, remember the NMO only provides an api to allow the rman backup to be written to tape so as long as the NetWorker version is supported on the OS you should be ok with NW7.4 and NMO 7.x, but as below consult release notes too - Consult online NMO Release...

The SCG only allows you to look at NMO against OS and wether this can handle Oracle/Lotus Notes version. Unfortunately not knowing your OS, we cannot answer your query. I can confirm I am running NMO4.2 against NW7.4 Server for Solaris 9.

I can confirm this will work fine, as I have configured an environment with 2 VTL's presented. I saw the following on the NW Server; • CDL1 - IEBRI011CDL1-A (scsidev@4.0.0) • CDL2 - IEBRI011CDL1-B (scsidev@8.0.0) Don't know the presentation part but expect you will get another control path...

The fact that it won't be supported may also be a consideration, best efforts only from EMC. no patching. EOL for 7.2.x - 30/06/08 & 7.3.x - 31/12/08

I can confirm we are using a 7.4 Management Console and connecting to 7.2.1 NetWorker Servers without any issues, so connecting from the 7.3.3 management console towards a 7.2.2 Server should not be a problem.

It is nothing to do with the module as I said previously there is a bug with savegrp that prevents the group from completing cleanly, even though there is nothing else to backup and it requires a patched version, patch LGTsc07813

There are savegrp patches available for this issue from support, depending of course which version you are running. The patch worked for me.

The first thing you want to do is get off 7.3.0, at least put a reasonably stable version like 7.3.3 down.

Try http://www.tek-tips.com/viewthread.cfm?qid=1138411

did you do modunload and modload the lus driver after you made the changes? if you have the correct target in there you should be able to see it from the o/s.

Also consider how you will restore the data in the future, drive technology will change along with tape technology. You may need to keep cloning it to new technologies and checking it's integrity. If you can't restore it, it's pointless keeping it forever.

Do you actually want to backup using the VSS method? if not add VSS:*=off in the 'save operations' field for the client. NetWorker will then use the legacy method to backup.

Can you run - sjirdtag 'path to control port', if this does not return the contents of you library then the problem is at the OS level, not NetWorker. Use - inquire to find the control path if you don't know it, it could have changed if you have added devices.

Have you check the control path to the autochanger, sounds like you are trying to issue commands down the wrong path.

Interested to know if this works or not as I was informed there is a bug in 7.3.2 and DSN licenses were incorrectly rejected. They were getting around this by giving full 'Storage Node' licenses but you had to sign a disclaimer saying you would only use them in the cluster.