I found article 1238 "How Do I Restore My Public Event Server?" to be very helpful. However, running system 5.3.2 as opposed to the 4.x of the article needed two little tweaks I believe. Does this sound correct?
1. Stage 2 #3 be sure to click the box to make the new public event server "running" status. The close the Network Manager application. 2. Stage 5 #2 now upon completing the import process and selecting the new public event server one can choose the bonjour server as opposed to entering an ip address, port and name.
I'm think this will work, using the bonjour server functionality. Before I was typing in the address and port, but whenever i turned my server machine off, the next attempt to use the public event server would trip an error "all data would be lost" if I went online because it would appear my ip address changed. My assumption is that the bonjour server functionality can handle reboots, eh?
Just a little bump, curious if anyone thinks my logic is sound with regards to the functionality of the "bonjour" public event server, will it still be found by NUDC after a reboot, again, the other method of enabling the public event server via name and ip address, seemed to lend itself to needing a restore ... I really don't want to have to restore everytime my server goes down.
I actually recommend against using Bonjour for connecting to the servers. Bonjour is great for initial connection, but it's not always able to pick up a server if you change machines or IPs. When you set up manually using an address and port, you can always go back and edit that information to repoint the client in the right direction, while a client that was set up using Bonjour can't be forced to find a server.
Each server has a unique identifier, so the error message you get about the server appears to be different and all data will be lost, is based on that unique identifier. It should recognize a restored server from backup, or a moved server database as the original, but will not recognize a rebuilt server or one that was otherwise newly created.
_________________________ Sean Boiarski Product Manager, Now Software
Hi Sean, Bonjour has been a source of frustration for me on the basis you describe.
I thought Bonjour was 'zero config' networking!
On that assumption (and knowing what assumption is the mother of...) I've always expected NUDC to find servers regardless of IP address etc. (I use a Macbook connecting to one server on the MacBook, another at on my wife's Powerbook at home and my secretary connects to the server on the MacBook when I'm at work. Bizarrely, she can connect to the server but NUDC on my own machine cannot because I'm at a different IP address. NOT zero config)
I actually recommend against using Bonjour for connecting to the servers. Bonjour is great for initial connection, but it's not always able to pick up a server if you change machines or IPs. When you set up manually using an address and port, you can always go back and edit that information to repoint the client in the right direction, while a client that was set up using Bonjour can't be forced to find a server.
Each server has a unique identifier, so the error message you get about the server appears to be different and all data will be lost, is based on that unique identifier. It should recognize a restored server from backup, or a moved server database as the original, but will not recognize a rebuilt server or one that was otherwise newly created.
Thanks Sean, so I'm a little stuck then. Twice before using the bonjour setting I did have flawless connectivity until a reboot occured I checked the ip address upon getting the error "the server appears to be different and all date will be lost is you connect", but the address was the same as the public event server and port was unique to the PES too. So I don't get what is causing the error or what to do differently. I should be able to reboot and find the server after a reboot right? even the host machine couldn't find the server.
Okay, I went back and re-read your initial post. You rebuilt an event server, correct? And now your trying to connect clients that were connected to the original server to this new server?
Unfortunately, that's not going to work. When you rebuilt the server, you created a new server with a new server ID... the clients will not synchronize with this new server and treat it like the old, because it's not the same server. Is there a reason you can't connect to the new server and unsubscribe from the old? Was there data that was not yet sent to the server from the clients that will be lost?
_________________________ Sean Boiarski Product Manager, Now Software
#504493 - 01/14/0802:26 AMRe: Restoring Public Event Server using 5.3.2
[Re: HhCreditCard]
Kempy
Registered: 04/16/07
Posts: 101
Loc: Melbourne Australia
WE have a similar problem on 5.3.2 - my G5 loses the server IP address, and bonjour, once an initial install is done will not work again so we install a new contact database and input the IP address etc manually. Rebooting the server does not help. Rebooting slave and master does not help. Disk utility does not help. It does get a little boorish having to install a new dat base, synch, select categories, sets, colours etc all the time.