Unsolved
This post is more than 5 years old
52 Posts
0
2368
August 3rd, 2011 14:00
NMMEDI architecture questions
I need to configure a NW for Meditech solution and am struggling to understand all the NetWorker requirements. My biggest area of confusion is around SnapImage vs. PowerSnap. My understanding was NMMEDI helped coordinate snapshots wih the CX, hence I would need PowerSnap. However, I'm looking at a quote configured by an EMC rep that included SnapImage instead of PowerSnap. My understanding of the differences between the two is SnapImage creates host-level file system snapshots, and PowerSnap works with array-based snapshots. Will one or the other (or both) for for a NMMEDI implementation?
Additionally, do I need any NMM modules?
Thanks,
Dan
ecarter11
2 Intern
•
177 Posts
1
August 3rd, 2011 14:00
Hi Dan,
Sounds like you have a good understanding of the technologies actually - you are correct - the NetWorker SnapImage Module creates host-level file system snapshots, and the NetWorker PowerSnap module works with array-based snapshots. Not sure why SnapImage appears on the quote - and frankly, PowerSnap itself as a standalone product need not be there either.
The NetWorker Module for MEDITECH contains the snapshot management capabilities built-in. This is similar to how NMM has built-in snapshot management (and to answer your question, for a MEDITECH installation, no, you do not need NMM). You do not need to add PowerSnap as a separate software/license in this case.
Is there some other server in the environment (something with high-density file system) for which SnapImage may be intended?
Slowrider5
52 Posts
0
August 4th, 2011 07:00
Eric,
Thanks so much, that helps a lot! I will do some checking into why SnapImage was quoted. My gut feeling is there was just some confusion on what's needed for NMMEDI. We all knew it leveraged snapshot technology so I think some assumptions were made we would need a SnapImage or PowerSnap license. That is great news all the functionality we need is included in the NMMEDI module.
So, just to recap, the basic requirements are:
1 - NetWorker Server
2 - Appropriate number of clients
3 - NMMEDI licenses for each Meditech server
4 - SnapView license for the Clariion.
5 - Auto-changer or disk backup capacity licenses
Lastly, could you confirm if NMMEDI can be added to a NW Fast Start kit? I'm working with a small hospital, and this NW solution will be for Meditech only. So, I think a Fast Start kit could cover the entire environment cost-effectively if I can add a NMMEDI module to it.
Thanks again!
Dan
ecarter11
2 Intern
•
177 Posts
0
August 4th, 2011 11:00
Hi Dan - your recipe there looks right to me. A couple of thoughts: If you're setting up a "proxy" a NMMEDI is needed there too. Also - since my head is mostly in NetWorker, the CX/SnapView requirements may need to be vetted w/ a core storage person. Yes, you need to license SnapView for sure, but be sure to check the other pieces (some are "software" but not necessarily licensed additionally from what I understand). This is listed in the install guide here on page 13-14: http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-010-603.pdf
Yes, NMMEDI can be added to a Fast Start environment.
Thanks for your work on this! Good to see.
-Eric