Citrix: Turbo Charging XenServer Backups
I’m a car enthusiast — mostly for European small hatches (don’t judge!) — and also a big fan of newer/better technologies, so when it comes time to buy a new car, I tend to go focus on two things: smaller and faster engines. Keeping with the engine “downsizing” trend, adding a turbocharger is the way to go.
My love of cars notwithstanding, that entire passage was only necessary to cover up the fact that I’ve appropriated the title of this post from Miguel Contreras (Turbo Charging your IOPS with the new PVS Cache in RAM with Disk Overflow Feature!) and Nick Rintalan (Turbo Charging Performance with PVS 7.7). So, we’ve already turbocharged several things around here and, so I said to myself, “Why not keep up with the trend, right?”
I’ve stumbled with the fact that our exports for XenServer backups are far from being ideal both from the time they take to complete and the space they take on the backup drive. Yes, you can compress them, but… it takes forever. Yes, you can use the better xe vdi-export techniques on your backup scripts, but then you have to compress them on the destination and also, that gets you “just” the VHD file without the Virtual Machine parameters (CPU/RAM/NICs), which just add time and complexity to the backup/restore strategy.
Read the entire article here, Turbo Charging XenServer Backups | Citrix Blogs
via the fine folks at Citrix Systems, Inc.