Jump to content

alabay

Members
  • Posts

    71
  • Joined

  • Last visited

Everything posted by alabay

  1. Years old thread, but I’d like to resume … RS 14.0.0 Mac used here. I usually backup with proactive scripts in a rolling order, A, B and C. There are different Scripts that have to be done in the morning. One of these scripts simply copies the catalogues. I’d like to be able to tell this script to be the last one in chain. Like »wait until all other scripts are done, then go«. Is this possible? To make a run script depending on done script(s) before?
  2. Well, the sad thing is that version 8 wasn’t and won’t be bugfixed. Best example of how it works the other way are the bugfixes of older VMWare Fusion releases. I would not be surprised if the bugfixes for 9 will be called 10 or 11.
  3. This Retro ist driving me insane! I recently updated to 10.7.4 and now I have the same issue. With R8, but as I read, this has not changed in R9 :-( And no, I don’t have FileVault in use, I have one old client and three local proactive sctipts. The shares have all been killed, it’s not possible to use them with RS and Lion. But still … CPU load until kill, afterwards everything works fine, on- and off-switchable. An NOWHERE, no-one can tell one nothing. What to do? Who will save us RS-victims?!
  4. This Retro ist driving me insane! I recently updated to 10.7.4 and now I have the same issue. With R8, but as I read, this has not changed in R9 :-( And no, I don’t have FileVault in use, I have one old client and three local proactive sctipts. The shares have all been killed, it’s not possible to use them with RS and Lion. But still … CPU load until kill, afterwards everything works fine, on- and off-switchable. An NOWHERE, no-one can tell one nothing. What to do? Who will save us RS-victims?!
  5. Since my update to Lion, Retrospect 8 lets my desktop machine ask and ask and ask for an unavailable share. Why can’t it be ignored? I wanted to backup sporadically and manual to this share. Looks like this doesn’t function, as sooo many does not work in this program. It’s drivin me insane! B.
  6. No, exactly they are named "Retrospect-X", X indicating A, B or C. Since the last update the recognition of an online disk is faster, it seems. Sad that it doesn't recognize it in seconds but in 10-15 minutes. But the bug, starting to collect files for a backup without having handshaked with the harddisk where all should be saved to, seems to be gone. Hopefully.
  7. As far as I know a normal "Retrospect" only runs one thread at once. Multiple is for a bigger edition, I guess Server or so. Isn't it so? I never saw more than one thread running. If a second should start at the same time, this one waits for the first one to finish. I cannot understand why it is NOT possible to start RS and – blob – everything is on my screen, the console, the activities. Independent from any missing share or client or whatever RS waits for. I'm sitting here in front of a Mac Pro and feel as if I am watching a 68k machine ... unbelievable.
  8. I have not more than three proactive scripts. Running ... only one can run at once. I have 6 GB on a Mac Pro 2x2,66. Should I forget myself and yell "crap"? :-(((
  9. Well, I have the same problem here. Like a joke. The server started at 7:46. It's now 8:07, I don't know what's going on. I don't see any activities, I cannot stop the engine, nothing ... Just telling "12.08.10 07:47:06 Retrospect[1867] Warning - unable to find template matching predicate activityType CONTAINS[cd] "Proaktiv"" Well ... killing joke ... I don't like this programm, and I don't recommend it. I'm just stuck to it. Bad.
  10. I have this the whole time. If memory serves me right, especially with iCab archives (that are zip).
  11. Well, I have to backup a research project to a SMB share via VPN connection to the university. An fitful I save my iTunes stuff to an external machine.
  12. This is not acceptable. Yes, here are 24/7 proactives working, too. But the problem seems to me unaccessible SMB and/or AFP shares. With this behaviour one cannot "qickly" backup something inducing a manual script. Because after starting the console one has to wait three to six minutes until something shows up and happens. Ehm, in times of 64-Bit OS, multithreading and CPU bolides?! My Atari was faster, decades ago.
  13. Well, I just started the RS console, let's see, how long it will take, until I can see any activities ... Machine fresh started, one external harddisc is on (for RS), no SMB-shares available. It took ... only three minutes today! Wow. I use 8.2.0 (377). Mac OS 10.6.4, Mac Pro Dual 2,66, 6 GB RAM.
  14. Well, new Beta 2 and it STIIIILLLL waits and waits. Dudes, is it SO impossible to create a software that COMES when called? It takes about six minutes until the console shows activities! On a Mac Pro. Here is another small issue from the machine's console: 30.06.10 08:54:23 Retrospect[2558] Warning - unable to find template matching predicate activityType CONTAINS[cd] "Proaktiv"
  15. But where? There is no implemented feedback button or menue entry.
  16. Well, I haven't found out a way to restore a 6'er pack from a remote backup file in 8.2 either. I gave up. No chance. Of course the catalogue file is "in" that file, nowhere else ... Oh my God!
  17. Well ... as I've written in an other topic ... RS8.2 STILL tries to connect, to connect, to connect and to connect (or: to resolve, to resolve, to resolve, to resolve ...) – but one cannot see to WHAT. It's still the problem with shares, smb, afp and so on, wich are unreachable when RS starts (when one starts the GUI, let's say so). 8.2 is even worse than 8.1 in this issue. And I'm on a Mac Pro, 10.6.4. So this machine is not really wimpy, I guess. But this hanging kills. One cannot backup quickly via a VPN tunnel to a SMB-Share. It's simply not possible. One can mount this share, one can ignore ist ... the same. RS waiiiits and waiiiits and waiiiiiiiits. LittleSnitch shows, that there is hectic action in the background. But what? Who? Why? I really don't get it!
  18. Okay ... I have to recall that! This time it was not Retrospect's fault, it seems. Due to my switch to 10.6, SMB, VPN etc. was a big hassle. It seems (?) now one has to mount the share manually, then it works. I haven't found out yet. But now there is something with netbios that hadn't been relevant before. Sorry for my snatch.
  19. Hey, I don't believe it! It's gotten WORSE! When I NOW launch a VPN connection, then RS 8.2 it waiiits and waiiits and waiiits (what the ... does it?! mdnsresponder connects, nothing more), until the VPN connection closes. 8.1 managed to connect to the share, when the script was chosen. I really start to HATE this app! :-((( I guess I'm going back to 8.1.
  20. Okay, I switched to Snow Leopard due to other issues, so I could try RS 8.2 out. Now it runs (I guess), but again, after starting, I don't see any activities. This was one of the big problems. When I start the console, I'd like to see immediately, what is happening. The engine is working, I see that from the process manager (or how it's called). I really wonder if you don't have this problem :-/ Mac Pro, 10.6.3.
  21. Ouh, I have to wait until it works with subfolders and 10.5. My desktop is still on 10.5 (does anybody here know if Logic 7 works with 10.6? :-P )
  22. I hope you will fix this strange bug with German localization, too. I mean that one with rules.
  23. RS is not better, it is completely different. TM and RS are very complementary! It is the BEST (I guess) solution to use both. RS for backups and TM for small accidents (like this one). As you see, you say eight days ago ... with TM this would be only hours ;-) You should replace Library/Application Support/Retrospect/Config80.dat.
  24. Maybe you should restore the preference file from a time machine backup? It's in /Library/Application Support/Retrospect (I guess). I think you should stop the Retrospect engine, before you restore that file. Of course, you could also try to restore from a previous RS backup, but time machine is ways easier ...
  25. Translations in work? E.g. German? Veeery curious about this piece of (non)paper. I hope there will be an update correcting some of these grand bugs we are aware.
×
×
  • Create New...