Layne123 Posted November 12, 2008 Report Share Posted November 12, 2008 I run a duplicate script - moving backups from one 2 TB FireWire 800 drive to another 2 TB drive for off-site backups. I am running an Xserve G5 and using both FW 800 ports. I have had 3 months of successful backups. Then all of a sudden I get these errors: Retrospect version 6.1.138 launched at 11/11/2008 2:25 PM + Retrospect Driver Update, version 6.1.13.101 + Duplicate using Off Site at 11/11/2008 3:41 PM Warning: volume Backups has the Ignore ownership setting enabled. - 11/11/2008 3:41:50 PM: Copying Backups… Can't write file “.DS_Storeâ€, error -43 (file/folder not found), path: “Backups/.DS_Storeâ€. Can't write file “Home Foldersâ€, error -1309 (file too large for allocation block size), path: “Backups/Home Foldersâ€. Can't write file “Home Folders.catâ€, error -36 (i/o error, bad media?), path: “Backups/Home Folders.catâ€. Can't write file “Localâ€, error -36 (i/o error, bad media?), path: “Backups/Localâ€. Can't write file “Local.catâ€, error -36 (i/o error, bad media?), path: “Backups/Local.catâ€. Can't write file “Remoteâ€, error -36 (i/o error, bad media?), path: “Backups/Remoteâ€. Can't write file “Remote.catâ€, error -36 (i/o error, bad media?), path: “Backups/Remote.catâ€. Can't write file “VisComâ€, error -36 (i/o error, bad media?), path: “Backups/VisComâ€. Can't write file “VisCom.catâ€, error -36 (i/o error, bad media?), path: “Backups/VisCom.catâ€. Trouble writing files, error -50 (feature not supported). 11/11/2008 8:11:27 PM: Execution incomplete. Remaining: 15 files, 13 KB Completed: 11 files, 462.1 GB Performance: 1754.9 MB/minute Duration: 04:29:37 After the script errored out, the off-site drive has 2 files on it. 1 entire file copied correctly and then 1 partial file. 78.8 GB of 260 GB File Backup Set Data (The file referenced in this error: Can't write file “Home Foldersâ€, error -1309 (file too large for allocation block size), path: “Backups/Home Foldersâ€). Retrospect continues through the backup process - AFTER the off-site script craps out - backing up hundreds of gigabytes of data to the other FW 800 RAID tower drives which serve as the main backup drive. Once all backup scripts are finished and I check Retrospect the next morning, Retrospect is "not responding" in the Finder and the off-site drive is spinning. If I try and access the off-site drive and/or open Retrospect, the Finder freezes and the only way o recover is to remove the external off-site FW 800 drive. This tends to point to the drive being the culprit, yet I have used the WDDrive Manager utility to look at the off-site drive and it shows the RAID 0 to be working 100% and both drives in the enclosure show that they are running fine. I don't have a spare 2 TB drive to test with. So has anyone experienced this issue? Does anyone have any suggestions? I can try and replace the off-site drive, yet if there's nothing visibly wrong with it I'm unsure about sending it in for RMA... Any input or assistance is greatly appreciated. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted November 12, 2008 Report Share Posted November 12, 2008 (edited) One thing to try might be to update to the current version of Retrospect and RDU (Retrospect Driver Update). Your versions are very old. Updates are here, free: Retrospect updates Also, a question: See the error message, which indicates a filesystem issue. How is this destination share being presented to the machine running Retrospect? (do a Get Info from the Finder on the volume, report what type of a filesystem it shows). The error message may be right (file is too large for allocation block size). Russ Edited November 12, 2008 by Guest Quote Link to comment Share on other sites More sharing options...
Layne123 Posted November 12, 2008 Author Report Share Posted November 12, 2008 One thing to try might be to update to the current version of Retrospect and RDU (Retrospect Driver Update). Your versions are very old. Updates are here, free:Retrospect updates Also, a question: See the error message, which indicates a filesystem issue. How is this destination share being presented to the machine running Retrospect? (do a Get Info from the Finder on the volume, report what type of a filesystem it shows). The error message may be right (file is too large for allocation block size). Russ Thanks. The version is in my original post - first line in the log entry. From what I can tell on the EMC site, it is the latest version. The file system is Mac OS Extended (Journaled). It has been this way all along I believe. I did just notice that the partition scheme in Disk Utility > Partition >Options... was GUID Partition Table. I'm going to reset to Apple Partition Map and see if that remedies. Thanks for the input. Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted November 12, 2008 Report Share Posted November 12, 2008 Then all of a sudden I get these errors:Can't write file ... Sounds like your drive is malfunctioning. Try reformatting, and if the error(s) persist, replace it. Dave Quote Link to comment Share on other sites More sharing options...
rhwalker Posted November 12, 2008 Report Share Posted November 12, 2008 Retrospect version 6.1.138launched at 11/11/2008 2:25 PM + Retrospect Driver Update, version 6.1.13.101 The version is in my original post - first line in the log entry. From what I can tell on the EMC site, it is the latest version. Sorry, no. According to my server's update logs and my backup tapes, Retrospect 6.1.138 and RDU 6.1.13.101 were both released on November 2, 2007. I don't know where you got your misinformation, and it would be helpful if you could post a link to that wrong information so that EMC support could get it corrected. Yes, I took the time to read every line of your original post, including the information about your outdated versions. Once again, I suggest you follow the link I provided in my earlier post, which shows that the current version of Retrospect is 6.1.230 and that the current RDU is 6.1.15.101: Retrospect Mac updates Regards, Russ Quote Link to comment Share on other sites More sharing options...
Layne123 Posted November 12, 2008 Author Report Share Posted November 12, 2008 I'll update and see if that has any affect. Quote Link to comment Share on other sites More sharing options...
Layne123 Posted November 13, 2008 Author Report Share Posted November 13, 2008 I reformatted the drive and the errors continued. Retrospect was able to backup a bit more data before crapping out, yet it did freeze. Turning off the drive and getting the "Device Removal..." error fixes the Retrospect freeze. It is looking like the drive is no longer functioning well with Retrospect. I updated Retrospect and will try one more time to see if the updates remedy the issues I am having. Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted November 14, 2008 Report Share Posted November 14, 2008 It is looking like the drive is no longer functioning well with Retrospect. While literally true, the above statement is overly restrictive. A better conclusion would be that the drive is no longer functioning well. Dave Quote Link to comment Share on other sites More sharing options...
Layne123 Posted November 17, 2008 Author Report Share Posted November 17, 2008 It is looking like the drive is no longer functioning well with Retrospect. While literally true, the above statement is overly restrictive. A better conclusion would be that the drive is no longer functioning well. Dave The backup worked perfectly on the XServe's FW400 port; >500 GB backed up to the 2 TB drive. Maybe its a bad FW 800 port on the drive as I traded FW 800 ports on the server to the other backup drive and the daily backup works perfectly to that drive on both Xserve FW 800 ports. So it seems that, for now, Retrospect was not the issue. Thanks for all your help. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.