NetWorker: Scanner fails on some savesets with error "scanner: Unable to create save set for SSID"
Summary: The scanner fails on some savesets with error: "scanner: Unable to create save set for SSID 'ssid number' internal error - cannot generate new save time"
Symptoms
Scanned media from another NetWorker server into a database
When scanning savesets from one NetWorker server to another, some savesets fail with error:
scanner: Unable to create save set for SSID 'ssid number' internal error - cannot generate new save time
Cause
Product limitation
The 'nsavetime' is a unique epoch timestamp for each saveset.
This issue is because the nsavetime that the scanner is attempting to scan into the media database is already in use and associated with an existing saveset belonging to the destination server.
To verify:
For one or more failing savesets, go to the original server where the backup was generated.
Run:
mminfo -q ssid=<ssid number> -r nsavetime,client,name,savetime
Where the "ssid number" is from the original error generated from the scanner.
The first field of the output is the nsavetime (epoch) timestamp for that saveset.
Now, on the destination server (where the scanner is being attempted) run:
mminfo -av -r nsavetime,ssid,client,name,savetime | grep <nsavetime from above output>
The output shows that the same timestamp exists in the destination media database, but the client name and saveset name are different to the one being scanned in.
Because of this, NetWorker prevents a duplicate saveset with the same timestamp from being scanned into the database.
Resolution
This is a product limitation.
Suggested workarounds:
- Perform recovery on the original NW server that performed the original backup
- Create a separate, dedicated scanner/recovery NetWorker server, with no active backups to run the scanner operation on