Symposium 5.0 upgrade

[mt6322]

We are in the middle of an upgrade from 4.0 to 5.0. Since the database restore did not work from the tape, we back-up the database to a remote directory on the network, then restore it from the network to the Windows 2003 (symposium 5.0) server. But during restore, it starts the SQL backup server service but immediately the operation fails.

Any advise will be greatly appreciated. Thank you.

 

[tekice]

reboot server and then try restore again ,i had this and reboot fixed prob

 

[brewerdude]

1. Make sure that you didn't change the server name after you installed sybase and before you ran the restore. The Sybase service will always fail if this is the case.

2. When doing the network restore, restore the files directly to the new server over the CLAN. Just create a folder on the c:\ drive of the new server, share it and do the restore to it. Since you'll have to have both systems on your network at the same time, this is how you'll have to do it:

a. Create a folder on your new server and share it.
b. Give full permissions to your backup account to this folder
c. Give the new server a new name and IP addy. Rebbot.
d. Do your network restore to the new server
e. After the restore is complete, take your old server off the CLAN. Rename the new server with the same name as the old server. Also change the IP addy to the one the old server was using. Reboot.
f. Install Symposium.



Good luck!

 

[mt6322]

Brewerdude - thanks for your advise. I would like to clarify if the instructions you have provided apply to what we set-up as described below.

Throughout the upgrade, the old Sympo 4.0 server (NT server) remained on-line with the current computer name and IP address. We assigned a new IP address and computer name to the new server, copied the new PEPs and the platform recover disk from the old server to drive D:\oldprd. The Sympsoium 5.0 server software was installed successfully but failed to restore the database from the remote directory due to the Sybase service problem.

 

[brewerdude]

We had the same Sybase server issues. You can have a different server name between the new and old systems, but to make absolutely certain that you are not going to have issues it's best to have the new server have the same name as the old server. If you have a large database Symposium will be a difficult child. We did the install about 5 times before we got it to go successfully.

Plus the other advantage of having the same name and ip addy on the new server - you don't have to have everyone create a new SMI workbench entry on their client.

 

[mt6322]

Thanks so much for your help.

 

[brewerdude]

Good luck!