I would always use the latest OS for the backup server itself (Windows 2012).
With respect to the client OS, you are stuck with the appropriate NW versions, even if they will not be supported any longer. Here is my recommendation:
NW Server Windows 2012 NW 8.2.3.#
NW Client Windows 2008 NW 8.2.3.#
NW Client Windows 2003 NW 8.2.3.#
NW Client Windows 2000 NW 7.4 .. 7.6 (NW support knows where to download them)
If you have good SQL admins, my personal opinion would be to export the SQL DBs rather than using the old NMSQL modules. This will take some disk space but it is more convenient for the db admins.
This is a small environment and I am not looking for any VBA configuration in this environment.
Hi Bingo,
I had the same configuration in my mind for SQL DB backup configuration with 2000 Win OS. but I am afraid if I could use 7.6 or lower version of networker for WIN2000 servers. due to EMC networker support..
I would always use the latest OS for the backup server itself (Windows 2012).
With respect to the client OS, you are stuck with the appropriate NW versions, even if they will not be supported any longer. Here is my recommendation:
NW Server Windows 2012 NW 8.2.3.#
NW Client Windows 2008 NW 8.2.3.#
NW Client Windows 2003 NW 8.2.3.#
NW Client Windows 2000 NW 7.4 .. 7.6 (NW support knows where to download them)
If you have good SQL admins, my personal opinion would be to export the SQL DBs rather than using the old NMSQL modules. This will take some disk space but it is more convenient for the db admins.
My experience with win2k is that it works with 7.5.x version, but not with 7.6.x. For older SQL version you would need to use either old NMSQL modules (like 3.1SP1) or use dumps. Bare in mind that I personally tested win2k version 7.5.x against 8.0.4.x server - can't say how this works (and if) with higher server releases.
Sometimes it is good to keep the old Compatibility Guides ;-)
Windows 2000 was supported until NW 7.4.x
EMC dropped W2000 support with NW 7.5.x
However - they dropped support. That does not necessarily mean that it will not work. It just has not been tested and approved any more. I remember I have successfully running NW 7.5.x - not sure about NW 7.6.x
As it is now beyond all supported NW version, just try it. My personal guess would be that all standard filesystem backups/restores will work. System restores could be problematic.
bingo.1
2.4K Posts
1
June 22nd, 2016 06:00
I would always use the latest OS for the backup server itself (Windows 2012).
With respect to the client OS, you are stuck with the appropriate NW versions, even if they will not be supported any longer. Here is my recommendation:
NW Server Windows 2012 NW 8.2.3.#
NW Client Windows 2008 NW 8.2.3.#
NW Client Windows 2003 NW 8.2.3.#
NW Client Windows 2000 NW 7.4 .. 7.6 (NW support knows where to download them)
If you have good SQL admins, my personal opinion would be to export the SQL DBs rather than using the old NMSQL modules. This will take some disk space but it is more convenient for the db admins.
bbeckers1
2 Intern
•
202 Posts
0
June 23rd, 2016 05:00
if it's VM's, then you'd also could go for NW8.2 VBA image backup, still also allowing for filelevel restores.
Image backup might also be more future proof as for instance NW8.2 server does not support NW7.6 clients. Nor does NW9:
NetWorker Version Interoperability Report
Nitesh_Turkar
32 Posts
0
June 24th, 2016 01:00
Hi ,
Thanks for your inputs,
This is a small environment and I am not looking for any VBA configuration in this environment.
Hi Bingo,
I had the same configuration in my mind for SQL DB backup configuration with 2000 Win OS. but I am afraid if I could use 7.6 or lower version of networker for WIN2000 servers. due to EMC networker support..
Vakil
1 Rookie
•
35 Posts
0
June 27th, 2016 15:00
Hi Nitesh,
Windows 2000 and Windows 2003 client backups have been dropped out of support.
ble1
4 Operator
•
14.3K Posts
0
June 29th, 2016 08:00
My experience with win2k is that it works with 7.5.x version, but not with 7.6.x. For older SQL version you would need to use either old NMSQL modules (like 3.1SP1) or use dumps. Bare in mind that I personally tested win2k version 7.5.x against 8.0.4.x server - can't say how this works (and if) with higher server releases.
bingo.1
2.4K Posts
0
June 29th, 2016 09:00
Sometimes it is good to keep the old Compatibility Guides ;-)
Windows 2000 was supported until NW 7.4.x
EMC dropped W2000 support with NW 7.5.x
However - they dropped support. That does not necessarily mean that it will not work. It just has not been tested and approved any more. I remember I have successfully running NW 7.5.x - not sure about NW 7.6.x
As it is now beyond all supported NW version, just try it. My personal guess would be that all standard filesystem backups/restores will work. System restores could be problematic.