Jump to content

mbennett

Members
  • Content count

    50
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by mbennett

  1. To save time, the most efficient thing to do is simply open the Dashboard first every time. As long as a job isn't in progress you can then click the power icon in the top right corner of the Dashboard window to launch the Retrospect program itself. Unless you're making quite frequent changes to the configuration there shouldn't be a reason to have the program open. Since Retrospect runs a couple of services it usually will not start when you try to launch it directly. If you stop both services first you'll be able to launch the program directly. Try putting the Dashboard in the startup folder instead. I haven't tried that, but it should work. I fully understand that this is a PITA but this is simply the easiest path to solve your problem. Mark
  2. mbennett

    Can't cancel grooming job - please see EDIT

    I just keep cancelling until it finally takes, but I agree it's frustrating. You might need to exit the program (which should kill the working jobs) and stop the two Retrospect services. Then go back into the program. Proceed to Configure | Backup Sets, select the set in questions and edit the Properties at the Members tab for a permanent fix.
  3. mbennett

    R16 really slow backups

    I have not experienced that type of slowness with version 16. They posted a point release on the download site on March 28th, make sure you're on version 16.0.1.103 or download it. If the problem continues contact support, and let us know what happened. Don't jump ship yet, you're probably right and this is some minor config problem.
  4. mbennett

    Restrospect 16 Desktop Advantages?

    David, I had to laugh when I read your suggestion. One of the HARDEST MOUNTAINS YOU WILL EVER CLIMB is to try to convince the management of a small software company to hire a good tech writer to create and maintain their documentation. They see this as a straight money losing proposition. I've tried with different companies over the years, and if there is a convincing argument I've yet to find it. They never think the subsequent decrease in support costs and increase in customer satisfaction will make up the difference. As with most companies, Retrospect's manuals fall into the category of "informative but not instructional". They tell you what the program can do, but not how to use the program to achieve the results you want. It's better than nothing, and you've got to appreciate the volume of the docs, but it's sometimes a treasure hunt to find what you're actually looking for. It is quite expensive to do it right. If you want to see somebody who does it right, and is much bigger than Retrospect, take a look at Fortinet. Just Google "Fortinet Cookbooks" and get on the Fortinet Youtube channel. It's phenomenal. Mark
  5. mbennett

    Restrospect 16 Desktop Advantages?

    I'm sure they keep advancing the technology to address new storage options, and there are always bug fixes and performance enhancements. This is what has changed. https://www.retrospect.com/en/documentation/user_guide/win/release_notes As a dealer, I've been using 16 for a week now, and to be diplomatic about this, I think you should wait about three months and come back and ask your question again. It's still pretty green. As with most other software vendors, installing point upgrades is usually beneficial. In other words from 15.1 to 15.2 or 15.3, etc. Major version upgrades are usually a complete recompile of the entire program and unless you have a tolerance for pain or really want the bleeding edge tech, as an early adopter you may be chasing bugs for a while. From a high-level view, you should always pay the ASM, even if it hurts. I know from this forum that there are people who are still on very obsolete versions of Retrospect who don't see the point. But from an industry standpoint, the ASM fees (or whatever maintenance fees are called for other products) are an investment in supporting the company so it will be around years from now. They aren't getting rich on that money, it's what keeps them in business and allows them to push forward on technology and remain competitive so they get new sales and gain market share. End of lecture. But my advice for today is hold of on installing Version 16 for several weeks, then go for it.
  6. What David Hertzberg said. At the suggestion of Retrospect support, I now schedule multiple jobs in multiple scripts one minute apart. You can easily run dozens at a time, and the maximum number is tunable in Preferences. You can't run two jobs at the same time from the same source. You can run multiple scripts to the same destination, but for the sake of clarity and organization you will want to use unique destinations. I believe (but haven't tested this) that you could schedule two scripts to run with the same source, one minute apart. The second one will wait until the first one is complete. Try this and let us know. If you have a script and want to run it immediately, highlight it in Manage Scripts then click the third icon from the left on the toolbar, a little scripty looking sheet of paper with a lightning bolt next to it.
  7. mbennett

    How to skip Dashboard, start directly

    I think this is a good plan, but if you have a Proactive backup setup the program always appears to be running, even if nothing is happening. After the Proactive backup finishes, it will assume that it's idle for 24 hours, or until another job starts. The first window on the Dashboard always tells you if a Proactive or any other backup is actually in operation, so you can ignore the warning about starting the program most of the time. Agree that the Dashboard is slow, and launching it before you need it is the best plan if you're impatient. I'm hoping the web interface administrative tool that's coming sometime or other will make the executable program obsolete in the near future.
  8. An easy way to evaluate this is to get on the Retrospect website and run the configurator. There's no legitimate way I know of to share a single license across multiple installations of Windows. But the VM issue throws a slight wrinkle in things, and it's been a while since I looked at the price list for that. They might offer an option that would do what you want.
  9. mbennett

    Error -1103 after Windows 10 April Update

    Lucky_Phil, According to Microsoft you can't uninstall One Drive in Windows 10, but you can turn it off, disable and hide it. I'm assuming that you're not using W10, but other people might be confused by your advice. FYI, https://support.office.com/en-us/article/turn-off-disable-or-uninstall-onedrive-f32a17ce-3336-40fe-9c38-6efb09f944b0?ui=en-US&rs=en-US&ad=US If that link doesn't work, Google the subject.
  10. mbennett

    Error -1103 after Windows 10 April Update

    Just to throw out an idea after catching up with this thread, you might also want to investigate the settings in Control Panel | Sync Center in relation to One Drive, as well as anything else. Sync Center might have a bearing on this. I saw a bulletin regarding a completely unrelated application yesterday that encountered errors caused by the Sync Center. Then I read another article today discussing how One Drive syncs files and folders to the MS cloud. Now this thread to bring it full circle. I'm going to continue to watch this thread, and want to say that I really appreciate the extremely professional community discussions on this Forum. Bravo.
  11. mbennett

    Error -1103 after Windows 10 April Update

    hevanw, Sorry my suggestion didn't work out, and apologies to Scillonian for the error in the name. Please be sure to share the solution if/when you find it. This error was the bane of my existence for several weeks and I'm really unhappy to see that it might pop up and bite me again.
  12. mbennett

    Error -1103 after Windows 10 April Update

    I fought this error, sometimes frequently and sometimes sporadically, on several systems for quite some time. Filed a support case which came back with several suggestions. Of course I tried them all in what I thought was most-to-least likely to succeed. And the least likely solution, to me at first, was the winner. The solution that works every time and totally stops this error is to move the catalogs out from under the My Documents directory. I could lecture you on the stupid attempt to "virtualize" user files which Microsoft started trying to accomplish with Vista, but I'm convinced that's what creates this problem. Of course it's pointless and unnecessary, and Microsoft keeps bungling around with it. You can search this forum for instructions from a user named Scillian (I recall) to do this, but these are instructions of his I modified and have in my own KB. The catalog files can be moved to another drive or directory. I use C:\Catalogs With Windows Explorer, or your file manger of choice, copy the catalog file to its new location. In the Backup Sets dialog select the Backup Set whose catalog you want to move and click Forget.... Back in Retrospect click More... in the Backup Sets dialog then Open...in the following dialog. Navigate to the new location of the catalog file, select the file then click Open. Then you'll need to go to Manage Scripts and update all sources and/or destinations that are not defined because when you forget/move the catalogs the backup set will be deleted from scripts wherever they're found. This part can be time-consuming and error prone, and it will test your memory, so keep checking the logs for errors until you find them all. Good luck.
  13. mbennett

    New Windows user wants advice

    Retrospect 15 for Windows and Mac was released today. Download it if you enjoy being on the bleeding edge of technology. Last I heard the browser based console is to be released in May~ 2018. I wouldn't bet heavily on that, but that's the marketing projection. We'll see.
  14. Here's the original question: No there doesn't seem to be a way to do that. It isn't a problem with Retrospect, it's a problem with the way Windows services work. When you stop a service, the application that service is running also stops. But as my final word on this thread, I suggest you install 12.6.1 and test the interaction between the Dashboard and program yourself. If it doesn't do what you expect, then communicate with support and present the issue to them. Let us know what happens. If you were comfortable and happy with using the Mac as a Retrospect server and it did what you want to do, why not go back to that? The fundamental operation of the Mac OS is based on Unix, and is definitely different and probably superior to Windows. Expecting them to work in an identical manner, or even in an exactly analogous manner is probably a waste of time. Good Luck
  15. I did get time to install the 12.6.1 version of Retrospect on Monday night, and have observed a couple of things. But to the point of this thread, this version does allow you to launch the Retrospect program without seeming to break anything. When you start the Dashboard, you can click the "Launch Retrospect" link if the program doesn't start at that time. As DavidHertzberg notes, if you're within the look-forward time frame the program seems to launch automatically and you'll barely see the Dashboard screen. If you're not within that time frame, clicking the link will show the message "Waiting for Retrospect to exit" as the services stop and the program launches. To me, this behavior is perfect and resolves the real issue. Blanket recommendation is that if you've paid the ASM fees, you should upgrade to 12.6.1 ASAP.
  16. I remember reading that at the time you wrote it. I don't know if the timeline provided by Ian Dennis in sales is accurate, but I expect it is relatively so. He specifically says "Preview coming" so perhaps the web UI is still going to be in beta, may still be an optional install, may be any number of things. Maybe it will just be a Youtube video showing where they're going and we won't see a live product until 2019. There are major enhancements to both Physical and Virtual Retrospect, but that's for them to announce. I also wouldn't have any reason to believe Jeff was intentionally misleading anybody, but with software development the deadlines and project times change almost daily. I'm still running 12.5 and haven't installed 12.6 which was framed as more of a bug fix. They actually released it a few days after I upgraded from 12 to 12.5 (isn't that always the way?) When I start the Dashboard and get the UAC prompt, then click Launch Retrospect it does briefly display a message at the top of the Dashboard screen that says something along the lines of "Retrospect is exiting", which I take to mean the services are stopping. The following quote is is in the release notes for 12.6, so presumably something is different. I'll try to install 12.6 on my system in the next few days. And last, because I'm really tired and this has been a long day, you seem to be concerned about my name, which is Mark Bennett. At some point when signing up for this forum it asked me to assign a handle for myself, something I don't like to choose at any time. So I picked ProFromGrover which is a callback to the book M*A*S*H* by Richard Hooker. My mbennett login is the first part of my email address. I can't explain why the forum software mixes this up from one time to the next, but it's not really that important to me. I just know it's not me that's causing it to shift from one to the other.
  17. I'm seeing a lot of errors showing "can't read error -1017 insufficient permissions" in the log file you attached. First thing is to reboot the system that's being backed up and run chkdsk /f on that drive. That might fix the problem. The insufficient permissions error probably refers to the directory where the catalog files are located, so you should also try rebuilding all of the catalog files that are concerned in the jobs that aren't working. Also, look up that -1017 error in the knowledgebase on the Retrospect website and see what it says. I didn't do that. It's always possible that the RDX drive is worn out or a cable is bad, but they're pretty reliable. I use one every day. It's also possible the RDX cartridge itself is bad. Do you have any grooming jobs running on these sets?
  18. deredk500, I haven't been following this thread until just now, but I logged in to comment about something that is pertinent. First, as a practical matter in a Windows environment the icon on the taskbar is a myth and hasn't ever worked in my experience. Looking at page 22 of the User's Guide pretty much reveals that feature as an artifact of Windows XP and previous Windows versions. You can go to Preferences | Execution | Startup and set the flag to show the icon in the taskbar, but it will never actually appear. The UAC features introduced with Windows Vista killed that ability. Second, as a practical matter you can't do what you're asking. When the startup preferences are checked to enable the Retrospect services, those services own the program. You can launch the Dashboard and see if anything is running. If no job is running, then clicking the "Launch Retrospect" link in the top right corner of the window (label was renamed for version 12 to make it more accurate) will stop the services and open Retrospect proper. If you take that action when a job is running, killing the services will kill the job. If no jobs are running the program will launch harmlessly and all jobs will run as scheduled even though the services are stopped. If you launch the program while a job is running it will kill the job because launching it will kill the services. If you exit Retrospect while a job is running it will kill the job, because the services will be relaunched when you exit. To summarize this, don't start the Retrospect program while a job is running, and don't exit while a job is running. The Dashboard was envisioned, I believe, as a way to monitor the operation of the program while allowing it to continue running. You can't modify anything but you can see what's happening up to a point. Perhaps you could launch the program from an RDP session and set the session to lock after several minutes of inactivity and require a password to reopen the desktop. Not a great solution but it's pretty simple if it's possible. I don't use RDP a lot and I haven't attempted this. I've recently revised my own policy on using the E-Mail alerts which may help you to not feel that you need to be in the program watching everything. At one time I had every system to send an email every time Retrospect twitched it's nose, and it drove me a little crazy. In Preferences | Notification | E-Mail I now only check "Use e-mail for reporting" and "Send e-mail for failure and media requests". For each Retrospect 'server' that is running normally I get two emails every night, one when the Launcher starts and another when it stops. If no other email comes from that system I know the jobs have run successfully. Retrospect is such a stable program this happens most nights. If I get additional email from a system then I know I have a problem and I can focus on it. Real problems don't get lost in the weeds of meaningless emails. Last, I'm a dealer and I got an email from the sales department yesterday. As I hypothesized last year with DavidHertzberg they've announced that the next release of Retrospect is coming in a couple of months, and the new web-based user interface (which I predicted and was hoping for) will be released this summer. This might also be the fix you're looking for. I believe it will be, so hang in there. There is a long Youtube video about administering the Virtual Retrospect product and I think that is approximately what you can expect to see with the new interface. This simply confirms their direction. I hope this helps you. Mark
  19. mbennett

    Cannot recatalog backups

    Second the motion. Starting another thread on the same issue didn't get you any meaningful results either. I've never seen this error and your situation is too complex for people on the forum to debug. Get on the horn with support. Good luck.
  20. You can usually fix this by running chkdsk on your system. Doesn't always work, but often enough to make it a good first step.
  21. mbennett

    12.5 Pro not installing

    Are you logged in either as the user "Administrator" or at least using "run as administrator" when you launch the install program. I don't think having an account where you have administrative rights will be enough. I've installed 12.5 a couple of times without issues, and I suspect this is your problem.
  22. mbennett

    Catalog Files on a NAS

    I don't think this is a Retrospect issue because I've seen it happen with other applications in similar situations. Microsoft has somehow screwed up the ability to browse a network and look for shares. I would first focus on finding out whether the Homegroup feature is enabled in the Network control panel. Disable it and go back to conventional network sharing. There is plenty of information you can Google on this subject. Good luck.
  23. mbennett

    error -3050 (VSS reported an error)

    Run the services.msc program from the search box, or the program from Control Panel | Administrative Tools | Services. It's the same thing. Find the Volume Shadow Copy program. It is normally stopped and marked to start Manual. Try to start it and see if it will go. If it does start without error and it's not being asked to perform any jobs it will probably stop by itself, and that's normal behavior. Your backup job might run OK the next time. If VSS doesn't start or gives an error you'll need to restart your system. If your backup job fails again restart your system.
  24. mbennett

    Latest update - backup reports better on mac

    No, the reports are pretty ugly, you're not missing any settings that I know about. I get a bunch of these overnight every night, and basically I just look at the first line. If it says zero errors and zero warnings I don't continue to read the body of the email unless there's something in particular I'm wanting to monitor. I delete the email and go to the next one. The only ones worth investigating are failed jobs, and even then I usually watch for patterns of failures over one or more days. Some jobs, such as cloud backups, will cough up a warning or two but complete successfully, so I don't get too excited unless something dire seems to be happening.
  25. Also, when I've found myself in this situation in the past it's because I haven't properly configured or run a Grooming job on the backup set. You can sometimes go a very long time without filling up a volume if you groom the set. You might try that next time before you try transferring the set to another disk. Good luck.
×