I searched this forum for a comment on EOSL... I didnt find one, so thought I would at least kick off the discussion.As I remove the water from the tea leaves... I see... EOSL in our present and future... we know that thousands upon thousands of our customers are still running on Networker v7.x... I hope that you will review Networker 8.x and find the niche that inspires you to go forward.
I believe in the toys in our toy chest, I am not in sales, I am however an evangelist... /grin
Plan today, implement tomorrow, squash a couple bugs and coast on to easy street.
Please contact your local rep for any questions/assistance in your planning.
The compatible modules will have the same release number as the networker server build they are compatible with… Meaning NMM 280 marries up with 8.1.1.build280.
It is - under NetWorker support page (Support by Product -> NetWorker which will give you this where you have service life information including link to EOL file on bottom left side).
It would be more correct to say that module release like NMM will be released with any major patch release (SP) due to dependency of PowerSnap module (NSM now in NW) and release build will identify minimum version of core agent to work with that module. For example, 8.1SP1 tree got GAed during 8.1.1.2 and so did NMM 3.0SP1 and they both had build 280. That doesn't mean you can't use build 289 of NetWorker (8.1.1.3) with it of course. This does not apply to other modules (NMDA and NMSAP).
muser2
2 Intern
•
15 Posts
7817
0
Posted April 2nd, 2014 15:00
True and one of the cool things is…
Starting with networker 8.1.1.Build280
The compatible modules will have the same release number as the networker server build they are compatible with… Meaning NMM 280 marries up with 8.1.1.build280.
Much better…
Semper fidelis et paratus! /ALE