Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. for example answering my ticket... last update 4 days ago and still waiting.... (ticket opened 14 days ago).... Thank you very much for your comments David.
  3. DavidHertzberg

    Several Issues with mac Clients

    For those who were wondering what post Pesetus was responding to, it was one of mine that it turns out Big Brother has deleted. The horrifying content 🙄 of that post which B.B., otherwise known as the head of Retrospect Tech Support, evidently objected to was my merely having repeated what another administrator said about European Retrospect Tech Support in the first paragraph of this post in another thread nearly two years ago. IIRC I advised Pesetus to contact U.S. Tech Support, which evidently he/she has done. So Big Brother is indeed watching you on these Forums, or at least is watching me. I could suggest better uses of his time.
  4. Yesterday
  5. According to support this is a bug (#8415). I'm still waiting for instructions on how to solve this...
  6. Last week
  7. jhg, Here's a SuperUser.com thread on how to kill a task at a scheduled time. Disclaimer: My only experience administrating Retrospect Windows was a Windows 95 Client on a Mac 6.1 Engine from 2001-2004. 🤣 Here's another SuperUser.com thread on how to kill a task in general from a command script.. P.S.: As I said ending the second paragraph of this post in another thread, if my prediction is correct you'll be able to leave a GUI-less Retrospect.exe running constantly—mostly using virtual memory when not executing backup or restore tasks—so your daily e-mail report will be created at 7 a.m. with no effort. P.P.S.: BTW e-mailing of the daily backup report was added to Retrospect Windows 12.5 (so you're not still running 7.5 😀)and to Retrospect Mac 14.5, but with absolutely no documentation. Even this Knowledge Base article, updated in December 2019, uses screenshots from before the Preference was added.
  8. jhg, You probably know this, but here's how and why to submit a Support Case for a feature request. However IMHO Retrospect Launcher—which you refer to by its ancient name of retrorun—is going to disappear from Retrospect Windows 17 (you're surely not really still running Retrospect Windows 7.5 as your Profile says?), as it did from Retrospect Mac 8.0 in 2009, in March or August 2020. I've discussed that prediction starting with this post in another thread. If I'm correct, there's no way your feature request will be implemented by Retrospect engineering. Later on in that thread, Nigel Smith suggested using Windows Task Scheduler—for which a basic guide can be found in this Digital Citizen article. Disclaimer: I'm a Retrospect Mac administrator, and I haven't used Windows since I chose to retire from my last job—where I was using Windows 95 for all but the last 5 months—in mid-2004. So I don't know how you would schedule a kill of Retrospect.exe after it has sent the daily backup report, say at 7:05 a.m.. Maybe someone else on the Forums has a suggestion, or maybe you'll have to research that yourself.
  9. I configured a daily email report to be sent at 7:00 AM, as shown in the attached screenshot. However, it appears that the email is sent only if the full Retrospect application is open at the requested time. I would have expected that the email would be generated by a small background process, such as retrorun.exe instead of the full app. If this it is intended that the email status requires the full app to be running, then I would like to submit a feature request that the task of sending the status email be moved to retrorun so that the main app does not have to be running.
  10. jhg

    Forum login uses HTTP, not HTTPS?

    On signing in, even though I used an HTTPS url for forums.retrospect.com, I get a security warning from Firefox saying the login will occur over HTTP, and the forum site indeed uses HTTP.

    retro7.jpg

  11. DavidHertzberg

    Stop "catchup" backups after starting Windows 10

    I briefly considered Windows Task Scheduler, but thought rbratton might not be knowledgeable enough about it—which was stupid of me since he/she is a software developer. In a prior thread NoelC wondered why the Retrospect developers hadn't included "easy integration with Windows Task Scheduler just by setting the right options in the Retrospect UI"; my answer in a post in that thread—whose first paragraph links to an article describing how to use that modern Windows facility—was that doing so would have seemed a bit premature in 2013. Maybe rbratton should write a Support Case for such a product enhancement—per this boilerplate post, for Retrospect engineering to implement assuming Retrospect Launcher will disappear in Retrospect Windows 17. If rbratton chooses to setup a Windows Task Scheduler task that launches Retrospect early Sunday or Monday mornings, he/she should simply pre-write unscheduled Retrospect Backup scripts —so that he/she can Run them in my predicted Retrospect Windows 17 R.-Mac-like GUI after having worked on a Saturday or Sunday. That would ensure that there are no Retrospect tasks to cancel later on Mondays. He/she can test this currently with run documents. Here's a Knowledge Base article on writing Retrospect script hooks, in case rbratton chooses to follow the suggestion in Nigel Smith's second paragraph. AFAICT script hooks automatically apply to all Retrospect scripts—meaning running any script while Nigel-hooked would end with a machine shutdown.
  12. Nigel Smith

    Stop "catchup" backups after starting Windows 10

    Or, since he knows the the time the script needs to run, he could use Windows Task Scheduler to launch RS when appropriate. Or even, if his BIOS supports it and he doesn't mind the security implications: set the PC to boot at a certain time and auto-login, set Windows Task Scheduler to fire up RS, use script hooks to to monitor and shut down both PCs when complete! These are computers -- we should be getting them to do things, instead of having to remember to do them ourselves! 😉
  13. DavidHertzberg

    Stop "catchup" backups after starting Windows 10

    Nigel Smith, You're correct in the immediately-above post, but to "schedule Proactive to run only for certain hours of the day" requires that the "backup server" be already running to act on that schedule. For the next few months, that can be done via the Retrospect Launcher. But, as I said in the second paragraph of the same post you quote, "Retrospect 'Inc.' AFAICT intends getting rid of Retrospect Launcher in Retrospect Windows 17". That would mean that as of March or August of 2020 rbratton's "backup server" machine would have to either be constantly running the GUI-less Retrospect Engine whenever it is booted, or rbratton would have to remember to start the Engine each midnight—a reversion from what he is going to do. I think the second alternative might be more burdensome than the only-on-most-Mondays cancellation procedure I described in the second paragraph of this post, which is applicable to regular Backup scripts. The first alternative would, of course, also work with Backup scripts individually scheduled to run only at certain hours. We'll see in a few months—but see the next two posts.
  14. Nigel Smith

    Stop "catchup" backups after starting Windows 10

    Not at all -- you can, for example, schedule Proactive to run only for certain hours of the day. So OP could set Proactive to run from 2am-6am every day, with an 20 hour interval. If the server is running during that time the server will be backed up, and it will also back up the client if that's available. No client is a "graceful fail", no server and nothing happens 😉 What you can't do with a single Proactive script is set the order in which clients should be backed up, so no good if that's important. You can't shut down the backup server, as part of the script, when it's finished. And using a schedule as above would mean you couldn't use the "Early backup" request to get a daytime backup, so you'd have to make another script for that -- you *might* be able to set a second Proactive script, running from 6am-2am, with a ridiculously large interval setting, that allows earlys, but I haven't tried that myself... Proactive is very flexible -- which is sometimes a boon, sometimes a pain -- and is always worth considering in any situation where backup routines can vary (presence of clients, volumes, target sets, etc).
  15. Earlier
  16. DavidHertzberg

    Stop "catchup" backups after starting Windows 10

    rbratton, Cheer up; even if my informed guess about Retrospect engineering plans to switch Retrospect Windows 17 to a Launcher-less Retrospect-Mac-like interface proves correct, you will have the following two options: The first option is the equivalent of your current solution. First, change your Sat.-Sun. backup scripts to both use the same execution unit (see page 272 of the Retrospect Windows 16 User's Guide), and change the scheduled time of those Sat.-Sun. scripts that backup your "backup server" machine to 5 minutes after those Sat.-Sun. scripts that backup your "client" machine. Then, on every Monday following a weekend on which you have not worked both Saturday and Sunday, boot your "backup server" machine first. Immediately, before you boot your "client" machine, start the Retrospect Engine and the Retrospect Console on your "backup server" and cancel every Backup activity awaiting execution. The Backup activity that has already started should be trying to back up your "client" machine; it will fail by itself because your "client" machine—not having yet been booted—is not yet visible on your LAN. After you have done the necessary cancellations, you can boot your "client" machine, By then no Sat.-Sun. Backup activities should be executing or awaiting execution, so you can leave the Retrospect Engine running on your "backup server" machine—where it will be using mostly virtual memory until the scheduled time for your midnight-Tuesday-morning Backups of your Monday work ( you can quit the Retrospect Console, restarting it to monitor those Tuesday-morning Backups). The second option is the equivalent of the one I said in a post above I personally would prefer. First, create scripts for Sat.-Sun. backups of your "backup server" and "client" machines, but do not schedule them. Then, on every Saturday or Sunday you work, when you have finished work simply start the Retrospect Console and Run those scripts using the appropriate Backup Set destination. When the Console shows those scripts have finished execution, you can shut down both machines. If you want, you can instead create a single two-Source script that does a Backup of both machines. I predict you'll like the new Retrospect Windows GUI after you get used to it. Based on the current Retrospect Mac 16 User's Guide, the Retrospect Windows 17.x User's Guide will be half—less than 300 pages—the length of the Retrospect Windows 16 User's Guide.
  17. rbratton

    Stop "catchup" backups after starting Windows 10

    Thanks for the info! I'll keep an eye on future Retrospect plans.
  18. DavidHertzberg

    Stop "catchup" backups after starting Windows 10

    rbratton, I had thought about what Nigel Smith says in the first paragraph of his post directly above. However I assume that you are bothered by the additional scanning time for regular backups that follow "catchup" backups, even if the backups are incremental. Moreover I'm not sure his second-paragraph suggestion of Proactive is applicable, because Proactive (which I don't use) assumes a dedicated "backup server" machine that is "always here" whenever the "client" machine is "sometimes here"—which (as Nigel Smith recognizes in his third paragraph) is not the situation described in your OP. Unfortunately your current solution will IMHO become impossible as of March or August 2020 (maybe with a month's delay if Retrospect engineering gets overwhelmed by other StorCentric-dictated enhancements). That is because, per this post in another thread (second sentence in P.P.S.), Retrospect "Inc." AFAICT intends getting rid of Retrospect Launcher in Retrospect Windows 17—as they did with retrorun (its old name) in Retrospect Mac 8.0 in early 2009. The Retrospect Mac 16 User's Guide describes no general Schedule Preferences equivalent to what is on pages 397-399 of the Retrospect Windows 16 User's Guide. Those Schedule Preferences are dependent on the Startup Preferences described on page 401, which affect the behavior of Retrospect Launcher—if the first checkbox in Startup Preferences is checked to enable Retrospect Launcher. This post is part of another thread that discusses the woes of using Retrospect Launcher in Retrospect Windows; and the post's P.S. says "And now that my [Retrospect Mac] backup script has finished running, the combination of Retrospect Engine and Retrospect Console has dropped to 250MB real memory. IMHO derek500's [Retrospect Windows] installation ought to be able to afford reserving that continuously." And in Retrospect Mac one can stop and start the GUI Console while the Engine continues to run.
  19. Nigel Smith

    Stop "catchup" backups after starting Windows 10

    Assuming incremental backups, no need to delete -- it'll just make the "proper" backup run faster because most has already been done. And consider using Proactive (unless standard scripts do something you need that Proactive doesn't), which is made for exactly this "sometimes here, sometimes not" situation. Re-reading your OP, it sounds like both computers get shut down and one is the RS server while the other is the client. Have a play with the "Look ahead time" in the general (rather than script) Schedule Preferences. I'm starting to think it's *because* you shut down the server that you are getting the "catchups" -- look ahead sees you've got something scheduled within the next 12 hours so makes sure it runs at the next opportunity (I'd assumed that you had the server running 24/7 and it was two clients you were restarting). It may be that setting "Look ahead" to 0 solves your problem, but that might require you to leave RS running on the server rather than quitting/autolaunching for the next scheduled run.
  20. DavidHertzberg

    Stop "catchup" backups after starting Windows 10

    rbratton,Page 398 of the Retrospect Windows 16 User's Guide says "Schedule lets you define a window during which scripts are allowed to execute." So the result of your experiment is exactly what I would have predicted, if I had had time to post. If you prefer to remember on most Monday mornings to delete the "catchup" backups that have been scheduled but not yet executed, that's up to you. If I were you, I'd prefer to remember on a few Sunday or Monday mornings to execute a pre-prepared run document. Different strokes for different folks.
  21. rbratton

    Stop "catchup" backups after starting Windows 10

    Here's what I did: The backup window when backups are allowed is from 00:00 to 07:00 every day. I ran manual backups on both computers which ran fine. I shut them down overnight so both scheduled nightly backups would be skipped. I restarted both computers around 9:30 AM today which is not in the allowed backup time window. Retrospect did not automatically start "catchup" backups when the computers booted which is good -- it honored my backup time window. But it did schedule "catchup" backups of both computers starting tonight at 00:00 -- the earliest allowed backup time. I think I can live with that; I'll just have to remember to delete these redundant backups (as the scheduled ones will occur a few hours later). Thanks for all the help.
  22. rbratton

    Stop "catchup" backups after starting Windows 10

    I haven't yet -- but it looks promising. I set the backup window to 00:00-07:00. For testing -- On one computer, I'll perform a manual backup tonight outside the backup window to ensure manual backups are allowed. I'll then shut it down overnight to skip the scheduled nightly backup. I'll restart tomorrow morning again outside the backup window to see if Retrospect tries to run a "catchup" backup. From the documentation, it looks like it won't -- so we might be good. I'll let you know. Thanks!
  23. Done!, thanks, i do have paid support i just hoped for more experienced users to have a tip i did not know about. Thanks again. With some luck, i will have a response here or at support and i will post the results .
  24. Nigel Smith

    Stop "catchup" backups after starting Windows 10

    Have you tried the "Options" section of your script? There's also scheduling options there, which only apply to that script (though the defaults reflect the Schedule settings in General Prefs, which might make you think otherwise...) and so would have no impact on manual backups. Set your "Start", "Wrap up" and "Stop" times to suit your working practices and required backup window and you should be good.
  25. DavidHertzberg

    Stop "catchup" backups after starting Windows 10

    rbratton, Sorry, but I read "the other runs MTWTF at 2AM" in your previous post as meaning you normally run what you call your "MTWTF" script at 2 a.m. on Monday through Friday. I now think you mean "MTWTF" as referring to the days you did the work that is backed up, not the days the script is actually run. Thus you actually run the "MTWTF" script at 2 a.m. on Tuesday through Saturday, even though it is backing up work you did Monday through Friday. Assuming that what I wrote in the paragraph above is correct, I hereby absolve you from the charge of not backing up your Friday work until the following Monday. So you are indeed professional enough to use Retrospect; you're just not always the most professional tech writer. It's good to hear you're using a version control system promptly. Making that same assumption, your "Weekend" script is actually scheduled for Sunday and Monday at 2 a.m.. But maybe your "Weekday" script is also scheduled for 2 a.m. on Monday, not just Tuesday through Saturday. If so it ran yesterday—Monday—right after the "Weekend" script ran when it was unable to run on Sunday or Monday at 2 a.m.. Or something along those lines.
  26. rbratton

    Stop "catchup" backups after starting Windows 10

    Go back and read my previous post -- my Friday work is backed up early Saturday morning. Plus ALL s/w changes are checked into a version control system offsite before I stop work.
  27. DavidHertzberg

    Stop "catchup" backups after starting Windows 10

    rbratton, You work in remote software development, but you don't normally back up work you do on Friday until the following Monday (assuming you're not working a Transylvanian schedule)? 😮 Please PM me your employer's company name, so that I can short-sell the stock. 🤣 My 7-days-a-week backups are scheduled for 3:05 a.m., but I boot my MacBook Pro "client" and then my "backup server" whenever my BPH wakes me up after that time—and let the backup run while I do my teeth. IMHO you're not professional enough to be using Retrospect; you should instead be using a Windows backup program that does near-continuous backup. That's why Retrospect doesn't have the feature you want. However, if you persist, I suggest creating one or more run documents (pages 236-238 of the Retrospect Windows 16 User's Guide). Then, if you work on a Saturday or Sunday, just use a run document to start the appropriate Backup script after you've finishing working.
  28. rbratton

    Stop "catchup" backups after starting Windows 10

    Thinking on this some more and looking at today's results, I'm not sure if this will work. The only time the backup using the Retrospect Client "fails" (i.e., it runs, but doesn't actually do any work) is when Retrospect thinks it has to run a "catchup" backup. On normal daily backups, it works fine. When doing the "catchup" backups, I'm not sure we have any control on how Retrospect orders the backups for execution nor inserting any delay between the "sacrificial" script and the "normal" script. It looks like Retrospect tries to run the "catchup" as quickly as possible. Or I could be missing something. (It happens -- haha!)
  29. rbratton

    Stop "catchup" backups after starting Windows 10

    Interesting... I setup 2 sets of scripts for each computer last Saturday. One script runs Saturday and Sunday at 2 AM; the other runs MTWTF at 2AM. I shutdown the computers around 16:00 on Saturday and restarted them around 13:41 today (Monday). Both "Weekend" scripts started at 13:43 today (using Execution units 1 and 2). The script that backs up Computer "B" using the Retrospect Client finished immediately, and then the "Weekday" script for that computer ran (using the same Execution unit) and finished immediately. The "Weekend" script for Computer "A" which runs on "A" completed around 15:00 and then the "Weekday" script started. It completed around 15:56. My assumption is that Retrospect saw that the backup scheduled for Sunday at 2AM ("Weekend" backup) was not run, so it immediately ran it. It then saw the backup for Monday at 2AM ("Weekday" backup) was also not run, so it immediately ran it after the first one finished. It did this for both computers. I think I'm a little worse off than before. What I'm really looking for is a setup option that says "If a backup is missed for any reason, just wait for the next scheduled backup." But I'm open for other suggestions. Thanks!
  1. Load more activity
×