Jump to content

shadowspawn

Members
  • Content count

    215
  • Joined

  • Last visited

Everything posted by shadowspawn

  1. Quote: One question still not answered: Is the Mac OS IN FACT scanning the drives on boot up and physically rewriting the inception dates before the drive shows up on the desktop?? No, not these days. (Assuming you are running Mac OS Extended format drives, also known as HFS+.)
  2. The interface is a little subtle, what you are actually setting is the exact times across the whole week that the backup server script will be active. When you click on a day, it is only to access the times for that day, not to immediately turn on/off the script for that day. e.g. Click on Wed. Click on Never. See what happened to the blue bar indicating the active times? This is how you turn off the script for those times/days.
  3. 1) I think there needs to be someone logged in for the Mail.app handler to work. 2) You only get email for scripted backups, so if when you are testing you run a manual backup, that will not cause an email. 3) You can test the email part directly to check that outgoing email is working, just in case. Login as the same user who will be logged in when the backup occurs. Open up the event handler in Script Editor. Copy the whole of the sendmail subroutine into a new script window, i.e. Quote: to sendMail given Subject:subj, myMessage:bodyText, recipientsList:reciplist [...] end sendMail and below it add this line with your email address: Quote: sendMail given Subject:"Test", myMessage:"message", recipientsList:"person@some.site.tld" then click run. You should have just sent an email. 4) Post again if none of this helps. I am going to be setting up the same thing as you, from scratch, in the next week or so, and will pay attention to what steps I take!
  4. It is "on purpose" since the functionality is the clients keep certain files private from the server. (Rather than the server seeing the file but choosing not to back them up, which is subtly but significantly different!)
  5. To add a little to what Amy said, each mailbox in Mail.app is a separate file. It can be very instructive to actually look at what contributed to the backup size. Open up the Contents Report and see what files actually hit the tape, and how big they were. You might just have a lot of mail in various mailboxes, but two traps are the Trash and Sent mailboxes which have accumulating more mail than you expect.
  6. A few notes: 1) The community-based forum is not an official means of contacting Dantz support, from Welcome to the Forum Knowledgeable and helpful Dantz staff do contribute enormously, but despite any impression you got from your phone call, this is "only" a community forum. (The phone people were probably just trying to make sure you knew the alternatives to paying for a support call.) 2) Shifting how/where your drive is connected should not cause problems with a file backup set. 3) Daylight savings should not cause problems with a restore. 4) Daylight savings does cause a (bogus) full backup. I think these days it is probably a deficiency in Retrospect rather than the file system. For regular backups the positive spin is that it is a good opportunity to start a new backup. For when you just want to get the changed files, it is a pain! 5) I have not tried fooling Retrospect into believing the time settings are compatible, but it sounds reasonable. Did you change the date before launching Retrospect? I am wondering if changing the date while it was running was ineffective.
  7. If you use a "subvolume" then only that part of the disk is scanned.
  8. Retrospect handles moving the catalog file fine. After you have moved the file there are two ways that you can inform Retrospect. Either try and do something with the catalog inside Retrospect and it will prompt you to find the new location, or I think double-clicking on the catalog in the new location will also inform Retrospect of the change. (If you don't want to delete the file from the incorrect location straight away, at least rename it so you don't get you or Retrospect confused about which one is the real one.)
  9. I can't speak for Windows file systems, but HFS+ stores the date in GMT, and the change to the local timezone happens at a higher level, as covered by Apple. TN1150 Dantz notes the same thing, and says the date was a problem in Mac OS 8.1 but fixed in Mac OS 8.5 TN405 I guess something broke again at a later point. :-)
  10. There is an example AppleScript which has all the source commented out in: Retrospect 6.0/AppleScript Utilities/Retrospect Event Handler and there is another one close to functional in: Retrospect 6.0/AppleScript Utilities/Email Retrospect Event Handlers/Mail.App (OS X only)/Retrospect Event Handler 1) Which one did you install? 2) Did you edit the script to put in your email address? 3) Do you see the event handler launch as a separate application when Retrospect is running? The problem may lie in what you installed, or whether it got installed correctly, or how it is working, so just exploring the options! (I am unclear whether the supplied handler will send email if it is not left running. It is working fine for me, but on a computer dedicated to Retrospect which runs 24/7. Someone else may know, or we can explore that when we find out where things are going wrong for you!)
  11. The second red cube?? It does sound like you have two different versions of Retrospect auto-launching, which is not a normal situation. (e.g. I have three copies of Retrospect installed, but only one auto-launches.) If you can actually see two copies of Retrospect in the dock at once, control-click on them and use Show Finder to see where on your disk they are. Two further pieces of information from your puzzle: 1) Did you install Retrospect in two different languages? Or run an updater for one language over the install of a different language? 2) The tricky part is how you got two to launch. I wonder if you have more than one copy of the background launcher. Try pasting this into Terminal and posting the results. ps -auxwww | grep Retro
  12. Unfortunately I think many of the Special Folder selectors only apply to Mac OS 9.
  13. Amy's post from the knowledge base has lots of good info. Two key points for your question: 1) If the Selector window shows the "and" you used in your description, then you are excluding files which end with .mpr and at the same time have file type MP3. This may not be what you were intending. 2) You can test your selector from within the Selector window, use Check Selector from the Selector menu. This is a great feature, and can be very educational! However, it can be intimidating wading through the results of a test of a complex selector on a whole volume, so remember you can use a Subvolume to test against a smaller set of files.
  14. Short version: your archive may be unreadable! Long version What is your tape device? How is it connected? If via SCSI, what type of SCSI adaptor? Are you seeing these errors when you perform an explicit Verify? On the original archives or on the new archives? It would be useful to copy some of the error messages from the log, especially some errors showing the "same errors on the same files" as this sounds odd.
  15. I don't recognise the particular error, so a couple of general suggestions. Sometimes a problem with a client is because the hard disk on the client has problems, so it is important to run whatever disk tools you have available (whether that is Disk Utility, or whatever). Hopefully however the problem is just one file or folder. You can define some Subvolumes on the problem client and try backing those up one by one, if one fails and all the others work then the problem lies within that subvolume. A (somewhat tedious but efficient) process of elimination will let you narrow down the problem area.
  16. The file selection criteria condition has access to the full path. You can choose whether to match an absolute or partial path based on how you write the condition. e.g. enclosing folder path name starts with /Ten/Applications/ file path name contains /Special/ (Natew: the Mac version does support path matching, there is a popup as to whether you are matching the "name" or the "path name".)
  17. I don't recognise the problem, so keep your fingers crossed for the answer from someone else. Something to do to find out more, is to have a look in Console to see if any messages there give some clues. Just launch Console (from /Applications/Utilities/Console), and then launch Retrospect. You will see a message in Console if Retrospect is crashing, but may also see a message from some part of the system or Retrospect itself about other problems.
  18. Have you tried reinstalling Retrospect? (Retrospect runs with special permissions and if the install has been damaged, it is possible it is unable to launch correctly.)
  19. This page covers the clients: Comparison Matrix Note however that Windows 2000 Server is not listed. While the client may work fine for backing up ordinary files (it does for us!), the Macintosh Retrospect server is not able to backup the full state of the Windows 2000 Server so it is not a solution allowing a Restore of the full system.
  20. Just an additional data point: last year I tried backing up a Macintosh client running Virtual PC by treating VPC as a Windows client. I had the same user-deferred problem with the hosted client, and did not find a solution. I have not seen the problem on "real" clients. (I did not know about the zero-countdown tip from Mayoff.)
  21. It sounds like the client software is not auto-starting. 1) Is the client still in the default location? The startup script has the location explicitly in the script. Try executing this in Terminal and post results: ls -al /Applications/Retrospect\ Client/ 2) Is the startup script there at all? Try executing this in Terminal and post results: ls -al /Library/StartupItems/RetroClient/ Quote: We have also ran into a problem where sometimes the client has that the drive is in use by root, and just hangs there. We have to turn off the client then turn it back on and do another backup. I have seen that happen after the server has a problem (like crashing or power failure), the client thinks it is still in use. It should not happen normally.
  22. The message is not from Retrospect, and does not mention Retrospect, is there some reason you are posting this message in a Retrospect forum? The message pretty clearly is from Norton Utilities. Since Norton Utilities includes low level utilities that can be seriously affected by changes to the operating system, it appears to include some checks to allow it to warn you that it is getting out of date with respect to the operating system. Your choices include downgrade the operating system, update Norton Utilities, uninstall Norton Utilities, reposting this query somewhere more appropriate, hoping someone here knows more, etc
  23. The CD-W216E has not been tested by Dantz on Mac OS according to the Storage Device Compatibility web pages, but there is an issue noted for Windows that might be relevant, on Windows you should use CD-R media media with this device. Mac OS X provides very different internal support for hardware devices, so there is no guarantee that something which works on Mac OS 9 will also work on Mac OS X.
  24. 1) What have you told Retrospect to backup? i.e. Are you running a manual back or a script? If a manual backup, what does it say beside "Selecting" in the Immediate Backup window? It it uses a Selector, what does the selector have in it? When you tell Retrospect to backup everything, it usually does a pretty good job! However since often it is convenient to back up less, there are lots of ways of restricting what does get backed up. The most likely answer is that you have unintentionally excluded some "good" files from the backup. 2) What did you tell Retrospect to restore? i.e. did you do a Search, or a Restore?
  25. While Retrospect is not a very good tool to use for synchronising, it is a great tool for backups. It is quite sensible to (say) backup both your desktop and laptop to your firewire drive before you even start trying to synchronise. Then if anything goes wrong with either computer, or your attempt to synchronise goes horribly wrong, you have a backup. The two basic ways of storing the backup are in Finder readable format (a Retrospect duplicate) or in a proprietary format (backup set). The advantage of the backup set is that you can keep backing up to the same backup set, only the new files get added in, and the old files are also retained until you choose to start over. (So if you find a file has got corrupted some time ago, you can still hopefully get back earlier good versions.)
×