Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Mocker

  • Rank
    Occasional forum poster
  1. Also, maybe if you have access to the machines when these failures happen, check out if you can telnet into the machine that retro is bombing out on and see if it allows you to connect. is it on specific machines? random machines? random times of the day/backup days? Any software firewalls?
  2. Retrospect can do it but not at the same time, at least not with the MAC version. With the windows version you can have multiple execution units running to different backups sets which allows you to do multiple jobs at the same time. The Mac version of Retrospect will only allow you to run one job at a time, whether its a restore, backup, recatalog, etc...
  3. Hello bma, I would try deleting the "device" files created in the MacHD:Library:Preferences:Retrospect folder and relaunch Retrospect again. These "device" files get created after you try to custom configure a drive and get used by default by Retrospect if it sees those files there. From what I can see, this drive was supported back in the RDU version though theres a UJ-857D one for the (I'm assuming for "dual layer" support for the dual layer version of the drive). If that doesnt help, Backup to an external hard drive =P I am not too fond of the optical media - they get scratched easily, etc... (just a suggestion )
  4. Try following the instructions on this article and dont recheck the options it tells you to disable: http://kb.dantz.com/article.asp?article=5441&p=2 Keep in mind - by doing so, Scheduled backups are not going to run Good Luck!
  5. Well... you can delete individual Snapshots... How many Snapshots do you have in that backup set? If the file that you want to delete only lives in one Snapshot then you can delete the snapshot. Run another backup so Retrospect grabs the other files that were in the deleted Snapshot. Keep in mind this would not work in CD-R or DVD-R media or WORM tapes since these are "Write-Once" types of media. Good Luck!
  6. It seems to be the History date in the Client log that it goes by. So to answer your question, it resets after the client has been "touched" by the Backup server. Everytime Retrospect tries to access the client for backups, it will update the History log in the client. So even if the job didnt complete, there would still be an entry in the History log for the Client. Hope that answers your question
  7. Looks like that drive isnt supproted yet: http://www.emcinsignia.com/supportupdates/technical/retrospect/search/?q=DW-D150A Theres not real troubleshooting that can be done with unsupported drives. Which drive did you use to write the existing backup set that you have and would you be able to use it with your current setup?
  8. Looks like no support for the UJ-85J yet: http://www.emcinsignia.com/supportupdates/technical/retrospect/search/?q=UJ-85J Best bet is to get on the mailing list for RDU's Trying to custom configure unsupported drives in Retrospect can be annoying - no real troubleshooting for those... it either works or it doesnt Hard drives as backup media FTW! Good Luck!
  9. I am not sure on the Mac side but on the windows side it changes the Modification date and time on the files when changing time zones - not sure if it would be the same thing as daylight savings... Anyways, try small and simple test: Setup a folder on your Client (or use an existing one) define it as a subvolume and back it up. Then, go to the Immediate section again, Backup - make sure the folder that you just backed up is still the Source and the Destination is also the same - then hit Preview. Retrospect at that point should scan that folder to match the files to the backup set. If the files are highlighted in blue, that means that Retrospect will want to backup the files again. If the files have diamonds next to them, that means that Retrospect does not need to backup the file again because it already exists in the backup set. If you still notice that Retrospect is trying to backup the files again, take a look at the attributes of the file. Retrospect will match files by Modified date/time, file size, Creation date/time, etc. Compare the file attributes in the backup set with the actual files on the Windows Client. Maybe Retrospect isn't seeing the File information properly? Also, check the Operations Log in Retrospect to see if this started happening at a specific date and maybe give you more info to go by. Good Luck!