Hi all,
If I have a script that is suppose to finish at 9:00 am, but it didn't
have a chance to go around all the clients yet, can I ask it (
interactively or through script ) to continue until it picked up all the
clients, or to go let's say another 1.5 hours?
Here are my specs:
Here is my
A client is using a Butler SQL Server to support a Panorama database. This
database stores data in RAM. I would like to Retrospect server, running on
the same system to shut it down, so that the data is flushed to a file,
before the backup starts. Butler SQL is not Apple Scriptable (at least
Hi Ben,
Are you receiving this error on one client or more than one? The piton
protocol is a proprietary encapsulation scheme, designed to protect
Retrospect's data packets as they travel over your network. Damaged
encapsulation indicates to Retrospect that the data contained within is
likely
At 12:21 PM -0800 on 13/12/00, [EMAIL PROTECTED] wrote:
Can't initialize source, error -515 (Piton protocol violation)
I have one client (only) who repeatedly has this error. Last night was typical: -515
error at 7pm, 7;30 pm, 8pm (approx), then the script went away did another
Thanks for the tips. Here's a few more details
It only happens on the one client, and there is another one on the same hub
that has no trouble at all. The client has two drives that need backing up
and the trouble seems to be worse on drive d:\, but it sometimes happens on
c:\ as well.
OK, I promised an update on this...
Things are OK on this issue. I had to define subvolumes in order to make
this folder back up, and that was a pain, but seems to work OK. The biggest
problem is that if I add new folders I have to then also add them as
defined subvolumes in Retrospect and
