- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- New to Version Control Repository and managed to “...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2013 05:56 AM
11-28-2013 05:56 AM
New to Version Control Repository and managed to “break it” after upgrade..
Hi,
I have been given the task of looking after HP SIM and all it entails and unfortunately our current environment had not been documented in the least. I was told to update our HP SIM setup from 7.1 to 7.2 so I built a test environment and this worked fine and for each option seemed at least to take the settings from the previous version of the component. However after all going well the upgrade bombed out at the VCRM update saying the service couldn’t be stopped correctly and installation had failed. I rebooted and did the VCRM part of the upgrade on its own.
This “seemed” to go OK but it didn’t seem to have stored the previous location of the repository (So I pointed to it) and it had not kept the versions of OS and schedule settings so I took a guess at what we would need on this. This then finished OK.
Today I checked a couple of remote servers that previously worked to list what new drivers are required and they are not showing up what is available and it says the VCRM is “busy”
When I look in my repository all the old files seem to be there (well it’s like 30GB but don’t know what it should be) but 12 hours on I am getting a stream of “MNF” files been written? Is it possible the repository is building itself from scratch? I am reading through the documentation but wondering if I should wait for these to stop first? Even though they are tiny these are currently writing at once a minute.
Any help appreciated!..
- Tags:
- upgrade