NetWorker: How to mark a ssid/clone id as notsuspect

Samenvatting: This article provides general information about how to change a "suspect" save set to "notsuspect."

Dit artikel is van toepassing op Dit artikel is niet van toepassing op Dit artikel is niet gebonden aan een specifiek product. Niet alle productversies worden in dit artikel vermeld.
Bekijk andere hulpbronnen

Instructies

A NetWorker save set becomes "suspect" when NetWorker determines that the save set cannot be trusted for recovery. This flag is automatically applied by NetWorker and typically indicates that something went wrong during creation, validation, cloning, or media handling.

 

Here are the most common reasons that a save set becomes suspect:

  1. Incomplete or Failed Backup. NetWorker marks the save set suspect if:
    1. The backup terminated early
    2. The client connection dropped
    3. Data movers (nmm, nsrmmd, so forth) failed
  2. Missing or Unavailable Backup Media. A save set is marked suspect if NetWorker cannot read or validate the data during:
    1. Clone operations
    2. Staging
    3. Recovery preparation
    4. Tape unreadable or mislabeled.
    5. Data Domain retention lock or retention expiration issues.
    6. Data Domain file system issues.
  3. Cloning Failures. If a clone operation fails to fully copy a save set (for example: Due to read errors), the original save set can be marked as suspect.
  4. Data Corruption Detected. NetWorker or storage reports corruption.
  5. Client File Index or Media Database validation failed. Index inconsistencies can cause NetWorker to mark a save set suspect:
    1. Corrupted client file index (CFI)
    2. Corrupted media database records
    3. Temporary read error during validation
    4. Partially purged or expired index segments
NOTE: The focus of this article is not identifying the cause of why the save set was marked suspect. A "suspect" flag does not automatically mean that the data is unrecoverable. It means that NetWorker cannot guarantee its integrity. The data is still recoverable if it exists on storage media. This article provides steps for marking a suspect save set "notsuspect."

Step 1: Backup the Media Database:

  1. Perform a Server Protection -> Server backup. Collect the bootstrap save set details: mminfo -B
  2. (Optionally): Export the media databases current state into an XDR file: How To Export the NetWorker Media Database Using nsrmmdbasm

Step 2: Assess suspect Save Sets and identify the ones you want to change to notsuspect:

From an elevated prompt on the NetWorker server, run the mminfo command to:

  1. Get the exact details of the save set IDs (SSID) which are marked as suspect:
mminfo -avot -q suspect -r "savetime(20),client,ssid,cloneid,sumflags,clflags,volume"
  1. Alternatively, you can export the output into a CSV file and review from an XLS reader (Microsoft Excel):
mminfo -avot -q suspect -r "savetime(20),client,ssid,cloneid,sumflags,clflags,volume" -xc, > mminfo.csv
  1. Display only the SSID/CLONEID of the suspect save sets:
mminfo -q suspect -xc/ -r ssid,cloneid

Step 3: Change the save sets to notsuspect:

WARNING: Ensure that you understand the conditions that lead to the save sets being marked suspect. This article has outlined some scenarios where this may occur. In scenarios where there are only specific save sets marked suspect it may proceed with the options below. In scenarios where large amounts of save sets are suspect, investigate the cause before changing them to notsuspect. Consult with NetWorker support for assistance in determining this cause.

Option One: Individual Save Sets:

Save Set IDs are marked "notsuspect" using the NetWorker nsrmm command from an elevated NetWorker server prompt:

nsrmm -y -o notsuspect -S SSID/CLONEID
Example: 
nsrmm -y -o notsuspect -S 12345/12369
nsrmm -y -o notsuspect -S 12345/12370
nsrmm -y -o notsuspect -S 12345/12371

Option Two: Multiple Save Sets:

  1. Create an input file (for example: ssid.txt). The file must only contain SSID/CLONEID combinations. This can be done manually after performing options Step 2.1 or 2.2, or by generating a file containing all suspect save sets:

Linux:

mminfo -q suspect -xc/ -r ssid,cloneid | grep -v ssid > ssid.txt
Windows (PowerShell): 
mminfo -q suspect -xc/ -r ssid,cloneid | Select-String -NotMatch '^\s*ssid\b' | Set-Content -Encoding ASCII ssid.txt
  1. Use a loop to mark all SSID/CLONEID from the input file as notsuspect:
