• State Suggested Answer
  • Replies 12 replies
  • Answers 3 answers
  • Subscribers 32 subscribers
  • Views 16811 views
  • Users 0 members are here
Options
Related

Support for Windows Server 2019

computer office
over 6 years ago

I've recently attempted to install the Quest agent (Core 6.1.3.100) on a fresh instance of Windows Server 2019, the agent "installs" however the machine doesn't reboot successfully (goes into boot loop). I have attempted a repair install of the agent but get the same results.

Has anyone successfully installed and protected a Server 2019 machine?  I don't see any official mention of 2019 being supported yet. 

  • 0 over 6 years ago

    Good morning, 

    Server 2019  has not been tested or approved for support with Rapid Recovery as of yet.

    You may want to try boot in Safe Mode and attempt to uninstall the Agent to get the OS back to being stable.

    Keep an eye on our Technical Documents page when a new release is put out. You can check the System Requirements Guide in the future for when Server 2019 becomes officially supported.

    support.quest.com/.../technical-documents

    • 0 over 6 years ago in reply to francis jeffrey

      considering the initial release date for 2019 was October 2, 2018, can you confirm when it will be supported?

      • 0 over 6 years ago in reply to aperrin

        We expect some level of support to come with the next version of Rapid Recovery that is released. We do not currently have a release date, but the hope is that it will be in the next couple of months.

        • 0 over 6 years ago in reply to Tim Seymour

          So this comment was made 4 months ago... is 2019 supported yet? It's been close to a year at this point and MS releases their OS builds early to most large vendors so they can work on support well ahead of release (i.e. it has been well more than a year). I see 6.3 was released but I don't see any mention of Server 2019 support...

          • 0 over 6 years ago in reply to nbeam

            Yes. 6.3 supports Server 2019 with one limitation.  Page 11 of the release notes for 6.3 says " Rapid Recovery release 6.3 supports Windows Server 2019, except for volumes using the using Resilient File System (ReFS). " Microsoft made some serious changes to REFS in 2019 and we've been working with them in order to get things working.

            I recommend reading the release notes and system requirements guide at https://support.quest.com/rapid-recovery/6.3/technical-documents prior to upgrade.

        • 0 over 5 years ago

          Do we have any idea when full support for Windows Server 2019 (ReFS) & RHEL 8 is ready?

          • 0 over 5 years ago in reply to webaccounts

            RHEL 8 is slated for our 6.5 release which will hopefully happen in July/August of this year. The Rapid Recovery Team is evaluating the development schedule for REFS support in Server 2019 and a release date should be available soon. 

            • 0 over 5 years ago in reply to Tim Seymour

              Hi, it's been a few days now, but ReFS still doesn't seem to be supported?
              Is there already a prospect for a new release or do I have to deal seriously with Veeam?

              • 0 over 5 years ago in reply to stefan.restle

                The Rapid Recovery Development team has been working with Microsoft on resolving an outstanding issue with the Rapid Recovery filter driver and a bugcheck in Windows Server 2019 when attaching to an REFS volume. They are close to a final resolution, but we still don’t have specific timeline for resolution. As soon as the fix is ready we plan to publish a patch to make support of REFS available in Server 2019. Thank you for your continued patience.

                • 0 over 5 years ago in reply to Tim Seymour

                  Thank you for the heads up. Greatly appreciated.

                  Any issues that arose from supporting rhel/centos 8?

                  • 0 over 5 years ago in reply to Tim Seymour

                    I see version 6.5 is out but it still doesnt support ReFS on Server 2019.  Can you please give an update?  This is a critical issue as many clients have ReFS volumes on Server 2019.

                    • 0 over 5 years ago in reply to Tim Seymour

                      This is a Gripe but also a Warning.

                      Unfortunately I miss the above note and am now dealing with a dead exchange server that I though was backed up with a reliable backup software.

                      I would just like to make two points.

                      Firstly the log files (essential for recovering a corrupt main data base) on an NTFS partition, had a number of log files missing when restored, so not just the corrupted main data base on the ReFS drive so there may be an issue with backing up Exchange 2019 also. 

                      Secondly why doesn't Rapid recovery send an error message/warning when it is backing up the known unsupported ReFS. That way someone like me me who missed the fine print initially can change to a another product for backup then they see the warning in the backup logs, rather than finding out after the server has been lost due to a Microsoft update. Wouldn't this be something a responsible backup software provide should do.

                      Not claiming it is not my fault for missing the fine print, just disappointed at being caught out with out any notification from the software. Even the errors Rapid gave took a lot of digging before I found the possibility it was the ReFS issue.

                      I'm sure Rapid will resolve this issue in the future.

                      Thank you