Jump to content

abg

Members
  • Posts

    18
  • Joined

  • Last visited

abg's Achievements

Newbie

Newbie (1/14)

  • Conversation Starter Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. Hi, Sorry for asking a question that I'm certain has come up previously but my searching didn't find the answer(s) I was looking for. I finally gave in and upgraded my OS from 10.14 to 10.15 in order to stay current with security updates. I started my first backup since the upgrade yesterday and found that I didn't get a backup of my hard drive because the Source "Macintosh HD" now has 2 instances and both were unchecked. I selected what I thought was the newer instance and re-ran the script and it's now backing up the entire disk, rather than just the incremental changes. Looks like I'll have to recycle this backup and start fresh. Is there any documentation on how best to deal with the 10.14->10.15 changes in Retrospect? Is it any more straightforward in V18? In a related question, is there a simple way to refresh the list of Sources that will remove those no longer available? Thanks for any help, ABG
  2. I recently upgraded from V10.5 to V11.0.0 (194). I'm running on an imac using OS X 10.6.8. My console log shows a tremendous number of messages pertaining to the Client: 3/25/14 5:07:33 PM com.apple.launchd.peruser.501[197] (com.retrospect.clientapp[21774]) Exited with exit code: 1 3/25/14 5:07:33 PM com.apple.launchd.peruser.501[197] (com.retrospect.clientapp) Throttling respawn: Will start in 10 seconds 3/25/14 5:07:41 PM com.apple.launchd[1] (com.retrospect.retroclient[21777]) posix_spawn("/Library/PreferencePanes/Retrospect Client.prefPane/Contents/MacOS/retroclient", ...): No such file or directory I tried to follow the upgrade instructions as closely as possible during the upgrade but clearly, something didn't go right. The Retrospect Backup Engine in the System Preferences shows V11.0.0 (194). Other than completely uninstalling and starting over, is there a straightforward way to address this? My searching of earlier posts (V8) talked about using an uninstaller for the client which I don't find in the V11.0 download. There's an uninstaller that will take out everything but the config and media set files, but that seems a little drastic. Still, that'll be my next step if there's no other way. Thanks in advance, Alan Glendinning
  3. I'm glad I found this thread as it helped me with an issue where I had a win7 "Backup & Restore" system image/backup and a Retro8 backup (made from the mac side) of my Bootcamp partition, with the Retro8 being the more recent. I was trying to decide if it was worth the risk of trying a complete restore from the Retro8 backup. Instead, I went with the older system image and I'll restore the more recent user files from the Retro8 backup to get a better handle on what else was changed in between backups (I don't use the Bootcamp partition very much so I don't expect very many differences). For what it's worth, I think this aspect of backing up Bootcamp partitions from the mac side (and its limitations) is worth a mention in the documentation. Thanks, Alan
  4. Ok. It wasn't clear to me whether you had backed up "most" top-level directories, perhaps missing some standard Mac OS X stuff, relying on being able to restore those from the install DVD, or whether you had gotten them all. In that case, all you would have needed to do for the "Step (1)" that I discussed would be to create the top-level directories (so that you could designate them as "subvolume" destinations for the restore. Even so, I think it might have been (or might be) safer and easier to do the install disk and updates to ensure that some special stuff (/dev nodes, volume partitioning, etc.) got done correctly. Yes, I think that is the expected behavior. To Retrospect's "chroot" behavior that is used to do subvolume restore, it can only work on a single volume restore at a time, hence the selection of a single source for restore (and destination). It many also have something to do with unix's prohibition (because of underlying design) of cross-volume hard links (but not cross-volume symbolic links, which are simply the text of the pathname). Again, see above. Short answer, that's the way it is. Long answer, it has to do with Unix chroot behavior. You might want to do a "man chroot" in Terminal to read the man page. Basically, the chroot capability was set up to permit web access for a contained filesytem (as if the filesystem really started at a lower level "root") without permitting any way to go out of that box. Needed for things like FTP, etc., so that malicious hackers couldn't scribble all over other areas of the disk, but Retrospect takes advantage of this to provide "subvolume" behavior. Well, the middle of restore crisis is not the time to learn / test this behavior. Really, it should be done as part of the installation / qualification / testing of any backup program, because that's when you discover the shortcomings of a backup program. Yes, there are several ways. One way, because you really don't seem to be going back that far, would be to restore the files in those sessions (not snapshots) from that date forward. That's the approach that would be used with other backup programs, basically restoring the incrementals forward from a given date. Or, you could craft a Selector (in Retrospect 6 language) to select all files modified from a given date forward. Note that such a process would mean that you will have to go through all of your subvolume sources, separately targeting all of your subvolume destinations. Good luck. I still think that the procedure I outlined is the most foolproof. Russ Thanks again for your help. Rather than create a selector I may just go ahead and restore my user directory to a new location (without Bootcamp I now have sufficient room) and just use the UNIX find command to delete everything older than 26-Feb in the restored directory. That, at least to me, seems like a more straightforward task than thoroughly understanding source groups, sub-volumes and selectors :tongue2:
  5. I think you did what was needed when you did your backup, considering the issues you were facing at the time. My saga in trying to get a catalog file created w/o running out of memory is detailed here: http://forums.dantz.com/showtopic.php?tid/26542/ I created a separate subvolume for each top-level directory on my hard drive, and then collected those subvolumes into a Source Group which is what gets backed up. Here's the mindset that you need, followed by what I would suggest, considering that it's not clear exactly what you mean by "basically": There are three things that need to happen, assuming that you backed up the subvolumes correctly: (1) you need to get the complete and correct root structure for your drive ABOVE all the subvolumes, including any stuff that might have been missed in the "basically" part; This is something that I probably messed up on, but I'm not sure it affects the behavior I'm seeing. When I launch Retrospect and click on Restore, followed by 'restore entire disk', I get a window to select a Source Snapshot for restore. This new window has two sections; the top one has backsets. Once I click on the one I want, it prompts me for the catalog file password and then the lower window is populated with the "current snapshots" in my backup source. These are the sub-volumes in my backup set, some 17 of them. Only one of these can be clicked on at a time. At the moment I'm running off a restore from Time Machine, which predates my latest Retrospect backup by some 4 days. I'm happy enough to continue from this state, but I'd like to understand just what I did wrong. It's starting to sound like my mistake was at the very beginning of the backup source group/subvolume creation (omitting some important files) but I'm still confused why Retrospect won't restore more than 1 subvolume during the "entire disk restore". Yes, I was running off a clone of my hard drive (I actually use 4 different backup strategies, but Retrospect 6.1 is the one I use on a daily basis) so it was pretty straightforward to play around and see which method was going to work best for a complete disk restore. So far, Time Machine is the simplest. While I was very comfortable using Retrospect 6.1 for various backups, and it had saved my bacon numerous time on a mac and on windows (V6.5), it occurs to me that I had never actually attempted a complete disk restore with 6.1 until today. Again, thanks so much for attempting to set me straight. One last question: is there a simple way to restore files from a backup set that were added to it after a certain date? That would certainly simplify my remaining task, restoring the data files from the 4 days they were only being backed up in Retrospect 6.1 Thanks again, ABG
  6. Please excuse any incorrect version numbers or terminology. I'm presently restoring my hard drive from a Time Machine backup and don't have immediate access to my files. I managed to hose my hard drive while attempting a win7 Bootcamp update. After erasing the drive, I restarted the machine from another disk with OSX on it (regular machine runs 10.5.8 and Retrospect 6.1.138, or whatever version precedes V8). While I have a very recent Time Machine backup, my most recent backup (by about 4 days) is my trusty Retrospect backup. I've always found it very straightforward to dig files or directories out of it. This time, however, I wanted to restore the entire disk, and selected that option. Let me first explain that I discovered a couple of years ago that I couldn't simply backup all my data by selecting the hard drive; there were too many files and I needed to create subvolumes and to then back up a collection of those. Arcane, but it appears to work (subvolumes were basically created for all the top-level directories on my hard drive). I connected my external drive with the backup, selected the catalog file, which showed the snapshot I wanted (early on 2-Mar). There were subvolumes listed in a window BELOW the snapshot, but I was unable to select more than one at a time. When I tried to restore "the entire disk", I basically could only get one subvolume restored at a time. Not at all what I had in mind, and since each "restore entire disk" ERASES the disk first it makes it impossible to restore all my data in a single shot. Is there something obvious that I missed in the restore process? In a related question, since I'm just planning to augment my Time Machine backup with the individual files/directories in my Retrospect backup added in the 4 days in-between, is there a straightforward way to have Retrospect select files on the basis of "date added to backup set"? Thanks in advance, Alan
  7. I'll try to keep this short, but I'm at a loss to explain the tremendous performance increase I saw doing (almost) identical backups only 4 days apart. For one of my backup schemes I use an external USB2 drive with several partitions. Last week the partition for my Intel imac was almost full so I set the backup to recycle and let it start Friday evening. Took ~40 hr to backup roughly 210 Gbytes of data. This has been typical for the year I've been backing up this particular machine. Yesterday, I decided that I wasn't satisfied with the way I had the drive partitions sized, so I adjusted those (knowingly wiping out my backup in the process). I kicked off another recycled backup process and figured I'd have it all wrapped up by tomorrow. Surprise, it completed the task in only 21 hrs. There were two changes of note between the two backups: 1. Upgraded the OS from 10.5.6 to 10.5.7 2. Deleted some 14 Gbytes of VIDEO_TS data from my user directory. Looking at the performance statistics, the subvolume containing the user directories (I backup 1 group containing 17 subvolumes; long story) on the first go-around I got the following performance: copy 158.1 Mbyte/min compare 249.2 Mbyte/min On the latest backup, I got the following: copy 343.5 Mbyte/min compare 569.6 Mbyte/min The backup appears to really have all the data it's supposed to, so somehow I'm now getting twice the throughput. Does the type of file being backed up really make that much of a difference? Obviously I'm delighted to see things speed up so much (even if it's only temporary) but I'm really curious to know what happened. Particulars: Retrospect V6.1.230 intel imac OSX 10.5.6 then 10.5.7 Backup type: File Backup Set Options: DES encryption USB2 external drive with 4 partitions (1 HFS ext./jour., 3 FAT32)
  8. D'oh! Answering my own question, clicking on the "Activities" icon displayed just what I was looking for. Sorry for the lame question, ABG
  9. I ran a backup of my system overnight onto an external hard drive. This is the first time I've used V8 to try to backup the entire drive. This morning, the external drive had the right amount of data (in 600 MB files) to represent the source, but the Log file still only had an entry saying that the backup had been launched the night before. After an hour of not sensing any disk activity, I figured that the backup was complete and quit Retrospect (+ stopped the Engine). I then opened the Log file with TextEdit and found that my backup was only about 1/4 of the way through the verification process. My question is, how can one tell how far along the Backup process has made it? In the earlier versions there was that very nice activity window that showed in excruciating detail which file was being backed up/compared to that made it pretty easy to guestimate when things would wrap up. Did I miss something in the Getting Started Guide? System details: Intel imac, 10.5.6, V8.0.608.1 Thanks in advance, Alan Glendinning P.S. The first phase of the backup, copying some 220 GB via FW800 only took about 8 hrs; I find that very encouraging!
  10. Woohoo! Worked perfectly. Two very minor issues I'm curious about: 1. The "Restore Windows System State" option never presented itself to be selected in any step of the process nor any other place I could find. I was restoring from an external hard drive; does the option not apply in that case? 2. I was slightly surprised by the "dual restart" nature of finishing off the restore, which wasn't mentioned in the User's Guide. Hadn't expected that. Version: 6.5.373 Thanks for the assistance but I hope I never need to repeat the procedure! ABG
  11. Thanks for the quick reply. Wish me luck :tongue2: , Alan
  12. I'm in the process of restoring the windows partition on my iMac (Boot Camp installation) using a complete backup of all files made using V6.5. Basically, the partition became non-bootable with consistent blue screens (aside: be VERY afraid if you try to install Parallels software and use your Boot Camp partition, but I digress) so I recreated the partition and reinstalled WinXP SP2. I'm now at a point where I could either just reinstall all my apps and install the user data from my backup (pretty straightforward but very time consuming) OR, and this is what I'd prefer to do, simply do a complete restore of the disk contents from my complete backup (on an external hard drive). I've read the documentation and I think my best bet is to follow the "restore from a full backup" section on p. 85 of the manual. Does anyone see any reason why this wouldn't work on my setup? I noted in a recent, similar thread the suggestion of using a "live restore" in V7.5. Does that have an analogy in V6.5? Thanks in advance, Alan
  13. Your catalog files are truly huge, the largest I'm presently working with is about 700 Mb. I was eventually able to back all my data by doing it in pieces; 824K was the largest number of files I put into any one Backup set. I guess it gets the job done, but I sure prefer the elegance of just backing up EVERYTHING with one set.
  14. My backup of user accounts, lots of data but not that many files, was able to create the catalog file successfully.
  15. More updates: I created a subvolume for my wife's account. That data backed up flawlessly in a couple of minutes and verified successfully so there's not something systemically wrong with my setup. I then tried a backup of all data except for User accounts. Not too much data (~50 Gb) but still a huge number of files (~1.3E6). It failed at the same point as the 1st backup, while trying to save the catalog file with the same -108 out of memory error. I'm now trying to backup just the User accounts which will have lots of data (~150 Gb) but only about 100K files. Is there a known limit to the number of files Retrospect can reliably backup in one Backup Set?
×
×
  • Create New...