At 6:53 AM -0600 24/11/00, Don Foy wrote:
I want
everything perfect for a backup, since a less than perfect backup is
absolutely useless. That one byte it missed and didn't tell me about may
have been in the middle of a file that could cost me several thousands
dollars.
I agree, but in that
At 12:52 PM -0600 24/11/00, Pam Lefkowitz wrote:
So Retrospect reports errors that it finds in the network setup that
doesn't affect ANYTHING else? If these errors existed then why does
nothing else complain?
Yet.
I copy large files from one machine to another, but that never fails
Yet.
Hi Ken,
The members of this list who are suggesting that your 519 errors are due to
something other than a problem with Retrospect are not doing so because they
"blindly follow the dogma that Retrospect is perfect," it's because they
have found it themselves to be true...for some of them, even
Background:
A lot of our backup clients are computers that get used for data
acquisition. Data acquisition can be adversely affected when Retrospect
starts reading a lot of data off the hard drive ;-)
The users generally know when the backups are coming, but they don't
always remember. I'd like
The users generally know when the backups are coming, but they don't
always remember. I'd like to give them a way to automatically script
turning the Retrospect client off at the beginning of an experiment, and
to turn it back on at the end (or, more likely, at the next reboot).
It is possible
The users generally know when the backups are coming, but they don't
always remember. I'd like to give them a way to automatically script
turning the Retrospect client off at the beginning of an experiment, and
to turn it back on at the end (or, more likely, at the next reboot).
It is possible
I'd like to give them a way to automatically script
turning the Retrospect client off at the beginning of an experiment, and
to turn it back on at the end (or, more likely, at the next reboot).
The issue is probably the performance hit when the backup is running,
rather than simultaneous access
Hi again,
I only received one response to the email below about 102
errors disappearing after restarts...so if anyone else has any light
to shed it would be appreciated. Since I posted we have found that if
IE crashes (which it does extremely frequently on the backup) machine
then
At 9:00 PM -0800 26/11/00, Craig Isaacs wrote:
Hi again,
I only received one response to the email below about 102
errors disappearing after restarts...so if anyone else has any light
to shed it would be appreciated. Since I posted we have found that if
IE crashes (which it does
I'm having the same type of problem with a lone G4 on a small
network. The other systems there, a blue G3, a beige tower G3 plus a
clone and a 6100, all seem to get backed up without fail.
I tried replacing the 10Bt hub with a Linksys 10/100 hub thinking
that would do the trick. It seemed to
At 9:02 AM -0800 26/11/00, Eric Ullman wrote:
he was
fairly certain that the problem was a bug in Retrospect.
I hope you understand that is NOT what I have been suggesting.
I need to finish rebuilding my network then I can give it a good
testing with a variety of backup servers, MacOS9 (X
I'm having the same type of problem with a lone G4 on a small
network. The other systems there, a blue G3, a beige tower G3 plus a
clone and a 6100, all seem to get backed up without fail.
[snip]
Just another data point:
We have 7 G4's here (early PCI to newest AGP) on our network here on
12 matches
Mail list logo
