![]() ![]() ![]() As far as it was concerned, the new vCenter was unknown and the old one was no longer anywhere to be found on the network. Now, this is where things started to get a bit interesting with regards to the existing Veeam B&R backup jobs. To be able to have an exit path, until the vSphere 4.1 hosts management agents, were reconfigured, a new vCenter VM was created with a new IP-adress and server name.Īfter the migration from vCenter 4.1 to 5.1, and from physical to virtual was completed, the existing Veeam B&R server was upgraded to the latest 6.5 release. Of course, it was also decided to move the vCenter installation from a physical server, to a VM in the same operation. To complicate things in this particular environment, I also had to migrate the vCenter SQL DB from a local MS SQL Server 2005 Express instance to a full-fledged MS SQL Server 2008 R2 instance. The customer engagement also includes upgrading Veeam Backup and Replication 6.0 to 6.5, and usually an isolated upgrade of Veeam B&R is a no-brainer next, next, next, done install. This week I´m working at a client site, upgrading their entire existing vSphere 4.1 infrastructure to vSphere 5.1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |