Welcome to this Ask the Expert discussion.
During this event we'll go over the best ways to install, manage and configure various Solution Pack into ViPR SRM, and steps to discover the various products/devices/objects into SRM for monitoring and reporting purpose.
We'd like to invite you to check out a quick demo of EMC's ViPR SRM. The video cover a quick overview of the various report packs, Capacity Calculator, Capacity Planner, Topological view and ViPR Dashboard.
Our support subject matter experts are available during the period of this event to provide you detailed information and support on any of your queries.
Meet Your Experts:
Techincal Support II - EMC, ViPR SRM
Shrinjoy has more than 5 years of experience as Technical Consultant, Support and System Administration Roles. He also has rich experience in Production support for Windows and Linux Servers, and EMC, HP and Netapp Storage arrays. Moreover, Shrinjoy has strong working knowledge in VMware and is VCP Certified, as well as certified in EMC ViPR SRM and EMC Vplex, along with ITIL v3 Foundation.
Technical Support II - EMC CS Remote
Pritam has a total of over 5 yeras of IT Experience, 2 of which working at EMC. He's a member of the EMC India ASD (Advanced Software Division) and Storage Resource Management Team. He is experienced in software development, product deployment, Software/Product Support. Pritam is VXN Certified and SRM Certified Professional.
This discussion takes place from Dec. 14th - 25th. Get ready by bookmarking this page or signing up for e-mail notifications.
Share this event on Twitter or LinkedIn:
>> Ask the Expert: Best Practice for ViPR SRM Solution Pack installation and configuration http://bit.ly/1LRgKxv #EMCATE <<
Welcome all, this Ask the Expert session is now open for questions. For the next couple of weeks our Subject Matter Experts will be around to reply to your questions, comments or inquiries about our topic. Let’s make this conversation useful, respectful and entertaining for all. Cheers!
Please provide a consolidated docs for ViPR SRM, with Architecture and Admin details.
I would like to know in the case where I want to modify the collection that is installed by the SP what is your best procedure to avoid this from being blown away during upgrade. Currently I take away write permissions from apg, but this causes different problems. The other way is to manually track every file change I have done then after an upgrade merge my changes back together.
Also, please do not consolidate all of the doco, I think the doco is structured perfectly as it is.
Thank you for your query. All related documents for ViPR SRM, can be found from the link provided below.
Please let me know if you need any other document from us.
Thanks and Regards,
Thank you for your question.
The modifications/customization in the files, after the installation of the SP, are usually removed after an upgrade. That is because the upgrade packages over-writes the same set of files, with the recommended settings provided with the upgrade packages.
Almost all the files from the previous versions are replaced during patching, with the new upgrade packages - so changes to conf files will be lost.
My suggestions are as below:
If the certain file was edited to eliminate or fix some error with SRM in your environment, check,
1. The latest Release Notes for any update relevant to the problem.
2. Wait and see if the issue re-occurs.
3. Make the modifications manually again and check if it fixes the problem again.
If the certain file was modified or edited to customize some report, request you to take a back-up of that file and save it in a secured place. Also kindly note the location of the file too.
Once the upgrade completes successfully, redirect to the same location and replace the original file with the previously saved file.
Hope this answers your query. Please let us know if you have any further question on this.
Thanks and Regards,
The collection is part of a SolutionPack, and the SolutionPacks are automatically versioned (starting with 3.5). You can switch between versions in the Admin Console:
You probably want to use the newest version, since it will have bug fixes, new reports, etc. But you can export your changes from the previous version and import them into the new version.