https://www.quest.com/community/rapid-recovery/en-USTelligent Community 13https://www.quest.com/community/rapid-recovery/i/ideas/request-for-a-specific-forest-migration-option-in-quest-active-directorySat, 17 Jan 2026 06:14:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:4d4f0dab-43cd-441c-ab8c-9d7e269ddd8ctechxnegi5I’ve been using Quest Active Directory tools for directory management and migration, and overall the experience has been quite solid. However, while working on a recent project, I realized there is a gap that could significantly impact complex enterprise migrations—there is no clearly defined or dedicated option focused specifically on advanced forest-to-forest migration scenarios . In environments with multiple trusts, selective attribute mapping, or staged coexistence requirements, the current options feel more workaround-driven than purpose-built. It would be extremely helpful if Quest could introduce a dedicated forest migration option that offers more granular control over cross-forest dependencies, object mapping, SID history handling, and post-migration validation. Such a feature would reduce manual effort, lower risk during large-scale migrations, and make the tool even more competitive for enterprises managing complex Active Directory infrastructures. I’m sharing this here to see if others have faced similar challenges and to encourage Quest to consider this enhancement in future releases.ADhttps://www.quest.com/community/rapid-recovery/f/forum/36786/rapid-recovery-acl-rules/85475Mon, 08 Sep 2025 21:36:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:4314e9e7-00ab-408f-93ae-da1b5763cc4cphuffIt's been a minute but it use to be 443 was needed. Easy enough to validate, but that's where I'd start. Now I want to check myself.https://www.quest.com/community/rapid-recovery/f/forum/36786/rapid-recovery-acl-rulesWed, 03 Sep 2025 14:44:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:d96bfb9c-78a3-49a5-a530-31e5e75f60b9simon peartWe have a Rapid Recovery 6.10 with multiple Rapid Recovery 6.10 agents round the network, they're all connecting to the Core through port 8006. I've read some guides that says make sure 8006-8009 are unblocked, which they are but when i block all traffic, apart from those 4 ports, all the agents go offline. Am i missing a port that also needs unblocking please?Rapid RecoveryACLhttps://www.quest.com/community/rapid-recovery/f/forum/36485/active-license-but-single-core-gives-error-the-grace-period-has-expired-check-license-settings/85005Fri, 04 Jul 2025 09:51:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:18864172-2cc9-4d03-adfe-d154baa08221Victor.Portilloawesome, glad it worked!https://www.quest.com/community/rapid-recovery/f/forum/36485/active-license-but-single-core-gives-error-the-grace-period-has-expired-check-license-settings/85002Fri, 04 Jul 2025 08:59:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:51230a6d-0eea-492d-9e41-6503bc4e09a4h hamThank you Victor.Portillo, I did not found this page in my search, but it contained the fix for my issue! My problem was this, an expired certificate: https://support.quest.com/kb/4043104/core-fails-to-contact-license-portal-with-the-http-request-is-not-authorized-on-the-anonymous-client-authentication-schemehttps://www.quest.com/community/rapid-recovery/f/forum/36485/active-license-but-single-core-gives-error-the-grace-period-has-expired-check-license-settings/84993Thu, 03 Jul 2025 13:43:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:b3d31d53-1b6c-4d16-a47d-6a9360520ae8Victor.PortilloThis KB article have a few suggestion to try License Portal troubleshooting guide (4371019) I hope it helps.https://www.quest.com/community/rapid-recovery/f/forum/36485/active-license-but-single-core-gives-error-the-grace-period-has-expired-check-license-settings/84992Thu, 03 Jul 2025 13:13:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:0d940393-53ca-4c37-b9f6-39d72da9b88ah ham(Temporary) disabled the firewall and removed the AV, didnt help. We do not use a proxy server.https://www.quest.com/community/rapid-recovery/f/forum/36485/active-license-but-single-core-gives-error-the-grace-period-has-expired-check-license-settings/84988Thu, 03 Jul 2025 08:48:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:97b54b54-235b-468a-8ad2-8c7fe757eacbh hamThis might be related, a manual update check gives this error on the affected core server (Other core server do not give the error): I have no idea which file this is. Details: Exception chain: The data at the root level is invalid. Line 1, position 1. Error in deserializing body of reply message for operation 'GetManifest'. The data at the root level is invalid. Line 1, position 1. Stack trace: Server side: System.ServiceModel.CommunicationException: Error in deserializing body of reply message for operation 'GetManifest'. The data at the root level is invalid. Line 1, position 1. ---> System.Xml.XmlException: The data at the root level is invalid. Line 1, position 1. at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, String res, String arg1, String arg2, String arg3) at System.Xml.XmlExceptionHelper.ThrowInvalidRootData(XmlDictionaryReader reader) at System.Xml.XmlUTF8TextReader.Read() at System.Xml.XmlBaseReader.IsStartElement() at System.Xml.XmlBaseReader.IsStartElement(XmlDictionaryString localName, XmlDictionaryString namespaceUri) at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescription messageDescription, Object[] parameters, Boolean isRequest) at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest) at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeReply(Message message, Object[] parameters) --- End of inner exception stack trace --- Server stack trace: at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeReply(Message message, Object[] parameters) at System.ServiceModel.Dispatcher.DemultiplexingClientMessageFormatter.DeserializeReply(Message message, Object[] parameters) at System.ServiceModel.Dispatcher.ProxyOperationRuntime.AfterReply(ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at Cloud.Common.Communication.Wcf.ErrorHandling.CloudWcfErrorInspector.AfterReceiveReply(Message& reply, Object correlationState) at System.ServiceModel.Dispatcher.ImmutableClientRuntime.AfterReceiveReply(ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [1]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Cloud.Common.Contracts.AutoUpdate.IAutoUpdatePublicCloudService.GetManifest(String coreId, String coreVersion, String productType, String locale) at Replay.Core.Implementation.AutomaticUpdate.ManifestResolver.GetManifest(Version currentVersion) at Replay.Core.Implementation.AutomaticUpdate.AutoUpdateService.DownloadManifest() at Replay.Core.Implementation.AutomaticUpdate.AutoUpdateService.CheckUpdatesInternal(Boolean nightlyJob) at Replay.Core.Implementation.AutomaticUpdate.AutoUpdateService.CheckUpdates() UI side: at WCFClientBase.HttpResponseMessageExtensions.Check(HttpResponseMessage message, Uri uri, String method, ILogger logger) at WCFClientBase.ClientBase.GetResponse(Uri uri, String method, String knownEtag) at WCFClientBase.ClientBase.ExecuteServiceCall[T](Uri uri, String method, String knownETag) at Replay.Core.Client.AutoUpdateManagementCoreClient.CheckUpdates() at Replay.Core.Web.Controllers.UpdateController.CheckForUpdates() at lambda_method(Closure , ControllerBase , Object[] ) at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters) at System.Web.Mvc.ControllerActionInvoker.<>c__DisplayClass24_0.b__0() at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation) at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation) at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation) at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation) at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation) at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation) at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation) at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName)https://www.quest.com/community/rapid-recovery/f/forum/36485/active-license-but-single-core-gives-error-the-grace-period-has-expired-check-license-settings/84985Thu, 03 Jul 2025 05:03:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:691563c0-f841-4e26-966c-7ce7f3a2fb6fsamar writingpro[deleted]https://www.quest.com/community/rapid-recovery/f/forum/36485/active-license-but-single-core-gives-error-the-grace-period-has-expired-check-license-settingsTue, 01 Jul 2025 09:39:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:6f228648-2654-48bc-ae40-b7a991bba614h hamHi, We have an error on one of our Rapid Recovery Core servers: 'The grace period has expired Check license settings' Before this error, it has ran without license issues for years now on this Windows 2019 standard server. A manual attempt to contact the license server (through settings) shows: ---- Unable to contact licensing server Communication with the license portal failed. This could have several causes, including the following: The license portal may be experiencing heavy load Your ISP may be having an issue A firewall rule has been added or changed Note: There is a 15 day grace period during which your license will continue to work. Please contact Quest Software Inc Support if this failure continues. ---- When I click on the link ( rapidrecovery.licenseportal.com/) it forwards me to ' id.quest.com/.../auth ...' No changes are made on this server, except Windows updates. 2 other Rapid Recovery cores with the same license do not have any issues. Already tried: - rebooted the Rapid Recovery services and the server - upgraded Rapid recovery to the latest version (6.10.0.316) - deleted registry key (HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\LicenseInfo ), restarted service and re-added the license - the ID's are different between the 3 cores - removed the affected core from the Quest license portal. Unfortunately this didn't help, does anyone else have an idea what this could be?BackupRapidRecoveryLicense Portallicensehttps://www.quest.com/community/rapid-recovery/f/forum/36372/best-way-to-restore-physical-platform-to-physical-platform/84599Fri, 23 May 2025 15:47:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:02381971-7173-4284-a46d-0a0f698793c6Victor.PortilloHi Simon, If you are doing a WIndows BMR you need to use a Windows BootCD not the Linux one, most likely that is the problem. In order to create a Windows BootCD you can take a look to this KB article How To: create a Rapid Recovery Boot CD (4035439)https://www.quest.com/community/rapid-recovery/f/forum/36372/best-way-to-restore-physical-platform-to-physical-platformFri, 23 May 2025 08:31:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:a2f0c336-4e0e-42e4-87f2-eb38ca591e53simon peartI'm doing a restore of a physical Windows 10 machine from Rapid Recovery 6.10 to another desktop machine. I'm booting off the Linux Live DVD, tried version 6.10, 6.9 and 6.7, and it gives me the ip and the password but it fails with the below error. I've turned off firewall on the Rapid Recovery Core, no change, i can ping the ip of the system fine from the Core, but still continuously get this error. 99% of our servers are VMs, these are easy to restore and sort, but the odd physical one still exists. It's not urgent that i do a restore but i need to migrate that machine over to another physical platform. ----- Exception chain: An existing connection was forcibly closed by the remote host Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. The underlying connection was closed: An unexpected error occurred on a receive. Call to service method 10.1.13.4:8006/.../fullMetadata PUT failed The URC instance cannot be reached at '10.1.13.4'. Please, ensure that your target machine has been successfully booted from Boot CD and the specified IP address/authentication key are valid ---- What about doing a fresh install of WIndows 10 on the new machine, removing the old machine from the domian, adding the new machine to the domain with the exact same domain name as the old machine, installing the agent and then restoring to the agent, is that a better option? I'm worrying that it's not as simple as it should be with this sort of restore.https://www.quest.com/community/rapid-recovery/f/forum/36147/automatic-agentless-backup-based-on-tags/82999Thu, 03 Apr 2025 21:23:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:070cd4e5-a59a-4692-b4bb-6ce98486cda7marc_65284I know about automatic agentless but we due to our configuration, we don't want everything backed up in all locations so I need to manually add new VM's to the appropriate RR core. If I could tag in vCenter that would be so much easier. I think Veeam does this? I will check out that Quest Ideas page, thanks.https://www.quest.com/community/rapid-recovery/f/forum/36147/automatic-agentless-backup-based-on-tags/82998Thu, 03 Apr 2025 20:54:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:999b7c8e-fd9c-419b-8704-472ec58043f1Victor.PortilloThere is a feature called "Automatic agentless protection". This feature will protect all new VMs; it does not take into consideration vCenter tags. You can add this as a feature request at Quest Ideas .https://www.quest.com/community/rapid-recovery/f/forum/36147/automatic-agentless-backup-based-on-tagsThu, 03 Apr 2025 20:39:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:73ca8c7a-01af-4b49-af6a-1fcb9d2a1e14marc_65284Is it possible to have Rapid Recovery backup VM's based on tags assigned in vCenter? I couldn't see any mention of this in the docs or poking around in the RR Portal.BackupRapid RecoveryVMwareagentlesshttps://www.quest.com/community/rapid-recovery/f/forum/35764/working-out-costings-for-online-storage/82274Wed, 22 Jan 2025 17:10:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:21dcf60f-f3e2-4276-97d4-e45d9d8a87a9phuffYou can archive yes, and although you will get the benefit of cheaper storage you will lose the benefit of retention. Replication gets you retention, Archive does not. Also, so we're clearly you can archive to S3, blob storage, but you can't replicate to S3, cold storage, replication requires a live Quest host and a live Quest repo. If you do what to replicate, each core has it's own retention policy, and each protected node can have their own retention policy, however all the data has to 'get' there first, and then retention kicks in. The best recommendation I can make to you for estimation on your SENDS, GETS, and READS is to calculate you actual metered traffic and add a 15-20% factor to them. It really comes down to what it is you're looking for. Archives are cheaper, as they can be on cold storage. The also do not provide retention policies, or virtual standby if you ever wanted to look into having a DR site. Always pros and cons, all comes down to what you're looking for. For replication, there are vendors that will supply you turnkey cores ready to use with fixed costs rather than an AWS/Azure where you get to configure it and the price can change significantly with bandwidth.https://www.quest.com/community/rapid-recovery/f/forum/35764/working-out-costings-for-online-storageTue, 21 Jan 2025 16:28:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:346bb5a3-7e6e-4a0d-8ea8-181a32a10a52simon peartOur current setup has 2x Cores, 1 at our DataCenter and the other at our headoffice. Each Core has a repository size of around 15-16TB being used and the repositories on each core replicate to each other. This gives us our online and offsite backups. We also have 5 archive jobs that are scheduled called Monday-Friday, with each archiving off between 5-6 servers, generally VMs, which then get copied to 5 tapes, this gives us the offline portion of the backups. Each archive uses around 3.3TBs of disk space. Now the question is, i'd like to investigate adding some online storage to this as well e.g. doing an archive to Amazon S3 or Azure. Is the archive option to online storage the best option, can i replicate incremental/base backups to the online storage instead when they are done? What's the best way to determine pricing, i can see pricing by size but also wants details like number of SENDS and GETS and READs, which i'm confused about how to calculate that?https://www.quest.com/community/rapid-recovery/f/forum/30427/support-for-rhel-8-centos-8-or-rocky-linux-8-including-rocky-linux-9/81813Mon, 02 Dec 2024 16:57:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:50b13094-eb75-49bc-84de-ef5c93d0be40webaccountsfyi: Rocky Linux 9.5's latest kernel doesn't work. kernel-5.14.0-503.14.1.el9_5.x86_64 Rocky 9.4: kernel-5.14.0-427.42.1.el9_4.x86_64 does work so you'll need to stay on this kernel for now.https://www.quest.com/community/rapid-recovery/f/forum/34434/rapid-recovery-support-for-rocky-linux-9-3/81743Mon, 25 Nov 2024 20:29:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:efb1cc9f-29e1-4fbd-b0d2-a5dfa64af32awebaccountsI can confirm: kernel-5.14.0-427.42.1.el9_4.x86_64 works kernel-5.14.0-503.14.1.el9_5.x86_64 does NOT. As of 11/25/2024https://www.quest.com/community/rapid-recovery/f/forum/35344/kernel-support-fails-again-rr-6-9Mon, 25 Nov 2024 20:25:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:cf58ef3a-bfcc-41df-9a32-55264ecaf17cwebaccountsI went to update the kernel on our RedHat Linux 9 machines and Rapid Recovery doesn't support their latest kernel. Kernel 5.14.0-427.42.1.el9_4.x86_64 Rapid Recovery 6.9.0-309.x86_64 This kernel came out in late 2021. Does Rapid Recovery have plans to support it?