Jump to content

kyeoh

Members
  • Content count

    58
  • Joined

  • Last visited

Community Reputation

0 Neutral

About kyeoh

  • Rank
    Occasional Forum Poster
  1. Hi, this is a suggestion for the development team for a situation I'm facing here. I backup two computers which backup to two hard disks (each as a disk media set) which are rotated off-site. Each computer has 200-300GB of data on the hard drive. I therefore have 2 Retrospect catalog files (one for each backup set), each about 2.7 GB in size, and growing. In addition, I use Time Machine on each computer to keep local backups. And I also clone the hard drives periodically. My problem is that I was looking around my Time Machine backup disk (using a hacked version of Grand Perspective, if anyone's interested) & noticed that TM has backed up multiple copies of the Retrospect catalog files. That's good, because ever time a Retrospect backup is performed, the catalog file is changed. However, what's bad about this is that the whole 2.7GB catalog file is backed up after each Retrospect backup. The old copies are retained as per TM protocol, so at the moment a good chunk of my TM backup drive is taken up with multiple versions of these catalog files. See the attached screenshot where each large brown rectangle is a copy of a catalog file. I don't imagine that 2.7GB worth of catalog file is modified each time Retrospect backs up, so why not store the catalog file as a container of smaller components instead? That way, after a backup, only the components containing the parts of the catalog file which have changed will need to be backed up by TM. I was thinking this could maybe be done using a catalog package containing multiple smaller files. Or perhaps using a similar concept to a sparse disk image. I'm no programmer, so maybe I'm talking rubbish here. Like I said earlier... just a suggestion
  2. Thanks. I'll give CCC a go.
  3. iOS 4 & the app?

    Mac OS X doesn't seem to allow port-specific firewall control using the System Preferences. However, nothing really changed on my Mac. It was the switch to iOS 4 I think that made the difference. It was working with iPhone OS 3.x. (And, side note, why can't I subscribe to this topic? In fact, why can't I subscribe to any topic?)
  4. Hi, I have a proactive backup script set to backup my computers onto a couple of disk media sets (on external hard drives) which are rotated off-site. I'm wanting to move these to new, more portable disks for ease of use. I'd also like to retain my backup history, so would prefer not to just start with a fresh media set on the new drives. The Retrospect 8 manual has a section on "Creating a Copy Media Set Script". Is this what I want to do? Can I just point Retrospect at the new copy & it will continue as if it were the old drive? There's another section in the manual on "Creating a Copy Backup Script". I'm unclear on this, but I don't think this is right. Correct? There's another section in the manual on "Moving Retrospect", but it seems to talk more about moving the backup computer rather than what I would like to do. Alternatively, there is this thread from the Windows section of this forum: http://forums.dantz.com/showtopic.php?tid/33361/, but RM's reply talks about a "Backup Set Transfer" which I can't find anywhere. Confused & dazed, Thanks!
  5. iOS 4 & the app?

    No, I'm using 8.1. Can't get it to work.
  6. iOS 4 & the app?

    Hi, is anyone able to get the Retrospect app working in iOS 4 on an iPhone 3gs? Mine no longer connects to the console. Deleting the data & starting again makes no difference.
  7. Hi, I use Retrospect to backup two Macs to a series of external hard drives which are rotated off-site. (Retrospect 8.1 build 626, Mac OS 10.6.3, Macbook Pros.) I have a Retrospect Proactive Backup script with a Disk Media Set on each of the external backup drives. Whenever I remember, I plug in whichever external drive is in the house & let Retrospect do its thing overnight, then take the drive off-site to swap the next day. I do this every several days, according to no particular schedule, whenever I remember. Now, my question is this. When neither of the external backup drives is plugged in, why does Retrospect still scan the source drives for changes & prepare itself as if to backup, right up to the point where it's ready to write to the (target external drive) Media Set? Then it stops & thinks, hey, there's nothing to write to, I guess I'll stop now. Why waste CPU cycles & slow my computer down with this futile activity? Why not look for the target Media Set first? Likewise, if external drive B (Disk Media Set is plugged in, why does Retrospect scan the source drive & prepare to backup to external drive A (Disk Media Set A), then realise its error, then start again, scanning & preparing to backup to external drive B? Once again, what's wrong with checking for the target drive/Media Set first?
  8. I tried something like this, only having the script run between midnight & 6am. The activity window says it's waiting for the right script time through the whole night & doesn't make an attempt to back up at all. Terrible. I now have the script running continuously, but only connect the backup drive when I finish work for the night.
  9. Agree with the OP. Worked in Retrospect 6, not in Retrospect 8. Wastes time, but seems to figure it out eventually. The reason not to have multiple sets for me is to back up to whichever backup drive happens to be available at any one time. I might forget to rotate & it will still work to whatever it can find.
  10. My understanding is that Proactive Backup Scripts are equivalent to Backup Server Scripts in Retrospect 6. Can anyone confirm this? Is this is true, then this is the way to go. I have this set up at the moment, but haven't brought my 2nd drive back onsite to try it out properly yet. (It worked like this in Retrospect 6 well.)
  11. Thanks. Tried the console thing, if you mean quitting it then restarting. Also tried restarting both involved machines. In the end, I gave the client computer a fixed IP address via a DHCP reserved table & am connecting to it using this. However, if the client computer connects via Ethernet rather than Airport to the network, it gets a different DHCP-allocated IP address & can't be found. Of course, the alternative is to ignore DHCP & set the client computer up with a manually-allocated IP address, but this requires the user to set the computer location manually everytime she enters or leaves this particular network... Quite frankly, it's not going to happen & I'm going to keep getting calls asking why the computer can't connect to one network or another.
  12. Sorry, I was too vague. By "target drive", I meant "a drive where the backup is destined to be backed up onto". So, the internal HD might be a source drive for the backup. And an external HD might be a target drive. Unfortunately, in Retrospect Speak, both these drives are called Sources. When I said "not available", what I meant was that the external drive wasn't physically plugged into the computer. P.S. I used Activity Monitor to Force Quit the RetroEngine. The fan slowed down, but when I visited the Retrospect system preference, I was unable to Start the Engine. Clicking the Start button asked for the admin password, but remained in the "Start" state, indicating that the Engine wasn't running. This was fixed using the "sudo launchctl unload /Library/LaunchDaemons/com.retrospect.launchd.retroengine.plist" documented in another thread.
  13. I returned to my computer to find the fan at high speed. Activity monitor shows the RetroEngine running at 120%. A screenshot is attached. Strange, none of the target drives are available. I fired up Retrospect Console. Strange. Activities is blank, none of the local sources are visible, only one of the clients is visible, the scripts page is empty. A screenshot is attached. I quit Retrospect Console & started it up again. Seemed fine for several seconds, with all tabs filled appropriately, but the Engine still very active. Then, the Console hanged & is still doing so, with the Activities tab almost emptied out again. What's going on here?
  14. Hi, I can't seem to find the answer to this anywhere. I have a Proactive backup script with a few sources. A networked client computer failed. Retrospect waits for the 30 minute period to elapse before trying again. How do I force Retrospect to backup that computer again now? I realise I could go to the other computer & use the Client program, but I want to do this from the Retrospect Console. I could also change the Script Options, but I don't want to change the script, just force this backup once. Thanks
×