Is anyone running their NMC server successfully in a virtual machine?
Mine is recently attempted to migrate from my backup server to a
dedicated virtual machine using the procedures in the admin guide,
where it ran for four hours successfully, and then errored with:

E. 11/15 10:21:06. *** ERROR *** Assertion failed: 100701 (9.0.2.3308)
E. 11/15 10:21:06. Unable to modify indexes for a row referenced in rollback log

I started up the original instance on the backup server where it ran
for a few hours without issue, did a fresh backup, restored to the new
dedicated NMC host, and same error.

So I tried just copying the lgto_gstdb/ files to the NMC host, it
started just fine, ran for a few hours, different corruption issue:

E. 11/16 01:16:06. *** ERROR *** Assertion failed: 102300 (9.0.2.3308)
E. 11/16 07:42:43. File associated with given page id is invalid or not open

As of now I assume that the original database files are good, because
they continue to run and back up with save command savepsm
successfully.  Support recommends I run with a fresh database to 1)
see what happens and also 2) there are no recovery tools other than
recoverpsm from a known-good backup, and if that's recovering with
corruption than my assumption is wrong.

To run a with a fresh database, is there any harm in running two NMC
instances in parallel? It would be less than ideal to lose another 24
hours of backup statistics...

Thanks!
-Eugene

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER