Migrate to new Server Hardware

jmoyer

Hi folks!

I have been doing some searches here, but I haven't found any info yet on moving from one server to another and what would be require to do this.

Can anyone offer a little guidance on things I should look out for when moving my Navision server to new hardware? I have it currently running on a Win2k server that is being sent back on lease. I will have a new Windows 2003 server ready to go in the near future.

Thanks in advance!

themave

My laymen's end user approach would be to:

1. setup new server with same name IP and directory structure for Navision Data

2. Install Navision server as normal on new machine, but do not connecting to domain yet, so you will have the same server name, ports ect.

3. Use Hot copy to create backup on different server in the network. disconnect existing server from network

4. Connect new server to network and join domain.

5. Copy hotcopy created database files to new server, same directories.

6. Start Navision Server, and be up and running.

Off coarse I would do this on a weekend, before hand to make sure it worked, before I would do it on the real database.

If you keep all the server names and ip address the same, all the remote users will connect without having to make any changes.

Savatage

Just curious what size DB are we talking about & is it split into multiple DB's & are you using Native or SQL.

thanks.

bbrown

This is a two phase task:

PHASE I (Preparing for cut-over)

Phase 1 should be completed prior to your scheduled cut-over. The purpose of this phase is to configure and test your new Navision server.

1. Build hardware and install new server in your domain. Use new server name & ip address. (Using the same name or ip address would prevent you from conencting the new server to your network). Configure your drives to achieve the best performance from the new hardware. It does not need to look like the old server.

2. Install a Navision client and create an empty database large enough to hold the existing production database (plus free space). Split the new database over multiple drives as appropriate for the new server. For best performance, physical drives that hold Navision database files should be dedicated to those files and not contain any other files.

3. Install the Navision database server and seelct the database created in step 2 during installation. Also select your license.

4. Get a complete Navision backup of your production database. Since this is only for testing, it does not need to be current. A backup form the previous night will do.

5. Restore to the new server.

6. Test the new server. (you may enlist the assistance of select end-users).

7. Schedule the cut-over and prepare a memo to your users. Inform them of the pending change and any actions required by the to connect to the new server. Use Navision client startup properties if desired.

Between Phases:

Limit changes such as development, new users, permissions. Any changes made to production should be made to the new server also. One approach is to limit the time between project phases.

PHASE II (cut-over)

Phase II needs to be completed during downtime. Phase I should give you an idea of time involved.

1. Get all users off Navision and stop the Navision service. Set the Navison service's startup to Manual. This is to prevent the service form restarting on server reboot.

2. Make a Navision backup of the production companies. Company data only.

3. Restore the backup to the new server. You will need to delete the existing companies first.

4. Assist your user as needed.

These steps are the same regardless of database platform (Native/SQL). SQL would have the additional step of creating SQL user accounts. Using the Navision backup & restore method will reindex and defrag your data. Possibely improving performance. It will also allow the new server to store the data in the best way for its drive structure. Simply copying the old database files will not accomplish this. You have just spend money on a new server, give it the chance to deliver.

NOTE: Remove your database and Navision license from the old server before sending it back to the leasing company.

Hope this is helpful.