I have a server that is currently running NetBackup 184.108.40.206 on a Windows 2008 32 bit version. I need to upgrade the NetBackup application to the latest version on new hardware running Windows 2016 connected to a fibre channel connected Quantum Scalar i500 LTO 4 tape library. I am looking to understand what steps I need to take?
What I would suggest is the following (and due to the oldness of the versions and starting with a 32 bit OS, this will be painful).
Use version 8.0 as the interim NBU version as this is the first version that supported Windows 2016 as a NetBackup master/media server. To install/upgrade to version 8.0 you require a 64 bit OS. The final upgrade will be the simplest. Don't forget to review the upgrade guide for details on the NetBackup web service user and potential new database user - as the NetBackup database is converted from Sybase SQL Anywhere to PostgreSQL.
Make sure you review the upgrade guide for 8.0 - there are a couple of catalog migration tasks that are required as part of the upgrade and a NBDB rebuild. I'd suggest SORT, but I don't think it caters for such an old version anymore. If you also have MSDP in the environment, then there are some additional steps for converting this (first to 8.0, then again to 10.2).
Again review the upgrade guides to make sure you understand the requirements.
As for the tape library, once you have ocmpleted the upgrade use the wizard to add it back in.
Quite the task you've been gifted here. :)
If this is a production environment is there a budget available to engage Veritas Professional Services or another support resource to help with the migration/upgrade? Unless you're already a skilled NetBackup Administrator, I'm not sure this is the project to pick up for on the job learning.
If that's not possible, have you considered standing up a new NetBackup Domain and re-creating backup policies from old to new? I didn't read that there was an urgency to get this done so creating new backups and letting the old expire off might not be the worst option if you have time to do so.
@davidmoline is the expert here so take his advice where possible. I'm just tossing out other thoughts.
Regards and good luck to you.
As they have to have the same hostname as before I would not do this - for the versions you will be recovering (7.6.x & 8.0) there is no requirement for domain accounts to be available.
Once you get to 10.2 - there is a requirement for a web service user (and now a database user) which can either be domain or local - though making them local would add complications performing a recovery (as the recovered permissions for a local user may not restore correctly). However, this does not apply to you (so lucky).
Once you have completed the second recovery and have the system at 8.0, then I would reattach the new master to the domain.
And if I haven't said this before - test the process out first using an isolated environment (such as in VMware) to make sure you can get it up and running, before doing anything for real).
All I can suggest is to put out a call to this group to see if someone can help. I'm sure some diligent admin has kept all the old CD's etc. and may be able to provide it to you. The last version that supported a 32bit Windows OS was 220.127.116.11 from memory (so 7.7 wouldn't help). If you can get 7.6 (both 32 bit and 64 bit, then you could upgrade your current system to that and work from there).
I don't have access to anything that old.