macsys Posted February 10, 2003 Report Share Posted February 10, 2003 Anyone know if there's a filesize limit to the catalog files? Getting volume full errors. Running latest version of Retrospect on X Server. Last week it was the -43 errors now it's this. Link to comment Share on other sites More sharing options...
Mayoff Posted February 10, 2003 Report Share Posted February 10, 2003 The catalog size is limited to 2 GB, while a file backup set is limited to 2 TB. What is the exact text in the operations log? Volume full usually means that the disk containing the catalog file is full. Link to comment Share on other sites More sharing options...
macsys Posted February 10, 2003 Author Report Share Posted February 10, 2003 Can't add this much data the limit is 1,000.0 G. The volume it's backing up is only 275 Gig, with 75 gig avail. The server that the backup is running from still has 55 gig left of it. The backup catalog size is 280.1 Meg. Link to comment Share on other sites More sharing options...
macsys Posted February 10, 2003 Author Report Share Posted February 10, 2003 Another question. Is the 2TB for the whole backup or just the individual share points. Example: I have 5 share points being backed up. 222 Gig 69 Gig 4 Gig 106 Gig 384 Gig Link to comment Share on other sites More sharing options...
AmyJ Posted February 10, 2003 Report Share Posted February 10, 2003 The 2TB limit is for the entire backup set. Link to comment Share on other sites More sharing options...
CallMeDave Posted February 10, 2003 Report Share Posted February 10, 2003 Quote: The volume it's backing up is only 275 Gig, with 75 gig avail I believe the size of the catalog depends a great deal on the number of files in the Backup Set, not just the total size of the data. Lots of files = larger catalog file. The answer for us was to use catalog compresson. It _greatly_ increased Retrospect's ability to store the information for files. Configure->BackupSets->Configure->Options Dave Link to comment Share on other sites More sharing options...
macsys Posted February 10, 2003 Author Report Share Posted February 10, 2003 Just got off the phone with Dantz tech support, your wrong here guy, the total is only 1Terabyte. Iam at that limit. The total is 997Gig. I am going to create a new set to see if this cures the problem. Link to comment Share on other sites More sharing options...
macsys Posted February 10, 2003 Author Report Share Posted February 10, 2003 Quote: Quote: The answer for us was to use catalog compresson. It _greatly_ increased Retrospect's ability to store the information for files. already compress the catalogs Link to comment Share on other sites More sharing options...
AmyJ Posted February 10, 2003 Report Share Posted February 10, 2003 My post was incorrect. The file backup set size is 1TB. The limit for a network file backup set is 2GB. Sorry for any confusion. Link to comment Share on other sites More sharing options...
Mayoff Posted February 10, 2003 Report Share Posted February 10, 2003 Yep, I was wrong too. I got my products confused. Retrospect for Macintosh has a 1000GB limit. Retrospect for Windows has lifted that limit, and would not get this error. Link to comment Share on other sites More sharing options...
AmyJ Posted March 24, 2003 Report Share Posted March 24, 2003 If you would like to be notified when the 1 Terabyte limit has been lifted from Retrospect for Macintosh, please subscribe to the following Newsletter. Only Dantz will be posting to this list, so don't worry about unwanted emails. http://list.dantz.com/mailman/listinfo/terabyte_limit Link to comment Share on other sites More sharing options...
Mayoff Posted March 28, 2003 Report Share Posted March 28, 2003 If you would like to be notified when the 2GB catalog file limit has been addressed on the Macintosh, sign up for the following newsletter: http://list.dantz.com/mailman/listinfo/mac_catalog_size Link to comment Share on other sites More sharing options...
mounce Posted March 28, 2003 Report Share Posted March 28, 2003 I don't think the problem of the original post was correctly interpreted. I have the same problem tyring to backup a Windows 2000 drive, but the 1,000GB log record is clearly wrong. The drive can't be that big. Our current hypothesis is that the Windows machine, that has been running for years without being rebooted, is suffering a common Windows problem that these systems tend to corrupt themselves if left on for too long. The problem might be in the file system on the Windows machine needing to be cleaned up. Does anyone else have a problem with this? The question is whether Dantz Retrospect is wrong by identifying a PC having a 1,000GB drive, or whether the PC is corrcupt by identifying its files as that amount when they can't be that big. Link to comment Share on other sites More sharing options...
AmyJ Posted March 28, 2003 Report Share Posted March 28, 2003 From the Knowledgebase: http://www.dantz.com/index.php3?SCREEN=knowledgebase Finder.dat files under Windows When scanning a Windows client, Retrospect 5.0.236 and 5.0.238 may incorrectly report an amount of data to back up that far exceeds the total capacity of the volume scanned. This problem occurs when Retrospect encounters one or more "finder.dat" files on the Windows client volume. Finder.dat files are created when dual-fork Macintosh files are copied to a Windows volume through utilities such as Mac OS's File Exchange or Retrospect's Duplicate functionality. They are used to track the multiple parts of the Mac file while it's on the Windows volume. Dantz is working on a solution to this problem. In the meantime, deleting the finder.dat files from the Windows client volume will alleviate the problem, though the files they represent cannot later be returned to a Mac OS computer with their Mac-specific properties intact. If you would like to be notified when the finder.dat issue has been addressed on the Macintosh, sign up for the following newsletter: http://list.dantz.com/mailman/listinfo/finder.dat Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.