Certain options, such as SUBDIR, PRESERVEPATH, IFNEWER, REPLACE, and source
and destination file specs are preserved; but other options such as QUIET
or RESOURCEUTILIZATION do not appear to be preserved.
The reference information for RESTART RESTORE says this:
> The restarted restore uses the sam
Andy,
Your suspicion was correct. I displayed the line with "od" options that cause
each byte to be displayed as both a character and an unsigned integer. The
integer value for the character in front of the drive letter turned out to be
150 (en-dash in the Latin I code page) rather than the cor
No bugs with DOMAIN processing that I am aware of that could cause this. My
first guess would be that the character preceding the 'h' is not an ASCII
minus sign character (0x2D), but some kind of typographical hyphen or dash.
Suggestions:
* Open the dsm.opt file with a bona fide plain text editor
We recently discovered that a restarted restore won't necessarily inherit all
of the command line options specified for the original restore. I don't know
whether this is a bug or a feature for which I have not found the
documentation. We started a large command line restore with "-quiet" and
"
We have a client system running 64 bit Windows 2008 and using TSM 7.1.1.0
client code. An H drive that does not need backup coverage was recently added
to the system. The system administrator added the following line to dsm.opt:
domain ALL-LOCAL -h:
The GUI client claims that this line is inva
FYI... we traced this back to an OS issue, haven't pin pointed it yet but
another indicator of an issue in the system is that a ping to LOCALHOST or
LOOPBACK (the 127.0.0.1 address) results in the first packet lost and
response times of 1000 ms.
I was working at upgrading the LANFree agent and it
Is there any way to recover from this error? I'm trying to restore a full vm.
I deleted the vm but before I could get the tape back to do a restore someone
created a new vm with the same name. The backup ran and backed up the new vm.
I've deleted the new vm it but am now getting this error.
