#Veeam backup vcenter full#
#Veeam backup vcenter free#

and before moving further, take a backup of your VeeamBackup database just in case something goes wrong. WeвЂre ready to go now really, just disconnect the hosts from your vCenter and move them over to the new one but donвЂt touch a single button in the Veeam environment yet, we need to do everything manually.

#Veeam backup vcenter free#

Because IвЂm from a special country I use my own langague for tablenames so please excuse that but basically it means вЂћjointableвЂњ, feel free to change the tablename to adapt but remember to change it everywhere in the coming scripts. I like working with databases because you can easily connect things through SQL but in order to use the information we have we have to add one table to the VeeamBackup database. I have no idea what this is and having the wrong path has no noticeable affect. If you look at the BObjects table youвЂll see that it has a вЂћpathвЂњ column which directs to a vCenter server and corresponding Resource pool. So why all this other stuff? Because we need to make sure weвЂre changing the right VMвЂs so we donвЂt mess up the actual backups. So what do we need to change to make this work? We actually just need to change the object_id and host_id in вЂћdbo.BObjectsвЂњ. Some records donвЂt have this ID and I have no clue why, I canвЂt be arsed to check because we can go around it. Uuid вЂ“ This is the VM Unique ID, it should not change between vCenters but I make no guarantees. Object_name вЂ“ this is your VM name, it should be the same as the name in your vCenter When you move that VM between vCenters then this ID changes. Object_id вЂ“ this is and ID that each vCenter assigns to their VMвЂs. Type вЂ“ type = 1 here means VM, yes this is confusing but we only use this for minor things.

Host_id вЂ“ This should match the ID in the вЂћdbo.HostsвЂњ table, before you edit this it should contain the same value as the ID of your original vCenter server.

Now you can look at вЂћdbo.BObjectsвЂњ, it has these important values Type вЂ“ YouвЂre most likely looking for type with ID = 1 ( vCenter ) Name вЂ“ This is the name you can use to identify which host is which ID вЂ“ The actual host ID, youвЂll need this later You therefore need to dig a little in the database and find which values are used to identify the location.ДЇirst table to look at is вЂћdbo.HostsвЂњ, it contains these important values: It tries to connect to the old vCenter to look for the VM but canвЂt find it. The method is therefore to pick up what data Veeam uses to identify VMвЂs and where theyвЂre located but that is the problem veeam faces when youвЂve moved the VM. The method should still be valid.ДЄll data for backup is saved into repositories so messing with the database will ( hopefully ) not mess with your actual data. This method is not supported by Veeam and requires modification for each configuration.

#Veeam backup vcenter full#

Veeam doesnвЂt support moving VMвЂs between vCenters without removing them from backup jobs and re-adding them resulting in a new full backup and all sorts of problems with restoring old points.