Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Recovery of Primary SS in release 7.5

Status
Not open for further replies.

leekawai

Technical User
Dec 2, 2010
56
HK
I have two SS.Secondary SS is backup of Security server. The Primary SS has data corruption. The PD does not work. Also I can't login to EM in PSS. The /var of PSS is full. Can't do any sysbackup. Only Secondary SS can do the backup. Is the possible to recover the Primary SS by the backup of Secondary ?

Thx in advance
 
can you deploy EM for the system into one of your other servers (UCM, etc) and then try to at least backup the PD.

Would say then if it is just a Sig Server, you can reload it put the base parameters in manually during install, add the Applications again in deployment manager, patch, then log into EM open node and sync and restart apps. Then if you were able to backup the PD stick it back on.
 
I think all you are going to be able to do is reload the Primary from scratch. Then rejoin all UCM Elements to it. Then you will have to reload the backup. There is really nothing in the backup that is going to help you anyway.
 
I think I had the same issue last week.

I logged in to the Primary SS using SSH - I got in OK.

I did an isetShow and found that TPS was still working (Half the IP sets were registered on it).

The disTPS command migrated all idle sets to the Secondary SS.

I kept doing isetShow until all the active calls completed.

I reset the Primary SS by holding the RST button for >5 secs.
(previously a software reset had failed)

The Primary SS came back up, PD works, I could get in to EM, and half the IP sets migrated back.

Good luck.
 
The issue you are going to have is the finger print that is generated when you originally configure the Primary will never be able to be recreated. And you cant promote a backup to a primary. If the you have confirmed you have corruption and /var is full in the primary your only way out is to reload the linux, base patch it, do the security config, deploy it and then service pack it. Then rejoin all your elements to it. Then you will have to reload the backup to get the new finger print. Been down this road a few times and this procedure is the only thing that fixed it. However, you may be able to get your support into it and delete some of the files out of /var long enough for you to get a PD backup. Other than that, bite the bullet and reload it. Doesn't really take that long. No baseball on tonight so go for it, GO ROYALS
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top