Backup Central

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


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

On 11/16/11 9:03 AM, Eugene Vilensky wrote:
Is anyone running their NMC server successfully in a virtual machine?

I am. I am running 7.6.2.5's NMC on a 32-bit RHEL5 VMware guest.

I migrated from a Solaris system by wiping out the database and starting from scratch.

I use Theirry's NetWorkerReporter for my statistics gathering...

--
Frank Swasey | http://www.uvm.edu/~fcs
Sr Systems Administrator | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
"I am not young enough to know everything." - Oscar Wilde (1854-1900)


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Amen to Theirry's Networker Reporter. It is the best piece of software to
use with Legato Networker. And best of all it is free of charge.


On 11/16/11 10:13 AM, "Francis Swasey" <Frank.Swasey < at > uvm.edu> wrote:

On 11/16/11 9:03 AM, Eugene Vilensky wrote:
Is anyone running their NMC server successfully in a virtual machine?

I am. I am running 7.6.2.5's NMC on a 32-bit RHEL5 VMware guest.

I migrated from a Solaris system by wiping out the database and starting from
scratch.

I use Theirry's NetWorkerReporter for my statistics gathering...

--
Matt Powell
mtpowel < at > clemson.edu
Storage Administrator
Clemson University
340 Computer Court
Anderson, SC, 29625
office: 864-656-0589
cell: 864-247-2823


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Eugene,

I suggest you open a service request with EMC. The issue you are having should certainly not occur. I can tell you that I have been running NMC on a RHEL 5 AS VM for at least four years without issue.

On 11 16, 2011, at 9:03 AM, Eugene Vilensky wrote:

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


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

In regard to: [Networker] NMC db corruption, Eugene Vilensky said (at...:

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 haven't seen that exact error, but I have seen these:

E. 07/22 02:02:26. *** ERROR *** Assertion failed: 102300 (9.0.2.3308)
E. 07/22 02:02:26. File associated with given page id is invalid or not open

E. 07/22 15:07:37. *** ERROR *** Assertion failed: 102300 (9.0.2.3308)
E. 07/22 15:07:37. File associated with given page id is invalid or not open

E. 07/29 07:50:25. *** ERROR *** Assertion failed: 201501 (9.0.2.3308)
E. 07/29 07:50:25. Page for requested record not a table page or record not present on page

One bit of information you didn't provide that might be relevant is what
the VM OS and version is.

I can tell you that all of our database corruption issues started when
I moved the NMC to a RHEL 6.1 host. It was only after opening a ticket
with EMC that I discovered that RHEL 6.x is *not* supported for the NMC.
It is for networker server, storage node, and clients, but not NMC.

The tech I worked with actually contradicted some of the software
compatibility guide, saying that NMC was supported on RHEL 6.0 but not
6.1, which to me seems like a ridiculous stance for EMC to take
considering how they do support for all other point releases, but in my
case it didn't matter. I moved the NMC to a RHEL 5.7 host, and all the
issues went away.

Tim
--
Tim Mooney Tim.Mooney < at > ndsu.edu
Enterprise Computing & Infrastructure 701-231-1076 (Voice)
Room 242-J6, IACC Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

On Wed, Nov 16, 2011 at 11:52 AM, Tim Mooney <Tim.Mooney < at > ndsu.edu> wrote:
The tech I worked with actually contradicted some of the software
compatibility guide, saying that NMC was supported on RHEL 6.0 but not
6.1, which to me seems like a ridiculous stance for EMC to take
considering how they do support for all other point releases, but in my
case it didn't matter.  I moved the NMC to a RHEL 5.7 host, and all the
issues went away.

Nail meets head. Considering this footnote I don't think I can blame
myself or the tech I'm currently working with:

"Red Hat Enterprise Linux 6.1 is supported for NetWorker Client,
NetWorker Storage Node, NetWorker Server and NMC from NW 7.6.2
onwards"


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER