creativearc Posted December 8, 2007 Report Share Posted December 8, 2007 I've searched the forums for instances of Leopard users and a '2.0 G' backup set limit. I'm on an intel mac mini, and the clients are all intel iMacs running client version 6.1.130. Is there a way around this? Do I have to uninstall and go to an earlier version? I don't have the exact error handy, but it's roughly this: 'The backup set can not fit that much data. The limit is 2.0 G' Thanks! Link to comment Share on other sites More sharing options...
Mayoff Posted December 8, 2007 Report Share Posted December 8, 2007 Can you provide some more detail? What type of backup drive is this? Tape, hard disk, dvd? What type of backup set? I suspect you have a hard disk formatted for Windows and not Macintosh. Link to comment Share on other sites More sharing options...
rhwalker Posted December 8, 2007 Report Share Posted December 8, 2007 What RDU? Link to comment Share on other sites More sharing options...
creativearc Posted December 9, 2007 Author Report Share Posted December 9, 2007 It is a setup that has been working for many years - so the drives are all formatted for Mac OS Extended (Journaled) The backup drive is on an external firewire drive. The backup set is a 'File'. None of my Retrospect settings changed in terms of the backup sets, schedules, or media. Since I upgraded to Leopard I thought upgrading both the software (and clients) was the best course of action. (Since this has been working for 3 years, should any of this matter?) I confess I don't know what RDU means. The retrospect version is 6.1.138 and the clients are all 6.1.130 - updated within the past 2 days. Let me know if you need any more info. Thanks for your help! Link to comment Share on other sites More sharing options...
CallMeDave Posted December 9, 2007 Report Share Posted December 9, 2007 Quote: I confess I don't know what RDU means RDU stands for Retrospect Driver Update. It's a file named "Retrospect 6.1 Driver Update" that lives in the same folder as Retrospect. You can get the version number of the file with a simple Command+I, or you can look in Retrospect's Operations Log for the version number listed each and every time Retrospect is launched. You might want to compare the RDU version of your last working backup against your first failed backup. Dave Link to comment Share on other sites More sharing options...
rhwalker Posted December 9, 2007 Report Share Posted December 9, 2007 The complete version history (and downloadable files) for the RDUs is here: http://kb.dantz.com/article.asp?article=7886&p=2 Link to comment Share on other sites More sharing options...
creativearc Posted December 10, 2007 Author Report Share Posted December 10, 2007 OK - I downloaded RDU 6.2.12.101. Previously I had no RDU files in my retrospect folder. I get the same error: the relevant portion of the log is below: ∆ Retrospect version 6.1.138 launched at 12/10/2007 7:19 AM + Retrospect Driver Update, version 6.1.12.101 + Normal backup using Paul iMac at 12/10/2007 7:20 AM To backup set Paul-iMac… - 12/10/2007 7:20:02 AM: Copying Users on Paul… 12/10/2007 7:20:02 AM: Connected to Paul Can't add that much data to backup set. The limit is 2.0 G. 12/10/2007 7:26:15 AM: Execution incomplete. Remaining: 312924 files, 59.0 GB Completed: 0 files, zero KB Performance: 0.0 MB/minute Duration: 00:06:13 (00:06:04 idle/loading/preparing) Link to comment Share on other sites More sharing options...
rhwalker Posted December 10, 2007 Report Share Posted December 10, 2007 You still haven't addressed the format of your destination disk (external firewire drive). Link to comment Share on other sites More sharing options...
creativearc Posted December 10, 2007 Author Report Share Posted December 10, 2007 I indicated post #104484 that it is Mac OS Extended (Journaled). The drive has been Mac formatted for a few years - it was never NTFS or any other format. Note: I should also add that I never recall installing any RDU in the past - this seems to be a first for me. Should I considering digging up an old RDU version? (not sure how helpful that will be if I didn't have any installed RDU files to begin with) Thanks! Link to comment Share on other sites More sharing options...
creativearc Posted December 10, 2007 Author Report Share Posted December 10, 2007 If it helps, this appears to be the last successful backup from mid-November: + Normal backup using mini at 11/17/2007 3:14 PM To backup set mini… - 11/17/2007 3:14:52 PM: Copying Macintosh HD… 11/17/2007 4:02:33 PM: Comparing Macintosh HD… 11/17/2007 4:02:35 PM: Execution completed successfully. Completed: 49 files, 9.9 MB Performance: 17.0 MB/minute (8.7 copy, 294.1 compare) Duration: 00:47:43 (00:46:34 idle/loading/preparing) Quit at 11/17/2007 4:02 PM Link to comment Share on other sites More sharing options...
CallMeDave Posted December 10, 2007 Report Share Posted December 10, 2007 Quote: If it helps, this appears to be the last successful backup from mid-November: It would help more to see up-log a bit where Retrospect launches, to confirm the version (or absence entirely) of an RDU file. Still, IIRC, Retrospect shouldn't need any RDU to support large File Backup Sets on locally attached volumes, only on network volumes. From the limited log entries provided, the problem is shown when a Retrospect client is the Source, and the problem is not shown when the Source is a local drive on the machine running Retrospect. - Have you had previous success when the Source is a Client? - Have you seen the error when the Source is the local hard drive? Dave Link to comment Share on other sites More sharing options...
Mayoff Posted December 10, 2007 Report Share Posted December 10, 2007 I suspect a problem on the external hard disk. Reformat the disk and create a new backup set. That will usually fix this problem. Link to comment Share on other sites More sharing options...
creativearc Posted December 10, 2007 Author Report Share Posted December 10, 2007 Two things happened to create this problem: 1) Client machines were upgraded to Leopard 2) Retrospect Software was updated to 6.1.138, Clients Upgraded to 6.1.130 - Have you had previous success when the Source is a Client? - Have you seen the error when the Source is the local hard drive? The only scenarios that I've ever tried have been with the current external firewire drive. Link to comment Share on other sites More sharing options...
creativearc Posted December 10, 2007 Author Report Share Posted December 10, 2007 Easy enough, can't hurt to try! I'll perform this action and report my findings. Thank you! Link to comment Share on other sites More sharing options...
rhwalker Posted December 10, 2007 Report Share Posted December 10, 2007 Not sure if this is an issue, but be aware that the partition map for Leopard is different from that for Tiger (not just APM vs. GPT). Russ Link to comment Share on other sites More sharing options...
creativearc Posted December 10, 2007 Author Report Share Posted December 10, 2007 Quote: Not sure if this is an issue, but be aware that the partition map for Leopard is different from that for Tiger (not just APM vs. GPT). Russ On that note, have other Leopard users had success with the transition? Link to comment Share on other sites More sharing options...
creativearc Posted December 10, 2007 Author Report Share Posted December 10, 2007 Quote: I suspect a problem on the external hard disk. Reformat the disk and create a new backup set. That will usually fix this problem. Indeed it did! Thank you! I wouldn't expect to reformat a drive that was already Mac OS Extended format, but hey, whatever works. Link to comment Share on other sites More sharing options...
Mayoff Posted December 10, 2007 Report Share Posted December 10, 2007 The file system was confused and acting like it was fat32. I don't know why this happens, but it does. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.