Home > Failed To > Failed To Initialize Ports Using Nsrexecd On

Failed To Initialize Ports Using Nsrexecd On

So, the next thing I would try is to use:nsrports -S 7939-7940and see if that gets it out of its own way. nsrports -s gonzo -S 7937-8937 will make the server use 100 ports for its service.)Remember to restart NW to make the changes active.So, if you have more than one client on Andrew Watkins says: March 8, 2011 at 4:02 am Had the same problem with Solaris 11 Express and the "nsradmin –p nsrexec" did not work for me, since it kept core Permissions Permission to re-post entire articles without consent is not granted. this contact form

It will rebuild all missing resources whenever the NW server will reconnect to each client.Then restart the NW daemons.I just verified that the NW server will now start as usual. Please type your message and try again. 1 2 Previous Next 18 Replies Latest reply: May 13, 2016 1:24 AM by JayJay9882 How to rename NetWorker server running UNIX JayJay9882 May Documentation Nomenclature Categories Architecture Aside Avamar Backup theory Basics Best Practice Cloud Data Domain Data loss Databases EMC Ethics General Technology General thoughts Licensing Linux NetWorker Policies Quibbles Recovery Scripting Security So if you need to backup your opensolaris-based system the author recommends to use networker client 7.4.5 over 7.5.x or 7.6.x. https://community.emc.com/thread/162605?tstart=0

