Upgrade from NW 6.0 to 7.1 including OS Update

[Malachias]

Hi all,

I want to upgrade my actual WinNT40 Server with Networker 6.0 to Win2000 with Networker 7.1

The new installation should be on the same machine.
Can somebody provide me with an optimal "to do" sequence.

Are there special problems or facts I have to be aware of?

Thx in advance
Malachias

 

[fazil1]

Hello,
First do a full backup and create bootstrap and keep this tape handy. Copy NSR directory if you might corrept it.
Secound get all your licenceses information uptodate.
Print it out.
Update OS to Windows 2k.
Apply windows Service packs and fixes.
Update networker to v-7..
If there are any issues with hardware and win2k,
reformat and install win2k cleanly.
configure it with Networker 6
do DR and restore Networker 6 from earlier backups and Bootstarps.
Once your installation is funtional, upgrade to V-7

 

[ario]

Hi,

I upgrade my backup server last week
from Windows NT 40 to Windows 2000
but still using Networker 6.2
What I did with my backup server are:

backup all data to other machine (including nsr folder)
then format existing machine and install with windows 2000
(clean install) then install networker 6.2, configure jukebox, stop services, copy res, index and mm folders to their orginal location, then restart services
this week, I planned to upgrade NW6.2 to NW7.0

I don't think upgrade WinNT40 to Win2K is safe enough

thanks

Ario

 

[Malachias]

Thx for your assistance.

As I understand, I have to copy my nsr-directory to my new installation.
Does this mean, that I can access my existing index-files again, without any special activities.

My main topic is the transfer of the existing index into the new installation.

Best regards and thx in advance.
Malachias

 

[LGTObug]

When you make an upgrade from Networker 6.0.x to 7.0. You first need to upgrade to an 6.1.x Version and after this to Version 7.x. Cause of this is that each Version has another Res-Directory structure.

First make a Full-Backup of the server. Save your Bootstrap.
After this do the OS-Upgrade to W2K, install Networker 6.1.3 (stablest Version in 6.1.x series) do an Disaster-Recovery with the latest Bootstrap like mentioned in the disaster-recovery guide.

If you have done this. Simply overwrite the old version with the new Version 7.x. There's no need to uninstall the old Networker-Version cause the res, index and media-database automatically get merged to the new structure.

An upgrade takes about 10 Minutes

The only thing i would do before is copying the res-file to another directory in the case that there are troubles with the upgrade.

hope this helps

 

[Malachias]

@ LGTObug,

OK, but I want to upgrade to new Version 7.1 and not to 7.0

I heard, that in this case it not possible to update an before installed 6.x version. Is this really correct?

Regards,
Malachias

 

[LGTObug]

It is possible but you need an Update/7 Enabler code. without you won't be able to do so. 7.0 or 7.1 no real difference.
Who told you this? overwriting the old Networker with the new version is the best method for an upgrade. I would say so.

 

[Malachias]

@ LGTObug,

ok.
I will try it the way,you told me.
Appointment is 17.11.03. So I still have some time to create a working concept. ;o)

Does the copy of the old filestructure also mean, that my before user backup setting are all taken into the new version (backup settings like cyles, backuptimes, etc)?

 

[TDun]

I would strongly recommend doing this in 2 stages.
O/S and then Networker
So,
1: Take a full backup
2: Upgrade O/S and patch it. Reload and test
3: take a full backup
4: Upgrade Networker (you will need the update license).

If 4: goes wrong, remove Networker, install a clean 6.1.3 and do an mmrecov (from 3's backup), then move over (while services down) the res structure.
For 2:, recover from 1's backup.

 

[LGTObug]

@malachias

yes, so it is. I would say that's fine. You loos no resource-configuration at this upgrade. All settings (cycles, schedules, pools, etc....) will be available.

Good luck,

 

[Malachias]

Installation looks good.
I just have some problems with my autochanger.
But I guess I can fix these.
I'll keep you informed...