Search results for query: *

Thanks, it was like looking for a needle in a haystack.

And then where? I've looked in the legato, pub, outgoing and outgoing2 directories.

Does anybody know where to get it? I looked on the emc website, but only found Jumbo release 11 for 7.2.2. The date on 7.3.2 is Septmeber, which is the original release.

It hasn't. Since we were having so many problems they allowed us to ftp it. They said build 11 should be released this week.

We just installed build 9 a few days ago. It appears that our server was running out of resources. Yesterday we upgraded the CPU and memory and things ran well last night.

BTW, we disabled GSS authentication and nsr is still getting locked up. Only now there are no errors in the daemon.log, everything just stops working. We applied the latest Jumbo patch with no relief.

Yes, it's been awful. There seems to be no end in sight either. Novelli, what do you mean by "redo"?

I had the same error occur a few days ago. It turned out to be a firewall issue, we didn't have the correct ports opened.

Hi Novelli, Yes we have a firewall, they are actually in different locations. We have the following ports opened on the firewall: Service ports: 7937-9936 Connection ports: 10001-30000 We never had the error before the upgrade. The firewall rules were not changed after the upgrade. Jodi

Legato support isn't too much better in my mind, nor is their new website. They all stink. The latest problem is a repeat of a problem that occurred two weeks ago. The backups were running on the server and storage node. We received the following errors in the daemon.log: 10/27/06 01:05:51...

It's running. It works when we restore 1 or 2 versions of the file. If we try more than two versions, we get the error. It is very tedious when the user needs to restore 20 versions of a file and they can only do two at a time. I restarted the daemons on the client and server and it still...

We recently upgraded from version 7.1.1 to version 7.3.2. The latest issue we have is with recovers. When attemtping to recover more than two versions of the same file (to rebuild a database) we get the following error: Requesting 4 file(s), this may take a while... recover: RPC error: RPC...

Not anymore from Legato, good point. Do you ever sleep 605? I noticed a post you made in the early morning hours and here you are again! I sure appreciate your assistance, as I'm sure other members do as well. Keep up the good works.

I guess I should have said you can't easily go back. My statement comes from the release notes for 7.3.2: When updating to NetWorker release 7.2 or later format, there is no way to revert to a previous release of the NetWorker software. It is a one-way conversion.

We upgraded on October 3 from 7.1.1 to 7.3.2 and have had a lot of problems. We run Solaris on our server and storage node. I have 4 cases open with Legato and none have been solved yet. There are errors in the log that I cannot find anywhere on their site, or in the error messages guide for...

I think I found the explanation I was looking for. Please correct me if I'm wrong. We have our server parallelism set to 128, the maximum for our setup. If I want to run both groups at the same time, I should set the group parallelism to 64 for each? It was set to 0 before the upgrade and...

Can anyone explain the savegrp parallelism function? Ours is set to 0 for each group. I can't seem to find a solid explanation anywhere. Thanks.

The server parallelism is set to 128, target sessions on each device is set to 6 (there are 12 devices total = 72 ) the client parallelism varies by client. The savegroup parallelsim is 0 for each savegroup. As far as I can tell, that should work. I'm nearly positive the values are the same...

Thank you all, unfortunately setting the connection ports on the storage node did not fix the problem. Back to the drawing board!

I should elaborate a little. The server had the service ports set to 7937-9936 and the connection ports set to 10001-30000. We did not do anything to change that after the upgrade. The storage node and some clients had the connection ports set to 0-0. EMC support tells me this should work...