my friend, my only very good advise for you is stay away from version 5. don't waste your time. you should have upgraded it to version 6.1.1. even this latest version has some bugs. legato is working on "RFE" as the call it which means bugs.
hope this helps...
check this:
in your client resource, what did you put in the save set field? if it's "All". it should save the index in the same pool as where your data is stored.
check also if the group and pool that this client is a member does not have any save set defined in the "save...
jdale2000: i'm interested on the latest nsrmmd fix. can you provide the ff:
build #, build date and build info:
just run what /nsr/nsrmmd.
Thanks.
For packageman: in NW6, legato has changed the index algorithm. the reason why your volumes are not converted to recyclable is that there is a...
there's something wrong with your DNS. this is a name resolution problem.
4 steps you need to do:
1. add the client's IP and hostname in the NW server host file.
2. make sure to define also the fully-qualified hostname of the client in the client definition "aliases" field. so...
upgrade to NW611 and apply latest fix for nsrd. works fine. i agree with you that legato support is sometimes not a help but it's always to have a support contract. renew your contract at least you have someone to blame to.
the best you could do is team the 2 NICs. you have to request from your network team to configure the 2 port used by the 2 NICS in etherchannel. this will give you redundancy, fault-tolerance, load-balancing capability. with this, you only have to use single IP since the teaming will create you...
since you dedicate 1 card for backup, then set up an alias for the 1st card IP address. then in all clients, change the server name listed in \Program Files\nsr\res\servers(windows), /nsr/res(unix) of all clients to the alias name. This will direct all clients to use the card dedicated for backups.
We are in the process of implementing ORMIS(Operating Room Management Information System) by iPATH. I would like to know if someone is running this application is Silver Thin SP node performance. If hardware specs is provided, the better.
Thanks.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.