Linux: 
while read SID; do nsrmm -o notsuspect -y -S ${SID}; echo ${SID}; done < ./ssid.txt
Example: 
[root@nsr ~]# mminfo -avot -q suspect -r "savetime(20),client,ssid,cloneid,sumflags,clflags,volume"
    date     time   client     ssid          clone id fl clflg volume
    01/30/2026 10:00 nsr.amer.lan 3262957455 1769785225 cr s nsr.amer.lan.dddefault.001
    01/30/2026 10:04 nsr.amer.lan 3246180451 1769785443 cr s nsr.amer.lan.dddefault.001
    01/31/2026 10:00 nsr.amer.lan 3028162808 1769871607 cr s nsr.amer.lan.dddefault.001
    01/31/2026 10:00 nsr.amer.lan 2961053959 1769871623 cr s nsr.amer.lan.dddefault.001
    02/01/2026 10:00 nsr.amer.lan 2726259321 1769958009 cr s nsr.amer.lan.dddefault.001
    02/01/2026 10:00 nsr.amer.lan 2675927701 1769958037 cr s nsr.amer.lan.dddefault.001
    02/02/2026 10:00 nsr.amer.lan 2474687480 1770044408 cr s nsr.amer.lan.dddefault.001
    02/02/2026 10:00 nsr.amer.lan 2390801411 1770044419 cr s nsr.amer.lan.dddefault.001
    02/05/2026 14:00 nsr.amer.lan 1434773694 1770318014 cb s nsr.amer.lan.dddefault.001
    02/06/2026 10:00 nsr.amer.lan 4119200246 1770390006 cr s nsr.amer.lan.dddefault.001
    02/06/2026 10:00 nsr.amer.lan 4085645824 1770390016 cr s nsr.amer.lan.dddefault.001
[root@nsr ~]# mminfo -q suspect -xc/ -r ssid,cloneid | grep -v ssid > ssid.txt
[root@nsr ~]# while read SID; do nsrmm -o notsuspect -y -S ${SID}; echo ${SID}; done < ./ssid.txt
1434773694/1770318014
3246180451/1769785443
2961053959/1769871623
2675927701/1769958037
2390801411/1770044419
4085645824/1770390016
3262957455/1769785225
3028162808/1769871607
2726259321/1769958009
2474687480/1770044408
4119200246/1770390006
[root@nsr ~]# mminfo -q suspect -xc/ -r ssid,cloneid | grep -v ssid > ssid.txt
6095:mminfo: no matches found for the query
[root@nsr ~]#
Windows (PowerShell): 
Get-Content .\ssid.txt | % { nsrmm -o notsuspect -y -S $_ | Out-Null; "Changed: $_" }
Example: 
PS C:\Users\Administrator.NETWORKER> mminfo -avot -q suspect -r "savetime(20),client,ssid,cloneid,sumflags,clflags,volume"
    date     time   client     ssid          clone id fl clflg volume
1/21/2026 1:47:17 PM lnx-srvr02.networker.lan 4151385874 1769021240 cb s win_srvr02.networker.lan.dddefault.001
1/21/2026 2:00:59 PM lnx-srvr02.networker.lan 4134609481 1769022063 cb s win_srvr02.networker.lan.dddefault.001
1/21/2026 2:18:39 PM lnx-srvr02.networker.lan 4084278892 1769023122 cb s win_srvr02.networker.lan.dddefault.001
1/22/2026 2:01:02 PM lnx-srvr02.networker.lan 4017255370 1769108466 cb s win_srvr02.networker.lan.dddefault.001
PS C:\Users\Administrator.NETWORKER>
PS C:\Users\Administrator.NETWORKER> mminfo -q suspect -xc/ -r ssid,cloneid | Select-String -NotMatch '^\s*ssid\b' | Set-Content -Encoding ASCII ssid.txt
PS C:\Users\Administrator.NETWORKER>
PS C:\Users\Administrator.NETWORKER> Get-Content .\ssid.txt | % { nsrmm -o notsuspect -y -S $_ | Out-Null; "Changed: $_" }
Changed: 4151385874/1769021240
Changed: 4084278892/1769023122
Changed: 4134609481/1769022063
Changed: 4017255370/1769108466
PS C:\Users\Administrator.NETWORKER>
PS C:\Users\Administrator.NETWORKER> mminfo -avot -q suspect -r "savetime(20),client,ssid,cloneid,sumflags,clflags,volume"
6095:mminfo: no matches found for the query
PS C:\Users\Administrator.NETWORKER>
NOTE: The information in this article also applies if you want to change a notsuspect save set to suspect. To do this, simply change -o notsuspect to -o suspect wherever seen.

Extra informatie

Getroffen producten

NetWorker

Producten

NetWorker
Artikeleigenschappen
Artikelnummer: 000023409
Artikeltype: How To
Laatst aangepast: 09 feb. 2026
Versie:  7
Vind antwoorden op uw vragen via andere Dell gebruikers
Support Services
Controleer of uw apparaat wordt gedekt door Support Services.