RDSM STS Corba : cannot connect on socket

YAHOO!!!

Re-Imaged the one pair of appliances yesterday then had a webex with Symantec last night through to this morning - finally finished at 1.35am!

The good news is that it looks like it has been sorted at last but will be able to confirm tomorrow as it goes live tonight.

The pointers for others that experience a similar issue are as follows:

If it happens (and there does not seem to be any known issues why it should happen - log entries seemed pretty much unknown to Support even at full level 6 for Debug and Diagnostics) and very little in them, then there is most likely an issue with the appliances - re-imaging the replication target appliances (the ones that will not add in to the replication tab or the Storage Servers properties) seems to do the trick - this is a re-image from the provided USB, not a soft reset ... however, also bear in mind the following ...

1. Any open NetBackup Consoles seem to cache the "wrong / failing" information so close them down and re-open them before trying again

2. NetBackup processes also seem to cache things and can prevent AIR working - or at least the Import phase - once everything has been configured ready for the backup and AIR duplication / Import it is handy to do a service restart on the NetBackup systems before actually running anything. We couldnt do that last night due to backups running but did get away with a nbrmms re-start on the Master which brought the Import to life.

Hope this helps others - will report back tomorrow with the results of tonights backups / AIR

A big thanks to Brian Benson at NBU Global ESS (Symantec Support) for his help and patience last night