Compare errors which mention data or resource offsets usually indicate
device communication problems. You can refer to the Retrospect User's Guide
for general device troubleshooting and maintenance, or contact
[EMAIL PROTECTED] for further troubleshooting steps.
Some things to check for:
1
Suddently Retrospect begins to show a list of
File "xyz" didn't compare at data offset integer
after backing up some clients.
Any suggestions ?
--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED
Title: RE: Backup and Compare Performance ... lots of small files
I'm not familiar with this particular backup device but it sounds like the read head is out of alignment with the write head. To eliminate other causes we would
1. clean the heads
2. run a short test backup/ compare/ restore
Anyone had similar experiences where the hierarchy of the data has a
dramatic effect on performance?
I find that Retrospect on a 10base T network, Backup Server on a
Pentium II 233, Client on a PowerBook G3 266, (or even better, on
Virtual PC on a PB G3 266) can achieve 60MB/min transfer
Guys,
I've just installed a new server for a client and all was going well
until the client stated using his existing data which we had copied to a
group share ... its a slug. This is particularly noticable when doing a
backup, copy is bad but it is even worse during the compare phase