Generated by Jive on 2015-04-23-07:001

How to troubleshoot NetWorker indexcorruption issues?

Product

NetWorker

Symptoms

• Index corruption• Error: 'error on open of recfile for index [index-name](-214)'• Error: 'Cannot mount index [index-name](-214)'• Error: 'missing file sr_i1'• Error: 'nothing in index at this time'• Cannot browse files• Unable to perform backup due to index corruption• Unable to perform recovery due to index corruption• Slow writing to tape• mmlocate loses locations of volumes when NetWorker daemons are restarted

Cause

The NetWorker server experienced and outage during the backup causing corruption ofclient index(es).

Note: The reasons for index corruption are many and varied. A NetWorker server crash isonly one reason for such corruption.

Resolution

Run index and media database consistency checks. Run media database controlledcompression procedure if regular index and media database consistency checks do notrectify problem. Recover client file index if index and media database consistency checksand media database controlled compression do not fix the problem.

How to troubleshoot NetWorker index corruption issues?

Generated by Jive on 2015-04-23-07:002

Client file index consistency check:

From command prompt of nsr bin directory run:

nsrck -F <client name>

Note: Command can and may need to be run 2 to 3 times.

Note: refer to nsrck man page or Command Line Reference Guide for more informationon the available switches for nsrck.

If item 1 does not fix the problem proceed to item 2.

Run media database consistency check:

From command prompt of nsr bin directory run:

nsrim -X

If index and media database consistency checks (as per items 1 and 2) do not fix theproblem proceed to item 3.

Run media database controlled compression procedure:

Consistency checks and controlled compression.

Note: 'daemons' are in reference to UNIX processes and 'services' are in reference toWindows services. Replace forward slashes (/) which are in reference to UNIX systems withbackslashes (\) on Windows systems.

Media Database Compression:

1. 1. Shut down NetWorker daemons/services2. Remove /nsr/mm/.cmprssd3. Restart NetWorker daemons/services

How to troubleshoot NetWorker index corruption issues?

Generated by Jive on 2015-04-23-07:003

4. Run nsrim -X

Then run media database scavenging:

1. 1. Shut down NetWorker daemons/services2. Cause a "controlled corruption" by removing:

• /nsr/mm/mmvolume6/{*_i*,ss,vol}3. The following files should remain:

• ss.0, vol.0, VolHdr4. Restart NetWorker daemons/services

If index and media database consistency checks (as per items 1, 2, and 3) do not fix theproblem proceed to item 4.

Either recover index from date/time prior to corruption, or start with new index:

• To recover Client File Index use "nsrck -L 7 client_name"• To start with new index:

1. 1. 1. Stop NetWorker daemons (UNIX)/services (Windows)2. Rename corrupt index directory3. Restart NetWorker daemons (UNIX)/services (Windows)4. Create new index (nsrck -c client_name)