Phil_1
1 Copper

Re: NMC - What drives you crazy ?

Another,

filter (again in ECC). I could filter the 'disabled' group, as in the previous example. However, We require an icon, next to the operator icon on the right, to show that the filter is in use.

time for a breather

Phil

0 Kudos
lalexis
3 Argentium

Re: NMC - What drives you crazy ?

I could not get something to run, I think it was the GUI. In their defense I was one of the first to try putting it on AIX, in fact it wasn't even listed as one of the operating systems at the time. They did have it packaged and everything for AIX I just could not get it to run. Might have been a Java runtime issue or something along those lines because my DBA was also messing with Java updates at the time. Luckily I had/have a Windows server that gets very, very little traffic so it is not a big deal to put it on there.

I guess the thing was that I just wanted to keep everything in one place.

0 Kudos

Re: NMC - What drives you crazy ?

About the naming of a jukebox. Just disable the jukebox. Open properties and rename the jukebox to what you like, we did on our server running NSR 7.4.4.

Now we have a library named rd=<storagenode>:DR  for the disaster site. Good luck, //Håkan Engman

0 Kudos
Phil_1
1 Copper

Re: NMC - What drives you crazy ?

Hakan_Engman wrote:

About the naming of a jukebox. Just disable the jukebox. Open properties and rename the jukebox to what you like, we did on our server running NSR 7.4.4.

Now we have a library named rd=<storagenode>:DR  for the disaster site. Good luck, //Håkan Engman


Hakan,

I've tried to do something similar. I did not try keeping the rd=<SN> part, instead calling it just DR. That did not work. I did think it must be do-able, since the Name field is editable, but it gave up

However, I was under the thought that the Name would be a human readable type rather than partial human/ technical.

I wanted to change the name to make it easier to script (shorter, simple letters). I wanted to name my libraries Primary and Remote, or similar.

I have modified the control port, when there was a connectivity problem on one path. Simple put the library controller down the other device, rescan host, modify control port parameter, and it worked.

Phil

0 Kudos

Re: NMC - What drives you crazy ?

Hi Mikey,

Must ask you again to just clearify this on memory usage on the NMC server.

Please correct me if i'm wrong.

You recommend 256 MB/RAM per 100 client definitions on the backup server.


Our largest server have 935 uniqe clients, and 1502 definitions.

That would make a recommendation of memory on the NMC to -->> 1500/100 * 256 = 3 840 MB

The NMC server is centralized, so can monitor another 6 servers, don't know the exact number of clients,

but my question is.

When is the memory used/allocated ? Will monitor memory usage and paging, but maybe you know

the facts.

-Does "Capture Events" and "Gather Reporting Data" have any impact on the memory usage ?

A gut fealing is that a bunch of Networkers out there run a NMC server with inadequate memory installed.

Hope we see you in Sweden again sometime soon Mikey,

Regards/Håkan

0 Kudos

Re: NMC - What drives you crazy ?

Well, I guess that we have to live the limitations upuntil re-arrangement of this config.


The thing i wait for the most is the ability to define the controlpath myself, or i.e. get support

for virtual controller targets. In our case HP-UX provide a virtual jb control path pointing to

two physical connections through our dual SAN infrastructure.Loosing the controler path will

make you go out of service after a while, even though it's quite doable to change it manually.

rd=  is the way Networker knows the target is a remote target.

<node>, well informative I think. Where to dig when you get problems...

Don't know what you are scripting, but in most cases you don't need to

specify the jukebox. nsrjb -u <volume> would select the proper jb, and

mminfo-pool usage might do the "other" selection.

Cheers,

Håkan

0 Kudos
Phil_1
1 Copper

Re: NMC - What drives you crazy ?

Hakan_Engman wrote:

The thing i wait for the most is the ability to define the controlpath myself, or i.e. get support

for virtual controller targets. In our case HP-UX provide a virtual jb control path pointing to

two physical connections through our dual SAN infrastructure.Loosing the controler path will

make you go out of service after a while, even though it's quite doable to change it manually.

Cheers,

Håkan


I understand, I think. When my first path went down, I just changed the path (scsidev@11.0.0 to scsidev@13.0.0 on Windows ), (kept the name) and it worked. It was on the remote jukebox as well. I would expect this to work via a virtual control path, however, I have not ventured into the virtual path or device.I've been warned off this by support, as well as warned of DPF (Data Path Failover). 'Not tested' is not what I want to hear from the company who boast of the ~'biggest testing environment on earth' - at least bigger than their compeditors.

Anyone else done this via Windows/ IBM CPF (Control Path Failover), or DPF.

Hakan_Engman wrote:

Don't know what you are scripting, but in most cases you don't need to

specify the jukebox. nsrjb -u <volume> would select the proper jb, and

mminfo-pool usage might do the "other" selection.

Cheers,

Håkan

We use "nsrjb -j <library> -u", to unload all drives prior to ejecting tapes. We could get around this by using a variable LL=<local library name> DR=<library a few miles away>, but then different people doing different scripts will use different variables presents additional problems.

Also, when using mminfo with -r location, <a huge name that screws up the field lengths>.

Phil

0 Kudos

Re: NMC - What drives you crazy ?

Phil_1 wrote:

Hakan_Engman wrote:

The thing i wait for the most is the ability to define the controlpath myself, or i.e. get support

for virtual controller targets. In our case HP-UX provide a virtual jb control path pointing to

two physical connections through our dual SAN infrastructure.Loosing the controler path will

make you go out of service after a while, even though it's quite doable to change it manually.

Cheers,

Håkan


I understand, I think. When my first path went down, I just changed the path (scsidev@11.0.0 to scsidev@13.0.0 on Windows ), (kept the name) and it worked. It was on the remote jukebox as well. I would expect this to work via a virtual control path, however, I have not ventured into the virtual path or device.I've been warned off this by support, as well as warned of DPF (Data Path Failover). 'Not tested' is not what I want to hear from the company who boast of the ~'biggest testing environment on earth' - at least bigger than their compeditors.

Anyone else done this via Windows/ IBM CPF (Control Path Failover), or DPF.

I do think that robot controller failover would be ok, as thera are no on-going sessions like on tape. Would never try path failover on physical tape, VTL drives should be immune to SCSI resets so it might be ok. Talking about IBM driver for tape and HP-UX driver, they are not completley loadbalancing as wanted.

The choosen path is selected upon start (boot ?) and the drive would continue to use that path until failiure. Resulting in usage of only one HBA in worst case. If the selection where session based, the OS would "loadbalance" over multiple HBA:s if available. But one have several drives, but only one contrlpath..

I guess that this is a limitation in the SJI driver, if it's still around in Networker.


We use "nsrjb -j <library> -u", to unload all drives prior to ejecting tapes. We could get around this by using a variable LL=<local library name> DR=<library a few miles away>, but then different people doing different scripts will use different variables presents additional problems.

Also, when using mminfo with -r location, <a huge name that screws up the field lengths>.

Phil

Environment variables for the libraries seems ok.

Howabout:

mminfo -q "<selection" -r "location(55),volume"  would set the same length all the time or,

mminfo -avq "<selection>" -r "location" -xc;   and use delimiter(;) when fetching the variables.

0 Kudos
SkipHanson1
1 Copper

Re: NMC - What drives you crazy ?

Phil,

  Hello. Apparently we support multi-column sorting today. Just keep in mind the order of the clicks.

If I click on the table header for age, then the table header for name you'll get.

Ben       7
Ben       9
Glen      6
Jack      5
Jack      8
Jack      9
Tom      6

Check it out and let me know if this helps ? We need to be more obvious about how this is done. I am

talking to eng about this. This in one of those "simple" things that could make a big difference.

Cheers,

Skip

0 Kudos
Sunman2
1 Copper

Re: NMC - What drives you crazy ?

Something I just noticed. I don't pay attention to it because it is rather usless. The Log tab rolls over too quickly. The Log tab is too small to be useful for us.

0 Kudos