Re: Annoying Backup Error
Maybe it would be better if Retrospect "recognized" the file it itself had messed with and would silently ignore that particular error on that particular file. Just seems fairly logical to me to NOT report that as an error. D At 2:18 PM -0500 10/5/00, Fuzzy Gerdes wrote: Retrospect is simply reporting that the file it backed up is a different size than the file that is on the hard-drive. Which is fine, because here's the sequence: 1. Retrospect backs up it's Operations Log (along with all your other files) 2. Retrospect writes to the Operation Log that it has backed up all the files. 3. Retrospect compares the files it backed up to the files on your hard-drive and discovers that one file is different in size. Yup, it's the file that Retrospect just changed, but it doesn't "know" that, so it logs it as an error. To the Operations Log, ironically enough. Fuzzy on 10/5/00 1:53 PM, Chris Benjamin at [EMAIL PROTECTED] wrote: For the past month or so, I've been getting the following error in my backup report. Now I know that this looks like a pretty minor error and it hasn't had any adverse effect when I've had to restore some files here and there. The thing is though, I get this EXACT same error every single day, regardless of the type of script I'm running. Both a normal backup and recycle backup generate the same error. I'm running the following setup. Any ideas or advice would be greatly appreciated... Mac G4/500 ASIP Server running OS 9.0.4 with Retrospect 4.3 to a single DLT unit on the server. The error log reads as follows... 10/04/2000 8:00:33 PM: Copying File Server 10/04/2000 8:02:18 PM: Comparing File Server Different data size (set: 155,280, vol: 155,341) for file "File Server:System Folder:Preferences:Retrospect:Operations Log". 10/04/2000 8:03:30 PM: 1 execution errors Completed: 103 files, 68.3 MB Performance: 80.3 MB/minute (74.4 copy, 87.1 compare) Duration: 00:02:57 (00:01:15 idle/loading/preparing) Thanks in advance, Chris - Christopher M. Benjamin A Trice Digital 114 - C Dekalb Street Bridgeport, PA 19405 610.272.6900 voice 610.272.8600 fax [EMAIL PROTECTED] http://www.atricedigital.com http://www.atricephoto.com -- Erik Fuzzy Gerdes [EMAIL PROTECTED] Graphics Technology Specialist Playboy Enterprises, Inc. 680 N. Lakeshore Dr. Chicago, IL 60611 -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050.
Feeling Stupid
OK, I'm running Retrospect 4.3 on my Mac, and I cannot, for the LIFE of me, get automated scripts to run. I guess I might just be confused on how this is "supposed" to work, so I'll describe what I'm doing, and hopefully someone can tell me which part of it is wrong. ;-) [ First, I've confirmed that Retro.Startup is in the extensions folder, as I know this is a common source of problems] I have created a scheduled-backup script, for 00:15 every morning. I have tried: (a) quitting Retrospect, thinking that some automated process would start Retrospect back up after midnight to start up the backup (b) left Retrospect running (running idle, but running) all day, so that hopefully at 12:15am, it would wake up and start the backup process. Neither process worked, so I'm at a loss as to exactly how this SHOULD be done. Can someone give me sorta a step-by-step of what I'm doing wrong? Unless I'm blind as well, I don't see any "simple walkthrough" in the manual. :( D -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Problems?: [EMAIL PROTECTED]
Re: Feeling Stupid
At 9:11 PM -0500 8/20/00, Pam Lefkowitz wrote: 1) what does the log say? Aboslutely nothing (well, it shows the times that I started the software, quit the software, etc., but nothing related to the automated backup) 2) do you have any error messages in modal/non-modal boxes (like backup failed with error "blah blah blah")? No. 3) did you save the scripts? Yes. 4) is your date/time correct? (you might want to go to AutomatedCheck to make sure your script is ready and AutomatedPreview to see when the next script is scheduled to run) Date and time is correct (sync'ed via NTP) I deleted my existing easyscript and have started a new one that is, according to preview and check, ready to go tonight at 10pm. (20 mins from now). Does any one beside me find it odd that "backup every day" in easyscript doesn't seem to include weekends? (which was probably my problem last night, so i created a simpler script for this evening telling it to back up weekly on sunday nights.) 5) do you have media in your drive and is it turned on? Yes. D -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Problems?: [EMAIL PROTECTED]
Silly Newbie Questions
OK, the Hardware Compatibility List says "All HP DAT Drives" for both Mac and Windows, but THEN goes on to enumerate a bunch of HP DAT Drives. Is it safe to still say "any HP DAT Drive", or is it just the enumerated HP DAT Drives that are acceptable? Secondly, is anyone using Retrospect to back up Linux boxen also on their network? (and more importantly have such backups been successful and easily restored?) D -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Problems?: [EMAIL PROTECTED]
Re: Silly Newbie Questions
Couldn't you, in theory, just share out "/" as an appletalk/smb share (platform-dependent), and tell Retrospect to back up that network share? Then, in theory, if you had to restore it, you reinstall, share it out and let it dump it back out on the share. The only potential problem I could see there is that ownership/permissions might not survive (which would, indeed, suck). I'm not a big fan of the method you're describing, but if the permissions/ownership problem exists, its the only currently existing way of dealing with it. (Of course, if anyone from Dantz is listening, a Linux client would be spiffy-cool!) At 10:55 AM -0700 8/9/00, Doug Clements wrote: There's no native linux Retrospect client, but I use Retrospect to backup tar archives of my linux machines. I smbmount a share on the NT server running Retrospect, and backup stuff to there using tar, which gets backed up via script by Retrospect. To restore, you have to recover the tar file from backup, reinstall linux and untar the tar file over the entire disk. It's pretty easy if you're familiar with linux, but it can take a long time. -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Problems?: [EMAIL PROTECTED]
