Fulco Posted December 29, 2008 Report Share Posted December 29, 2008 After updating Retrospect Single Server from 7.6.106 to 7.6.123: Matching fails: 90Gb of 300Gb data is backup-ed again, even if the 90Gb is NOT changed at all. (the 90Gb is already in the Backup Set and NOT CHANGED) Please help, Fulco Quote Link to comment Share on other sites More sharing options...
Mayoff Posted December 29, 2008 Report Share Posted December 29, 2008 What do you mean? What is the exact error in the log? Quote Link to comment Share on other sites More sharing options...
Fulco Posted December 29, 2008 Author Report Share Posted December 29, 2008 There is no error in the log. The 300Gb is backup-ed daily to a Disk Backup Set. This was working fine for weeks. Yesterday I updated to v123. Now Retrospect wants to Backup 90Gb of the 300Gb again. These 90Gb is already in the Backup Set (was not changed at all). Fulco Quote Link to comment Share on other sites More sharing options...
Mayoff Posted December 29, 2008 Report Share Posted December 29, 2008 Even if you didn't change the file, something about the file looks different to Windows, which is causing the files to be copied again. Quote Link to comment Share on other sites More sharing options...
Fulco Posted December 29, 2008 Author Report Share Posted December 29, 2008 This is not true. Most files are Read-Only. Between Daily Script to Disk Backup Set(version 106) - Update to v123 - Daily (v 123): only a few hours; no restart; no file changes (did update on a Sunday); result: 90Gb change. So there must be a difference between v106 and v123, how files are matched! Fulco Quote Link to comment Share on other sites More sharing options...
Mayoff Posted December 29, 2008 Report Share Posted December 29, 2008 This is not true. Have you compared the file name, size, creation date and time, modify date and time, meta data including archive bit and NTFS permissions? All it takes is for something very minor to change on the computer to cause a problem. Something as simple as a virus scan could make a change to the file meta data. Have you checked to make sure no backup set members have been marked as missing? Does this data now get backed up every single time you run a backup operation? Quote Link to comment Share on other sites More sharing options...
Fulco Posted December 29, 2008 Author Report Share Posted December 29, 2008 Due to the additional 90Gb the Disk Backup Set reached its limit. Backup Set size 500Gb. Total size of disk to be Backup to this Set about 350Gb. Disk Backup Set: Groom Retrospect Policy. Groom was unable to free enough space for the extra 90Gb. So it asked for new Member. So I can't tell if this 90Gb backed up every time. The matching problem looks like a Forum Post I did before: Topic#27326 Post: "Archiving doesn’t match file already in backup Set" A windows meta-data/permission change due to a Virusscan or any other action, would result in a frequent backing up of large 'NOT' changed data. No, this is not the case! Fulco Quote Link to comment Share on other sites More sharing options...
Fulco Posted December 29, 2008 Author Report Share Posted December 29, 2008 I added 50Gb to the Backup Set Backup Total: 325Gb Backup Set: 512Gb Groom: Retrospect defined policy Now Backup fails, adding the 90Gb of 'already copied' data, can't Groom enough space. So now the Backup Set is unusable. Fulco Quote Link to comment Share on other sites More sharing options...
Mayoff Posted December 30, 2008 Report Share Posted December 30, 2008 You may want to try a catalog rebuild from Disk and then do the groom again. Quote Link to comment Share on other sites More sharing options...
Fulco Posted December 30, 2008 Author Report Share Posted December 30, 2008 Rebuild Catalog. Groomed (removed 210Gb). Run backup: "Preparing to execute...": Assertion failure at "tstring.cpp-1392" Fulco Quote Link to comment Share on other sites More sharing options...
Fulco Posted December 30, 2008 Author Report Share Posted December 30, 2008 Restart Retrospect. Again Run Backup Now 250Gb need to backed up?!? Fulco Quote Link to comment Share on other sites More sharing options...
Mayoff Posted December 30, 2008 Report Share Posted December 30, 2008 Sounds like some type of corruption to the backup set. You may want to try a catalog rebuild since the crash may have hosed something. Quote Link to comment Share on other sites More sharing options...
Fulco Posted January 2, 2009 Author Report Share Posted January 2, 2009 (edited) Rebuild again. Another error. Deleted Disk Backup Set. In the meantime I looked into Retrospect crashing upon Exit: see Forum: "Crash on Exit after update to version 7.6.123" But now the same (Matching wrong) started happening with another Disk Backup Set. Please Help. Fulco Edited January 2, 2009 by Guest 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.