Forum Discussion
- davidmolineLevel 6
There are a couple of possibilities that may be causing the error. The recovery time from deep archive is typically longer than the timeouts in NetBackup and hopefully this is the issue.
Rather than altering the timeout to suit the retrieval time, it may be better to move the particular backup back to a higher S3 level (standard for instance) and then perform the restore. I think this process is also called warming.
The other possibility is that the backup is corrupt - hence the status 83 (read error).
Cheers
David - Sharad_Singh7Level 4Warming process is taking longer time than 24 hours then it eventually fails. Any suggestions for increasing timeouts.
Related Content
- 12 years ago
- 3 years ago