Locate partners—or learn about becoming one.Find EMC PartnersEMC Business Partner ProgramBecome an EMC ResellerPartner CommunityPartner PortalRSA PartnersDell PartnerDirectContact UsPartner with EMC today.Live ChatContact SalesCall 1-866-438-3622Call 1-866-438-3622Company InformationKeep up with the news, However, in an emergency, when there's an upgrade about to be done and you need to walk someone through doing an incremental backup before the upgrade without giving them administrative access On the client do: · nsradmin –p nsrexec . Using version 7.5.x or 7.6.x causes nsrexecd to crash thus making remotely initiated saves impossible while locally initiated jobs run fine.

  • Close this window and log in.
  • nsrd and some other processes are started but immediately shutdown and only the nsrexecd keeps being up.
  • For instance, let's consider a save against the /root folder on a backup server where I've got a directive that's configured to skip everything in there.
  • GudjonssonSenior Technical Account ManagerExello Norge AS - Kronprinsensgate 1 - N.0251 Oslo - NORWAY+47 24 13 08 00 - [www.exello.com]Følg oss på Twitter: [twitter.com](Kopier alltid support < at > exello.no på
  • You should verify the backup which you configured after successful first backup with mminfo command.
  • Click here for more details.
  • But under NSR ist still claimed that the old networker name is the name of the backup server.I figured it would be easier!
  • I just searched the entire server for lsof....not there.

Is it something earlier than 7.6?There was a problem in the 7.4 series where to get it to use ports 7937-7940, you had to tellit to use ports 7939-7940 (because there I know very well what sudo is and what it does, but I would - at this point - prefer you do it as root without sudo (just to eliminate something Follow me on TwitterMy Tweets Tags7.6 ADV_FILE archive Backup Basics boost capacity change control client clone Cloning cloud data domain data protection deduplication Disaster Recovery disk backup documentation EMC Index jukebox So I tried to link the files accordingly.

august 2012 13:39To: NETWORKER < at > LISTSERV.TEMPLE.EDUSubject: [Networker] Trouble with saving through firewallUpdate:Since I changed the nsrport range, I'm not able to stop and start the networker service on the You will also see that client configuration saveset name starting with "NMCASA:/gst_on_NMC-Server-name/lgto_gst" with Backup Command attribute: savepsm (for a Windows Console server) or savepsm.sh(for a UNIX Console server). Re: How to rename NetWorker server running UNIX bingo May 10, 2016 12:32 PM (in response to JayJay9882) Obviously not even the client service could be started.This points to the fact Go Here You should first try below solution: Start or Restart below services: COM+ Event System COM+ System Application Distributed Transactions Coordinator Microsoft Software Shadow Copy Provider Volume Shadow Copy service Networker remote exec

The normal Networker “save” command cannot back up NMC database successfully if it is open during backup hence it is always better to use "Savepsm" command. So you should have ports 7937-7952 set on the server and the client, this can be done using the command "nsrports -S 7937-7952". Subscribe to updates Email Address* First Name Last Name * = required field powered by MailChimp! On first start nothing happened.

Turbocharged EMC NetWorker Full of useful information about a variety of topics, Turbocharged EMC NetWorker will allow you to become a NetWorker Power User. https://adsm.org/lists/html/Networker/2012-08/msg00050.html No...same problem.No 390XXX ports at all listed as per rpcinfo.Oh....and lsof is not on the server. Config-Files?Networker is really driving me nuts!What version of NetWorker are you running? Verify if you have replaced the old name in all resourcesI think this is almost it Do not forget for the clients that a new/changed servers file will only become effective

My Kindle eBook ("Stop, Collaborate and Listen") provides the necessary details for successfully aligning IT to the needs and purpose of the business. weblink So i did some tests with debugging turned on: [email protected]:/# nsrexecd -D9 lg_stat(): Calling stat64(). [....] [....] 0 1270119900 2 0 0 1 654 0 opensolaris nsrexecd 2 %s 1 0 How useful that "some" is though is of debate. Is it something earlier than 7.6?There was a problem in the 7.4 series where to get it to use ports 7937-7940, you had to tellit to use ports 7939-7940 (because there

Rename the server and adjust the DNS name5. When starting a save job (either locally or remotely) nsrexecd dies: 0 1270119985 2 0 0 2 654 0 opensolaris nsrexecd 2 %s 1 0 33 Found 390113 program on port Re: How to rename NetWorker server running UNIX Hrvoje Crvelin May 10, 2016 5:56 AM (in response to JayJay9882) You can't change it as it is ro attribute. navigate here Re: Networker won't start up Hrvoje Crvelin Sep 18, 2012 11:32 AM (in response to DennisP) 1.

Re: How to rename NetWorker server running UNIX Hrvoje Crvelin May 10, 2016 3:25 AM (in response to JayJay9882) Server as client or server as backup server? Archives Archives Select Month January 2017 (1) December 2016 (1) November 2016 (4) October 2016 (1) September 2016 (2) August 2016 (1) July 2016 (2) June 2016 (2) May 2016 (2) Conclusion Although officially unsupported by EMC using networker client 7.4.5 works fine on Opensolaris.

I'm running v7.5.2.I used the command "NSRPORTS -S 7937-7940 -C 7941-7960" on the client then restarted the NSREXECD service.

Report Abuse Like Show 0 Likes (0) 8. I believe, if I remember correctly, that was official procedure. Edit the servers file (done that for all clients already)5. If you see any 390XXX numbers, removed them with rpcinfo -d 390XXX 4.

Report Abuse Like Show 0 Likes (0) 7. So i did some tests with debugging turned on: [email protected]:/# nsrexecd -D9 lg_stat(): Calling stat64(). [....] [....] 0 1270119900 2 0 0 1 654 0 opensolaris nsrexecd 2 %s 1 0 Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action. his comment is here Nsrexecd (NetWorker Remote Exec Service) service stared automaticaly but "EMC GSTService" will have to be started separately.

That was even stranger because i just restarted the process prior starting the backup. Stop NetWorker services and do VMware snapshot2. where you rename backup server to temporary name first, under that name you do client name of old server to new one and finally you rename it from temporary name to Report Abuse Like Show 0 Likes (0) 6.

You may think that as of 7.5 onwards, where the level is expressly ignored for manual backups, that this isn't possible: [[email protected] ~]# save -l incr -b Default /tmp Client initiated You can not post a blank message. Re: Networker won't start up DennisP Sep 18, 2012 12:23 PM (in response to DennisP) root=> rpcinfo -p localhost program vers proto port service 100000 4 tcp 111 rpcbind 100000