- #VEEAM BACKUP TEMPORARY SNAPSHOT INSTALL#
- #VEEAM BACKUP TEMPORARY SNAPSHOT DRIVERS#
- #VEEAM BACKUP TEMPORARY SNAPSHOT UPDATE#
- #VEEAM BACKUP TEMPORARY SNAPSHOT DRIVER#
#VEEAM BACKUP TEMPORARY SNAPSHOT INSTALL#
One of my Linux CactiEZ VMs was being a bit picky with the yum package I was trying to install so after some troubleshooting I figured I’d restore a virtual machine from Veeam Backup (granted not 3.0.1 which I believe is out, I have the original 3.0 release installed right now) to get an earlier state and see if it helped to start fresh (my other thought was there was a repository issue but my older CactiEZ 0.4 yum was working just fine, it was my CactiEZ 0.6 box I recently set up that was having issues (it runs CentOS 4.7)).īut my restore fails, with an error relating to not being able to create the directory on the ESXi host to restore the virtual machine.
#VEEAM BACKUP TEMPORARY SNAPSHOT DRIVER#
I was going through and upgrading VMware Tools on all of my virtual machines (the new release adds some driver support for enhanced NICs to Server 2003 and a few other minor things). The new NICs work great and now I have redundant paths to the SAN! (In one case I now have more than one NIC in the whole box that was doing SAN and LAN just on VLANs, so it’s quite nice to have multiple NICs available now!)
#VEEAM BACKUP TEMPORARY SNAPSHOT UPDATE#
So I upgraded yesterday when Update 4 was released (I actually just did a point release update to new Update 3 firmware the night before…doh!).
#VEEAM BACKUP TEMPORARY SNAPSHOT DRIVERS#
Veeam Backup is awesome and their version 3.0 is the first version to support the free ESXi version! I love the deduplication and compression and the ease of use when making backups! On March 31st, VMware released ESXi 3.5 Update 4, which added drivers for some very nice NetXtreme quad-port Gigabit Ethernet cards, which I have in two of my three VM host servers but have been unable to use until they released an updated version with built-in drivers for that hardware. I recently purchased Veeam Backup 3.0 to back up my three VMware ESXi Free hosts. (I even mentioned remembering the upgrade in my post at the last minute before I published it.) Upgrading fixed the problem and it appears to be working normally again now! Apologies for the fuss if you have Veeam Backup and ESXi Free make sure to upgrade both if you haven’t! I’m leaving the post with details of the errors below if someone finds the information they’ll at least know they need to upgrade :-) Maybe I should just call it an April Fools joke? Ha.
I added the 2 new disks I just made, being careful to make sure the first one I added was the boot disk.UPDATE 10:45 am : Silly me, I forgot until right before I was about to go to bed last night that there was a Veeam Backup 3.0.1 release I needed to upgrade to from 3.0. I shut down the VM and removed the 2 existing virtual disks. Vmkfstools -v 3 -i Server_1-000002.vmdk -d NewFile2.vmdk Vmkfstools -v 3 -i Server-000002.vmdk -d NewFile1.vmdk
You can convert to thin disks at this point if you want by adding a switch to this command. There were 2 vmdk's on the vm that each had 2 stuck snaps. Everything was perfect after that and Veeam jobs ran great. I was then able to delete the obsolete vmdk's and snap files through the datastore browser. Then I told the VM to use the new vmdk's and turned it back on. It brought all of the contents of the original base vmdk with it to the new clone.
I wound up having to shut down the VM, run a command to identify the current active vmdk snap files (which I can't remember), then clone those snap files to a new vmdk.
0 kommentar(er)
