Last week I upgraded a VCenter Server from version 4.0 to the newest version 4.1. Version 4.1 now needs a 64bit operating system (yes, it's a must now) and therefore I reinstalled the physical server with the 64bit version of Win 2003.
I started the VCenter Server inventory from scratch again, adding all the physical ESX and ESXi servers to it. And I wondered, if Veeam Backup & Replication 4.1 would correctly work again... the VM's names didn't change so if it works by vm object name, there shouldn't be a problem.
But no. The Veeam jobs didn't run anymore and ended with an error:
Analyzing object "VM-Name" Object VM-Name not found. There are no objects to backup
What can be done about that is to go into the properties of each job and reselect the VM's to backup. This adds the new so called refID from the new inventory of VCenter Server into the Veeam database and should now communicate with the correct VM.
Important Update 20.07.2010:
Even though some manual adjustments were made in the job properties and even in the SQL database, the jobs won't run. After having contacted Veeam support, the answer is simple: Veeam Backup & Replication in version 4.1 is not compatible with vSphere vCenter Server 4.1!
No comments yet.
AWS Android Ansible Apache Apple Atlassian BSD Backup Bash Bluecoat CMS Chef Cloud Coding Consul Containers CouchDB DB DNS Database Databases Docker ELK Elasticsearch Filebeat FreeBSD Galera Git GlusterFS Grafana Graphics HAProxy HTML Hacks Hardware Icinga Icingaweb Icingaweb2 Influx Internet Java KVM Kibana Kodi Kubernetes LVM LXC Linux Logstash Mac Macintosh Mail MariaDB Minio MongoDB Monitoring Multimedia MySQL NFS Nagios Network Nginx OSSEC OTRS Office PGSQL PHP Perl Personal PostgreSQL Postgres PowerDNS Proxmox Proxy Python Rancher Rant Redis Roundcube SSL Samba Seafile Security Shell SmartOS Solaris Surveillance Systemd TLS Tomcat Ubuntu Unix VMWare VMware Varnish Virtualization Windows Wireless Wordpress Wyse ZFS Zoneminder