Nuts and bolts in NetBackup for VMware: Understanding V-Ray vision through backup process flow
Now that we know how VM discovery job works for a VMware Intelligent Policy (VIP), let us move on to the actual backup job. The process flow described here is the same for both VIP and browse-and-select type policies unless specified otherwise.Harnessing the power of VMware vStorage APIs for Data Protection
Trucks move stuff. The engine burns fuel to generate power. Transmission system sends the power to the wheels. The trailer carrying the payload moves. Trucks consume a finite amount of time and energy to reach destination. We have learned in high school that engines and transmission systems have less than 100% efficiency. You are losing some of the generated power to heat and friction. Let us say you were given four of these big rig systems, all are identical with the exception of the transmission systems. Now you are measuring the time they take and fuel they burn to move a fixed amount of payload from one location to another. You repeat the experiments for different amounts of load. You plot the results to benchmark performance, efficiency and scale. Backup solutions integrating with VMware vStorage APIs for Data Protection (VADP) are similar to the transmission systems in trucks. The engine that really powers the backup process is the set of vStorage APIs. The goal of the backup solution is to harness its power to move data in virtual machines to secondary storage systems. Thus the virtual machines being backed up constitute the payload. As some of you already know, Veritas/Symantec had asked Principled Technologies to benchmark these transmission systems in harnessing the power of VADP. Here are the results. Remember that all trucks are equipped with the same engine (VADP). The load added (from 100 VMs to 1000VMs) for various tests are also the same. In accordance with the strict benchmarking standards, all the trucks were given a few runs to break-in so that the regular day-to-day operating conditions are evaluated. After the break-in runs, three benchmarking runs are conducted for each load. The median value for each truck for each loadis plotted above. Let us interpret the results. Performance The first thing that stands out from figure 1 is that the orange truck (NetBackup is represented in Orange. As this benchmarking started before the announcement of Veritas separation we used orange to represent NetBackup) is the fastest no matter how small or large the payloads are. And red truck (Competitor ‘C’) is the slowest! Even at the largest payload of 1000 VMs, NetBackup is 5.8x times faster than the slowest in the herd. The blue (Competitor ‘E’) and green (Competitor ‘V’) are weak when compared with the performance leader, NetBackup. However both are way better than the red truck. The bottom-line: If you are on blue or green trucks and run out of gas, do not hop onto to red truck! It is more like hopping on to an inefficient and slow steam wagon! Efficiency Now let us quickly gloss over figure 2. What you see is the CPU consumption at the data mover. In trucking terms, we are looking at how much gasoline is consumed for the trips and how much is still available in the reservoir if you had wanted to carry more loads. The orange truck (NetBackup) not only completed the trip much quicker but it also did the task with a lot of gasoline to spare. As you see can see we had to specifically draw attention to almost lost orange line in the resource utilization chart because of overwhelming gasoline consumption for pretty much all other trucks. The worst performer once again is the red truck. It is not just slow; it is also a gas-guzzler! There aren’t really any more resources to spare so you couldn’t have added more payload and hoped to finish the trip in the same time frame. The blue truck uses up nearly 85% of resources to for its trip. The greentruck starts somewhat well but the consumption shoots up during the final quarter. Scalability What exactly is scale in the context of this benchmark? The scalability is a measure of how well the product performs as the load it needs to handle increases. As you can see from figure 1, as you increase the load NetBackup continues to perform well ahead of the herd. But this data by itself only justifies that NetBackup is #1 in scale. Now let us move to figure 2. NetBackup data mover (media server) is using less than 50% of the gasoline while finishing the task in less than 1/5th of the time when compared to the worst performer. In other words, by the time the red truck moves 1000 VMs, NetBackup could have moved 10,000 VMs! That is 10x better scale! NetBackup is not only #1 in performance but it stays at that position while consuming the least resources thereby making more room for future demands. Thus NetBackup is indeed the king of scale. There is a lot more for us to share with you. How about scalability in recovery? How about storage integration? Will you be at VMworld San Francisco this year? Join George Winter and me at this session to learn more about the benchmark design, methodology, results and lessons learned. King of scale benchmark revealed in VMworld#STO5475Looking for the Right Data Backup Solution for the Virtual World? Ask Yourself These Three Questions
Backup is like an insurance policy. You want it for the peace of mind, but you don’t want it to dominate your workday (also, nights and weekends!). You need to protect data on your virtual machines to guard against hardware/storage failures and user errors. You may also have regulatory and compliance requirements to protect data for the longer term.Defying Convention at VMworld 2013: Designing VMware backups that work!
VMworld 2013 is just a week away. Perhaps this is the one of the biggest technology events where I get to see experts who really get their hands dirty (functional IT staff like system administrators, VM administrators, Storage administrators, solution architects etc.) back in their jobs.Day and Night: NetBackup 5220 vs. that other product
I have worked for NetBackup Technical Support as a Staff engineer for long time. Customers don’t call us when things are working great; they need our help when they are not getting what they want from the product. Naturally, a seasoned engineer in support is continuously dealing with weaknesses or defects in the product more than its strengths.VMware announces "End of Availability for VMware Consolidated Backup"
As you may have heard fromVMware, the end is near for their VMware Consolidated Backup product, or VCB. It has been superseded by a new technology called vStorage APIs for Data Protection, or VADP. See their posting at http://app.connect.vmware.com/e/es.aspx?s=524&e=12880125. In NetBackup 6.5.1, we introduced "NetBackup for VMware" which requires VCB from VMware. The VCBrequirement remains inall later NetBackup 6.5.x releases. There are no plans to support VADP in NetBackup 6.5. In NetBackup 7, which is now available, we support both VCB and VADP. In fact, we support mixed environments of both, which recognizes that customers do not likely upgrade all ESX servers at once. There is even more good news:you do not needto upgrade to "vSphere 4" to leverage VADP (but vSphere is loaded with other advantages). Once you deploy NetBackup 7 for VMware, these are the minimum requirements for using VADP: - You use vCenter 2.5 or later. In that case, NetBackup 7 can protect VMs on ESX server 3.0.2 or later. - You use ESXserver 3.5 U2or later. If that does not apply, NetBackup 7 will attempt to use VCB. We will continue to support VCB deployments through NetBackup 7.It's uncertain at this time, but Idon't anticipate continued VCB support after NetBackup 7. Lastly, if you are using VCBtoday, the transition to VADP is relatively simple.What is known as the "VCBproxy server,"or the NetBackup Client for VMware, continues to be theoff-host backup server. The significant improvement in VADPis the backup host no longer needs a large disk staging area to hold a copy of the VM snapshot. With VADP, NetBackup now reads the snapshot directly from the ESX server, eliminating the inefficient VCBcopy and the associated staging area. This improvement alone should reduce the VM backup time in half! NetBackup 7 also supports other VADP enhancements, like block-level incremental backup of VMs. (Note, BLIB is one of those VADPcapabilities that does require an upgrade to vSphere 4.) For more information, please attend a webcast for "NetBackup 7 for VMware" at http://www.netbackupdemo.com. Or for the serious enthusiast, you can download the latest user guide at http://seer.entsupport.symantec.com/docs/340112.htm. Happy Virtualizing! Brian Smith NetBackup Product Manager