Troubleshooting
Problem
A Tivoli Storage Manager Backup-Archive restore data from a different node. The restore operation stops with the ANS1345E and ANS1302E errors.
Symptom
The restore stops with the following messages ;
ANS1345E No objects on server match '<filespec>'
Total number of objects restored: 1,234
Total number of objects failed: 1
Total number of bytes transferred: 5678.91 KB
Data transfer time: 23,456.78 sec
Network data transfer rate: 0.02 KB/sec
Aggregate data transfer rate: 0.01 KB/sec
Elapsed processing time: 12:34:56
ANS1302E No objects on server match query
Diagnosing The Problem
In this case, a restore was performed using client nodename nodeB and data was backed up from nodeA., The following commands were run on nodeA to give authorization to nodeB :
set access backup d:\mydir\* * nodeB
set access backup d:\mydir\*\* * nodeB
The restore operation was then started on nodeB using the following command :
dsmc restore "\\nodeA\d$\mydir\*" .\ -fromnode=nodeA -subdir=yes -ina -todate=<date>
Resolving The Problem
In this case, because the -inactive and -todate options are used, a classic restore is done. While the restore was in progress on nodeB and restoring data from nodeA, an incremental backup was started on nodeA, which expired files which were to be restored by the client on nodeB. The errors were logged because of this scenario.
To avoid running into this situation, do not run a backup from the same nodename that is used with the restore operation and do not expire data for the node while the restore is ongoing. Consider using the "no query" restore protocol, instead of classic, using the pitdate and pittime options instead of the inactive and todate options. For example :
dsmc restore "{\\nodeA\d$}\mydir*" .\ -fromnode=nodeA -subdir=yes -pitdate=<date>
With this command, a no query restore is started and the Tivoli Storage Manager server sends data to be restored to the client, avoiding the errors.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21674199