|
On 29-Oct-2015 12:35 -0500, Jerry Draper wrote:
In a recent DR simulation we restored some libraries with lots of
DDM files.
The target system of the DDM files was NOT on the network as this
was a simulation.
The restore operation of each file failed after a timeout of 315
seconds.
There are many, many DDM files so at 12/hour we weren't getting
anywhere fast.
There are no break messages so you only find out after wondering why
the restore is taking so long.
How can this be managed so we can restore the files and NOT validate
the remote system?
What is the actual information from a spooled joblog? Just a SWAG,
that [the messaging in the joblog will reveal that] the timeout is
nothing to do with contacting a remote system, and instead is a
functional issue with the *DBXREF.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
