mjbolzan Posted March 25, 2008 Report Share Posted March 25, 2008 When i back up, the scanning of the time machine volume has just started throwing the error message Scanning incomplete, error -108 (not enough memory). This error seems wrong on its face. it also causes the backup to be incomplete so all the devices re-scan and are re-backed up until the backup server window closes. I have Retrospect version 6.1.138 running on a MacBook Pro 15", 2.4 GHz, 4 GB RAM. OS X 10.5.2. 320 GB internal volume partitioned into 3, all backed up. all programs are shut down. I backup to file sets on firewire drives. I use backup server scrips. the firewire disks are "400 GB" disks partitioned into 2 volumes with the backup partition being 342 GB. I have attached to the computer another firewire drive which contains time machine backups--all 3 internal partitions backed up there. I have excluded the time machine volume from the backup. (By the way, is anyone else irritated that when excluding a volume, retrospect still scans the entire volume?) the time machine volume has been attached for months. current stats are-- capacity: 435.5 GB (device is partitioned) used: 257.8 GB available: 177.7 GB Any solutions? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 25, 2008 Report Share Posted March 25, 2008 I have excluded the time machine volume from the backup. (By the way, is anyone else irritated that when excluding a volume, retrospect still scans the entire volume?) You should not be using a selector to exclude the volume. The volume should not be listed as a source in the script. If the volume is removed as a source, it won't get scanned. If you are using a volume container, then you need to use selected volumes instead. Quote Link to comment Share on other sites More sharing options...
mjbolzan Posted March 26, 2008 Author Report Share Posted March 26, 2008 You should not be using a selector to exclude the volume. The volume should not be listed as a source in the script. If the volume is removed as a source, it won't get scanned. Thank you for your reply. I'm backing up the "local desktop" which has variable things attached. I'd prefer not to have to explicitly name the things i want to backup or exclude. I use a particular naming convention which allows me to easily exclude most volumes i do not want backed up with a single selector. Having an exclude volume selector not scan seems the desirable behavior to me.... Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted March 26, 2008 Report Share Posted March 26, 2008 Having an exclude volume selector not scan seems the desirable behavior to me.... Yep. I mentioned this to the fine folks at the EMC booth at Macworld this year; since Retrospect already knows the unique identifier of logical volumes as well as of defined Subvolumes, Retrospect should be able to ignore any specified volume it encounters during its walk down the tree _before_ scanning it. 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.