• Backup VLAN unreachable after linking to hypervisor

    Historically we've deployed the agent on all of our VM's and protected them directly from the core (no hypervisor associations/links). Each VM was given a secondary network adapter and assigned a static IP on a "backup" VLAN (i.e. 192.168.3.0/24... normal…

  • Failback Without Second Core

    My team is trying to test failover of production systems for a customer. They have five Windows server VMs on an ESXi host that each have a virtual standby on another ESXi host, but only one Core. There is a SQL server and an Exchange server involved…

  • Upgrading to 6.2 and would like to go agentless on existing VMs running 6.0.2 and 5.4.3

    Hello Quest / Rapid Recovery community!

    I'm preparing for an upgrade of existing COREs from 6.0.2.144 to 6.2.0.  My windows-based protected machines are a mixed bag of 6.0.2 and 5.4.3.  The main reason for the upgrade is to take advantage of the archiving…

  • Standby option server time issue

     Hello,

     

    I have an issue, i create a standby option backup from esxi to hyper-v and that occurs every hour, the problem is that the VM datetime keeps get changed.

    After some digging i found the problem is rapidrecovery... when the process start the vm…

  • VCenter permissions

    I have a question regarding the necessary permissions to export a vm from Rapid Recovery. I have a tech that I would like to test the backups of our customers once a month. A simple export of the VM to and ESXi host and then having the tech boot the machine…

  • Problem with Agentless Allocated space

    Hi,

     

    i use RapidRecovery  6.0.2.144 to backup about 12 ESXi (6.0.0 4192238) hosted VMs agentlessly.

    On some of those machines (thin provision disks)the shown allocated space is wrong (says the disk is full).

    The problem is then that my base image are bigger…