Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About jim144

  • Rank
    Occasional Forum Poster
  1. Thank you, CallMeDave for your prompt and clear answer. I was hoping to make a duplicate of all volumes on the client computer, which would become its complete and total image-- and which could be used as if it were a bootable clone. Which is the better entity for a total restore, a Retrospect backup or a bootable clone? Or are they equal in reliability? Is Retrospect capable of creating a finder-readable clone? If not, what is a good means of creating one? Thanks, JIM
  2. Trying to duplicate a client iMac with 23 GB. Only the "hard drive" or one of the five volumes on the client duplicate. How can I duplicate the entire client computer so it can be completely restored from this duplicate? Thank you, JIM
  3. Phillippe, You can make two backups. Do a "Duplicate" and you will find that it is readable as it is on your Mac desktop. Also do a "Backup". That one will not be readable, but Retrospect makes a ciopy of all the invisible files, such as preferences, permissions, extensions, etc. If you ever have the necessity to totally restore a hard drive, this is the one to use for the restore. Don't forget to backup both frequently.
  4. Here are two selectors thast don't work. JIM The instructions below do not prevent the Pictures, Music, or Movies folders from being backed up: Include files matching selector All Files or… but always exclude files matching name exactly matches Pictures or matching name exactly matches Music or matching name exactly matches Movies Nor does this below exclude Pictures: Include everything but always exclude files matching name exactly matches Pictures
  5. I did use "enclosing folder" to avoid backing up mu Pictures folder. For insurance I also added Boolean OR with path, and with label color. It still isn't excluded. JIM
  6. I exclude a file (by name, or color, or by path) from a backup, but it gets backed up anyway. Sometimes only the "excluded" folder gets backed up. Can anyone tell ne why things are not working? Thanks. JIM [Retrospect version 6.0.204; Mac OS 10.3.9; 750MB RAM; backing up 60G from internal 8OG via Firewire to OWC HD 250G.]
  7. Dave, Thank you for your reply. I am trying to do Duplicate my internal drive excluding three large folders (to save space on my external HD). The script includes: everything except caches; and excludes (with standard selectors), the Music, Pictures, and Movies folders. I get on my external HD almost the opposite of what I am looking for. I get the applications folder partially filled, the system folder partially filled, and the entire Music, Movie, and Music folders. What could be causing this? Do you think an update to 6.1 will fix this, or should I examine my thinking? JIM
  8. Would someone be kind enough to explain the difference between “replace entire disk” and “replace corresponding files” in duplicate backups. Thanks. Retrospect version 6.0.204; Mac OS 10.3.9; 750MB RAM; backing up 60G from internal 8OG via Firewire to OWC HD 250G.]
  9. An incremental backup of 60G on an 80G internal HD can take only a few minutes, but the preceding scan time seems forever. Is there a way to speed up the scan? Thanks. [Retrospect version 6.0.204; Mac OS 10.3.9; 750MB RAM; backing up 60G from internal 8OG via Firewire to OWC HD 250G.]
  10. To save space on my backup hard drive, I’ve scripted exclude filters on files that do not change, particularly my Macintosh “Pictures” folder. But they are not being excluded and are backed up anyway in spite of the filter. I’ve tried: label, size above, path, folder name. Please suggest what’s not working. Thanks. [Retrospect version 6.0.204; Mac OS 10.3.9; 750MB RAM; backing up 60G from internal 8OG via Firewire to OWC HD 250G.]
  11. Each time a .jpg file is opened and closed in Photoshop it recompresses and the image degrades (loss, or modification of information). Does the use of data compression in Retrospect or hardware cause this same type of degradation? Thanks. [Retrospect version 6.0.204; Mac OS 10.3.9; 750MB RAM; backing up 60G from internal 8OG via Firewire to OWC HD 250G.]
  12. I use Retrospect's duplicate feature. There are others like carbon copy Cloner and Superduper. Storing a backup dribe in Mailboxes is clever. Consider encrypting your backup for protection in case of theft.
  13. I think you've done a good job figuring out the up to date way of backing up. I did what you are planning to do by using two HDs, with one off-premises. Further: 1) I do a copy/duplicate/finder-type backup one night and a proprietary Retrospect incremental backup on alternate nights with scripted schedules. I would use the Retrospect backup for a complete restore and the readable backup for the occasional restoral of a particular file. 2) I suggest a complete backup rather than a partial backup of key files. I've had to completely restore on three occasions and never again want to go through what I did the first time from a partial backup--re-enter applications, updates, registration codes, and preferences. 3) Above is the overview. Actually, I use a 250GB drive and have room for multiple backups. I alternate two Retrospect backups (as well as the duplicate) and recycle each one every four months, using a two month offset. That way I always have two months worth of snapshots at recycle time.
  14. Thank you for your replies. A Dantz tech informs me that the Backup is the better way to restore from because it has recorded invisible files. permissions, etc. that render a restored disk to function the way the original did. He implies that the duplicate is missing a lot of behid-the-scenes items and may not function well. I am going to do save both. I'll use the backup for a full restoral and use the duplicate to pick up an occasional file that I have acciddntally deleted. The problerm with the duplicate is that it is the latest version, instead of incremental with snapshots, so that if I find a file is corrupted, I can't go back to an earlier version. My answer to this is to record three of these and rotate every other day giving myself about a week of backlogged items. JIM
  15. My aim in backing up is to have a complete, bootable image of my source drive. Using MacOS 10.3.7, Retro 6.0.204. Then, if the source drive gives up, hopefully I can do a complete functional restore, including permissions, etc., (from the backup on an external hard drive). The Question: Which will give a better restoration-- a file backup or a duplicate backup? Thanks, JIM