This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Upgrade from AppAssure 5.4.3.106 to Rapid Recovery 6.0.2 on DL1000 (backup and replication)

I got my last three sets of backup/replication DL 1000 units (six total servers for three separate clients) earlier this year, when RapidRecovery was probably already in the process of replacing AppAssure. Upgrades are included as part of my AppAssure support contract. Now I see that the upgrade to RapidRecovery is available and at level 6.0.2.144. While Dell provides what I can only assume are sound download & upgrade instructions, I would prefer to hear a real-world experience of the process from someone that has tried it--things like these:

  • Would you recommend this upgrade or are there reasons I should avoid it or wait for some further RapidRecovery service pack?
  • How well did the upgrade go?
  • Were there surprises, such as auto-reboots of servers running the Agent?
  • How long did it take?
  • How is performance afterwards?
  • Does the UI change much? For the better? For the worse?
  • Are there omissions in the Dell documentation that led to any panic moments or inference-based steps?
  • Was there any post-upgrade reconfiguration necessary?
  • Is there any recommended post-upgrade cleanup?

If not, I guess I may be the guinea pig here.

Parents
  • Hi Brian,

    The latest build of Rapid Recovery Core for the DL appliance is 6.0.2.177. The latest agent build that exists is 6.0.2.144. So the behavior you are seeing is expected. I'll make a note with the development team and let them know that the UI states the wrong build number when deploying an agent in build 6.0.2.177. Thanks for reporting it!

    Tim
Reply
  • Hi Brian,

    The latest build of Rapid Recovery Core for the DL appliance is 6.0.2.177. The latest agent build that exists is 6.0.2.144. So the behavior you are seeing is expected. I'll make a note with the development team and let them know that the UI states the wrong build number when deploying an agent in build 6.0.2.177. Thanks for reporting it!

    Tim
Children
No Data