Hi all,
My Company is in the process of acquiring another company that also uses VBR. We'll be carefully analyzing what their setup looks like but we'd don't currently have access due to regulatory and legal issues.
I'm looking for feedback from those that have gone through similar scenarios. Did you leave them completely separate? Is there a clean way to merge? etc.
Thoughts, comments, ideas are appreciated.
Thanks
G
-
- Influencer
- Posts: 16
- Liked: 2 times
- Joined: Nov 12, 2015 9:14 pm
- Full Name: Gordon Armstrong
- Contact:
-
- Product Manager
- Posts: 14599
- Liked: 2969 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Adding additional Veeam environment via aquisition
Hello,
I have seen both scenarios at customers. If the IT departments merge, then they merged the VBRs usually together (except when different VCenters / continents with unstable links are involved).
In other scenarios, they started merging licenses at some point in time when Veeam renewal happened and just added Enterprise Manager for central license management.
There is no "merge" button for two VBRs. But one can export / import job settings with the REST API if that saves time.
Best regards,
Hannes
I have seen both scenarios at customers. If the IT departments merge, then they merged the VBRs usually together (except when different VCenters / continents with unstable links are involved).
In other scenarios, they started merging licenses at some point in time when Veeam renewal happened and just added Enterprise Manager for central license management.
There is no "merge" button for two VBRs. But one can export / import job settings with the REST API if that saves time.
Best regards,
Hannes
Who is online
Users browsing this forum: karsten123, Semrush [Bot] and 210 guests