Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by mcswgn

  1. Disks on the machine running Retrospect are in the "Local Desktop Container". If you look at the list of Source Volumes, in the Volume Selection window (say in an immediate backup or when creating/editing a Backup Server script and you click on the Sources button), you should find the "Local Desktop" at the top of the list. Select the entire container or individual disks and files will be matched and backed up just like any of the clients. This should be the default when creating a script. (I mean, by default I believe you should find the Local Desktop container and the Backup Clients container both included in a script. Although, it's been a long time since I created a brand new script, so maybe you need to add them explicitly.)
  2. There are two odd things about the way the installer is behaving on your system. The first is that some files (as you have observed) are being installed unreadable by "other". The same is not true when I install the same client versions. However, in a traditional unix world this can be affected by user settings (namely the umask). Not being experienced with how the MacOS Finder (under which the client installer runs) interacts with the traditional unix side, I don't know whether something like this could actually be a factor, but it would explain why you might see something that most don't and why others at your institution may also see the same (since there is a good chance you have some sort of uniform way of setting up accounts). This is, of course, just grasping at straws. Certainly the installer should be designed so as to *not* be affected by individual user settings. The second strange thing is the group owner of the installed files. One of your listings shows (in part): Quote: -rwxrwx--- 1 root maser 919 3 Jun 2003 Info.plist "maser" is the admin account I reinstalled the app into. This shows that the principal group for the user "maser" is the group also called "maser". Maser may be a member of the admin group, but admin is not his principal group. When the client is installed it is installing under the principal group of the user installing it--which is normal. The end result, though, is that when any other user--besides root, even other admin users--tries to run the client they can't because "maser" is a group of one that doesn't include them. The above quoted listing shows that for the one file displayed only the user "root" or a member of the "maser" group will be able to read that file (and the client won't run if it can't read all the relevant files). Of course, this wouldn't have been an issue if there weren't "---" under the "other" permissions (which gets back to strangeness #1). However, if you are creating special admin users for the purposes of just administering machines, then you want to make sure they all have the same group as their principal (first) group to avoid these sorts of oddities.
  3. Quote: natew said: You could try chmod -R 775 on the client application. This won't work because it overwrites the SUID bit on the pitond program. A symbolic mode works, though. chmod -R o+rx /Applications/Retrospect\ Client is sufficient to allow anyone to run the client.
  4. What exactly is happening when it stops and what do you actually see? (E.g., error messages, etc) Giving a little more details will help.
  5. Dantz has said that the price for the 5.1 upgrade went up on Dec. 18 and that this is the same price that will be charged for the 6.0 upgrade. Those purchasing the 5.1 upgrade after 12/18 are entitled to the 6.0 upgrade for free. Those purchasing the 5.1 upgrade in the preceding month, 11/18-12/18, (when the price was lower) can get the upgrade to 6.0 for the difference in price. Since you purchased on 12/1, you would be entitled to upgrade to 6.0 for the difference between whatever you paid and the current price. Just call the Dantz customer service number after Monday to find out how to do it.
  6. I hope the ReadMe will prominently warn users to update clients first! Will the 5.1 application be able to "push" the 6.0 client to make that update? Will the 6.0 application be able to push the 6.0 client to older clients (in the event someone forgets) even though it can't back up the older clients?
  7. Also, make sure the installer is on the local disk, not a network disk. There was a problem with the installer being unable to properly authenticate itself when run from a network share. I don't know if later client installers fixed this, but my memory was that it looked a lot like what you are describing--client appears to install fine, but won't stay on.
  8. To quote the post by Robin Mayoff: Quote: * FileVault stores each user's home directory in an encrypted disk image file, similar to those created by Apple's Disk Copy. When a user is logged in, Retrospect will back up the contents of the user's FileVault-protected home directory (provided that either the Local Desktop container or the specific user's FileVault-protected home directory is selected in Retrospect's Source Selection window). If multiple users are logged in, Retrospect will back up all mounted FileVault home directories. and also: Quote: * In the Configure Devices window, Retrospect will show all mounted FileVault home directories as removable volumes, listing a "Content unrecognized" status. WARNING: Do not select a FileVault volume and click Erase! To do so will erase the entire contents of that user's home directory. This says that a FileVault home directory shows up as a separate volume. This volume is mounted only when the user is logged in and then this *separate* volume is backed up as long as the selector includes the mounted volume. However, the files will not show up under Users--they will show up under this other volume. Look at your desktop to see the name of your FileVault home directory and then look through the log or the snapshots for a volume of this name, not the name of your main disk. These files will be backed up in unencrypted form and you can restore individual files. However, the home directory is only available for backup when the user is logged in, so if you backup at night and you always log out completely before going home, your home directory will never get backed up. Use of the Fast User Switching should give the best of both worlds.
  9. You can restore everything on the OS X volume, but NOT when booted into OS 9!! You have one of two routes that you can take. Both require that the boot volume at the time of restore be OS X. The choices are basically to boot off a new install of OS X on the volume that has been damaged, or to boot from some other disk with OS X. If you reinstall OS X on the damaged disk after reformatting, in order to do a complete restore the version of OS X on the disk and in the backup set must be *identical*. So for example, your CD has 10.2.4. If the version in the backup set had been updated to 10.2.6, then you would need to bring the installed 10.2.4 up to exactly 10.2.6 before trying to restore the entire disk. This only applies if you are restoring the entire disk, not if you decide to restore only selected documents, etc. The other alternative, booting off another OS X disk, is not as restrictive. The versions of OS X don't need to match. If you have Retrospect 5.1, the installer CD is a bootable OS X volume and can be used for doing the restore (assuming the backup set wasn't written to CDs). In your case you also have your OS 9 disk. If there is room you could add OS X to that volume and then use that OS X volume to repair the other disk. If you boot from some other OS X disk make certain that "Ignore permissions on this disk" is *not* checked for the disk you are repairing. (The wording of the option is from memory, so this may not be exactly correct. It is found by selecting the disk, Get Info... > Ownership & Permissions.) This is very important or the newly restored OS X disk will be worthless. If you restore the entire disk you will want to think about when the damage occurred (if it can be pinned down). You would want to select a snapshot for restoring the entire disk (including system) that predates that. You could then go forward and do a second restore of, for example, your entire home directory from the most recent snapshot.
  10. FWIW, Apple pulled the 10.2.8 update yesterday (9/23/03). It is no longer available and no comment as to why. However, there are unofficial reports on www.macrumors.com of a wide variety of problems after updating for some people.
  11. You cannot do a complete restore of a disk to the currently active startup disk under OS X unless the versions of OS X before and after are exactly the same. So you could not restore a 10.2.6 system to a startup disk that is running 10.2.8. The reason is that restoring a different OS version will cause the active system files to be deleted and the system will then crash. If you have Retrospect 5.1, the installer CD is bootable so you can make that be your startup disk and then restore whatever you want to the internal disk. Likewise, if you have any other disk (e.g. a firewire disk) that you can boot from, then you can restore to the main disk.
  12. Just grasping at straws here, but how much RAM do you have installed? Have you looked at RAM usage (say with 'top' in the terminal) right after rebooting and then after a few days? It's not uncommon for unix systems to collect a large number of idle processes after they have been on for awhile, although normally this would be handled intelligently by the memory management system. I wonder whether over time you could be going more and more heavily into swap.
  13. What you are seeing is a complete listing of the disks contents. The bars on the left are a "zoomed out" version of the same file listing so you can keep track of where you are in the list. The checks are things that need to be backed up (which would be everything if you are doing a standard backup) and the diamonds indicate the files that already exists in the backup set and so don't need to be written again. Therefore, the only files that will actually be written to the backup set are those with checks that do *not* have a diamond. To change the check marks, select the item (or closed folder for the entire contents) and click Mark or Unmark in the top right corner, as appropriate. Once you are done making any changes (which would normally be nothing) just close this window and you will get to the backup dialog box that I think you are talking about. To get back to the selection window, click on the Preview button in the backup dialog box.
  14. You can't just write an image to a read only disk and get it to boot. Too many things in a default configuration expect to be able to write to the disk. (E.g., log files, swap space, etc.) It *is* possible to create bootable CDs, however. First of all, Retrospect 5.1 comes on a bootable CD, so that might take care of everything you need. If you want to create your own customized CD (I don't know if this would also work for a DVD), download BootCD. You can find it on versiontracker.com. It will create a bootable CD customized for your system (booting with an active network, which is very nice). You can add your own apps to the image before burning, but sometimes this can take a bit of trial and error. The utility gets around the need for a writable disk by creating a RAM disk on which anything that needs to be writable gets placed. This is why putting your own apps on can sometimes take trial and error. Apps frequently write to places you weren't expecting and so on the first few attempts not enough gets put on the RAM disk. Standard apps like Disk Utility work fine by just dragging them over, though. If you want to use a hard disk, like a firewire disk, then Retrospect can certainly duplicate the necessary system files to the external disk.
  15. This is one of those topics that keeps coming up. 100GB is the native capacity of the media. Whether you exceed that and by how much will depend on a couple of factors. First is the compression ratio you can achieve with your data. The media manufacturers claim a "compressed capacity" of either 200GB or 260GB for the same media! That's a compression ratio of 2x or 2.6x, but many files are already fully compressed and will be unable to be compressed at all. For example, .mp3, .mpg, .jpg files all use compression as part of their file structure. Attempting to further compress files of this type will actually increase their size slightly. Binary system files also tend to have very low compression ratios. However, I've seen compression ratios as high as 10x for ASCII postscript files. The typical Word document will be somewhere in between. So the overall compression ratio you actually see is not going to be the mythical ratio claimed by the manufacturer and will be highly dependent on your particular mix of files. Second, capacity of a tape drive is only optimal when data is streaming continuously to the drive. An AIT-3 drive takes data at a phenomenal rate. LaCie quotes transfer rates of I think 12MB/sec. That's 720MB/min. In order to optimize capacity you would need an *after* compression supply of data at this rate. If your mix of files is such that they are actually capable of being compressed at a rate of 2x, you would need a continuous supply of data at at a rate of 2x720 = 1440MB/min. If you don't meet that rate, then the drive buffers keeping running out of data and every time they do the drive will start writing nulls to the tape until more data arrives. This really messes with tape capacity! They do this because it is very bad for a tape to keep starting, stopping, re-seeking, starting again (called "polishing the heads"). It is much better to waste some tape capacity than to wear out both the media and drive prematurely.
  16. You can do it by hand if you are doing an immediate backup. Click the Preview button from the Backup window. From there you can select/deselect files and folders to be backed up. It is easier, though, to create a selector from the Special tab -> Selectors. Write the selector to Exclude each of the enclosing folders you don't want. Then in the backup window click on the Selecting button and choose the selector you just created. That way you can use the same selector over and over again and you also can use it for unattended backups.
  17. The Duplicate operation will allow you to duplicate a volume on one client to a volume on another client. However, there is a Note in the manual that states you cannot duplicate a subvolume on a client to another subvolume on the same client. Not having tried it before, I don't know how broadly to interpret this statement. Taken literally, it would not exclude what you want to do. However, I cannot image how it could be OK to duplicate drive C: to (say) drive D:, when it would not be OK to duplicate a folder (subvolume) on C: to a folder on D:. I suggest you try it :-) What I wouldn't recommend is trying to duplicate to the other disk mounted as a remote share on the MacOS X machine. That sounds like a recipe for disaster.
  18. A newer Retrospect application is supposed to work with previous versions of the client (with one exception mentioned below), but it is recommended that the clients be upgraded. You should definitely upgrade the application first and then you can work on the clients "at your leisure". Be aware, however, that 5.0 won't use appletalk for backing up mac clients. If you currently have any clients that are using appletalk, you should look into whether they are capable of running the newer clients that work over IP.
  19. The are additional file properties under unix that don't exist under OS 9. Consequently, the files don't match as the same. This is known behavior. Take this opportunity to archive your old backup set and start a new one.
  20. If you did a "Save as..." when you saved your customized Retrospect Event Handler, then you needed to select both the "Stay open" and "Never show startup screen" options in the Save dialog box. Your description (the script starting up and shutting down for each event) makes it sound like you didn't do that. Do a "Save as" again and this time make sure those two boxes are checked.
  21. Yes, that is unfortunately the choice you are left with when using the stock event handler. This thread got me thinking again about how to best modify the Retrospect Event Handler to get it to behave in a more reasonable way. Below is a first stab. I did this for the "legacy" handler for Eudora because that is what I use. I haven't looked at the others at all. I presume, though, that they just differ in how they talk to the mail program. If so, then these modifications should work just as well for them. All these changes do is add another counter that lets the timer be reset more than once. Otherwise, it works just like the old handler. When there is a media request Retrospect starts the count-down timer for the amount of time set in the Retrospect preferences. When that times out the first time an email is sent warning that media is required. The timer is then reset. The next kMaxTimerResets number of times the timer runs out it will be reset but no additional email is sent. If there is no media by this number of resets, then the current operation aborts. For example, if inside Retrospect you set the media request timeout to 10 min and inside the event handler you set kMaxTimerResets to 12, then when media is required Retrospect will wait 10 min, send an email, wait 12*10 min = 2 hr, then abort. Note that when Retrospect aborts the log will indicate it waited only 10 min for the media, but this is not correct. I've tested this a little bit, but didn't see an obvious way to artificially induce a media request, so the testing has not been extensive. "Try it at your own risk" as the saying goes. Modifications to the standard Retrospect Event Handler for Eudora Light (in addition to the customization required to get the std handler to work): 1. At the beginning with all of the other "properties" and just *before* the line: -- Nothing below this line needs to be edited. add the lines (changing the 12 to whatever you prefer): Code: -- Set this property to the number of times to reset a media timeout before aborting property kMaxTimerResets : 12 2. Add the variable gResetCtr to the line defining global variables, making this line read: Code: global gBackUpReport, gVolumeErrors, gNumVolumesBackedup, gStorageSet, gMediaRequestSent, gBackUpServerRunning, gTimeKeeper, gResetCtr (this should be one line unless you break it and start the second with "global ..." again) 3. Rewrite the "on MediaRequestTimedOut" handler to look as follows. (The changes/additions are in lines 2, 7-8, 10, 12-14, and 19 below. Be careful of line breaks as I don't know how this will appear in a browser window.): Code: on mediaRequestTimedOut given numberOfSecondsWaited:theTimeOut set theTimeOut to secondsConverter(theTimeOut * kMaxTimerResets) if not gMediaRequestSent then set theMsg to "Retrospect needs a " & theRequestedMediaType & " named \"" & theRequestedMember & "\"." & return & return & ¬ "Please provide this " & theRequestedMediaType & " or other appropriate media." & return & return & ¬ "You have " & theTimeOut & "to supply Retrospect with new media or the current operation will cease." sendMail with sendNow given Subject:"Retrospect: Media Request", Message:theMsg, recipientsList:kMediaRequestGroup sendMail without sendNow given Subject:"Retrospect: Media Request", Message:theMsg, recipientsList:kMainGroup set gMediaRequestSent to true set gResetCtr to 1 return false -- reset the media request else if gResetCtr < kMaxTimerResets then set gResetCtr to gResetCtr + 1 return false -- reset the media request else set gVolumeErrors to gVolumeErrors + 1 set gBackUpReport to gBackUpReport & ¬ "•Media request timeout occurred before script could successfully finish•" & return & return return true -- already reset maximum number of times, so timeout. end if end mediaRequestTimedOut The changes to lines 7 & 8 above (switching which has the "with SendNow" and which has the "without SendNow") has nothing to do with this modification of the behavior of the script. They are correcting what I believe to be a bug in the original script.
  22. It has the name of the backup set that it goes with. If you have been doing a "file" backup, then the catalog and data may actually be one file. (It depends on how big it has gotten.)
  23. That would be true if the client had already been logged into that Retrospect server. If the conditions of the client change (e.g,. the IP number is different when the client was originally added by IP#) so that the server doesn't recognize it as the same machine, then the "old" (previously logged in) client will be visible in the list but grayed out because the server doesn't "see" it. The "new" client still has the same name, so it won't show up because it's being covered up by its "old" self. In this situation the only way out is to forget the old instance of the client so the new one becomes visible and then you can add it. However, if this happens there is a good chance the client wasn't added the right way the first time around and it would pay to look more closely at how it's done the second time. (E.g., clients with dynamic IP numbers should not be added by IP number.) This will happen any time you uninstall/reinstall, but shouldn't happen with an upgrade where you didn't uninstall first.
  24. Yeah, after posting I realized that it didn't apply in this case and debated whether I should go back and edit my post. Then I thought that if someone had to remember just one thing, it would be better to leave it this way as then they would always get it right.
  • Create New...