VCRM reindex

[Typhoon87]

Is there a way to have VCRM avoid a reindex every time the host OS needs to be reabooted? Its annoying because a reboot of the OS suddenly means 3 hours of reindexing and the inabilty to use the VCRM on client machines.

I am running the latest 7.2.2 version.

[David Orwig]

Are you sure it's the VCR reindexing? I had issues similar and it wound up being a load of unprocessed traps in the "c:\Program files\HP\Systems Insight Manager\traps directory". 1.3 million to be specific

[Typhoon87]

I am not running SIM and I also see the reindex notes in the log file for VCRM.

I see in the log file

Initializing Version Control Repository Manager service start.

Catalog validation started

Catalog validation completed.

and the time stamps between the start and stop are about 4 -5 hours. Why does it need to reindex every time the host OS is restarted?

[shocko]

I have the same problem. In my case though, it appears to be that although I have the repository manger set to only download software for Windows 2008/2008 r2/2003 it's also downloading all available software for *nix/windows 7 etc. which is leading to a huge amount of repository bloat and causes the catalogue validation to take hours. I'm investigating this now. I may open a support case and I'll post back if I get anything useful.

[Typhoon87]

I also see the same issue that you are seeing the repository has quite a few scexe linux updates even though I do not have linux chosen as an OS.

I will say in 7.2 they did improve the speed of initizlaion by a bit but it still needs alot of work

Are you also using VCRM 7.2.2?.

Im a bit weary of openeing suppor cases with HP for this type of thing. I once opened a case about the VCRA and it took weeks to hear back try reinstalling the software but in a specific order. which did not fix my issue.

[shocko]

I've logged a call in relation to this with support and I'm going to insist on some type of resolution or at least help me to understand the product better. I'll post back ASAP.

[Typhoon87]

Any chance of an update on this?

[Typhoon87]

Just asking again if there is any update on your case.

They have relaeased V 7.3.0 has been released. I have upgraded and there was an imediate reindex after the installation finshed. That took aboiut 26 hours to complete.

I have just rebooted the server and they chagned the text used on the items after a reboot to say A catalog item has been modified XXXXXXXX   where the X's are the softpaq id.

its been running since about 11 this morning and is still going right now.

[shocko]

Hi guys, meant ot post back. Here's what HP said:

"Because the VCRM downloads and extracts the SPP for Proliant, this will mean you will always have components for windows/Linux operating systems in the repository. There is no way around this. So, even if you have only selected some windows systems to dowload items for, once the SPP is extracted it will bring in the Linux components therein. Also, the re-index will always take a long time due to the size of the repository once SPP etc are extracted"

Great design eh?! :(

[masirider]

Yep... that was the same responce that I received from HP.

I hope the design improves in the future.

[Typhoon87]

Agreed a terrible design.

Why dont they store it in kind of sql comapitable db style even if they use like a default frontbase install or seomthing to keep track of everything in the database. Also this still does not explain why it needs to reindex at every boot.

[shocko]

I know~! Its crazy.

[waaronb]

My guess is that it's because when VCRM is running, it monitors your repository directory and will pick up any files you manually copy in there.

If the machine reboots, it doesn't know if anything got plopped into the repository while it was offline, so it decides that rescanning the whole dang directory makes sense.

Now, we all know that's a poor way of doing it.  Why not scan for anything with a recent date-created, or keep track of when you last scanned it and only do the ones with a date-modified since whenever that way.

Because the way it is now, it extracts the contents of each EXE to get the manifest or whatever out of it, and that right there is what takes a majority of the time, I'm pretty sure.  If it were just a matter of scanning the directory and ONLY doing that for new or modified files, well heck, it'd be done in a few minutes, tops.

Yeah, it's a pain, and it's made me setup my VCRM to NOT get auto updates, and I only copy in the cp*.exe files that I actually care about, but it's a pain for me because I have to scan the HP download pages and prowl around for updated files to manually copy to the repository.  But by keeping the files in there to a minimum, catalog validation "only" takes 30 minutes or so on reboot.