Veeam Backup 4.0 Release

[Gostev]

WARP SPEED AHEAD: VEEAM BACKUP IS 10+ TIMES FASTER
New Veeam Backup & Replication 4.0 Makes the Most of VMware vSphere™ 4 Changed Block Tracking; True Enterprise Solution Includes Centralized Management

Press Release
http://www.veeam.com/news/veeam-backup-is10-times-faster.html

Video
http://www.youtube.com/watch?v=0KB9ktninyc

What's New
http://www.veeam.com/veeam_backup_4_0_whats_new_wn.pdf

[Gostev]

FAQ

Q: When Veeam Backup & Replication 4.0 will become generally available?
A: Current schedule is the following: RTM is late Q3, GA in beginning of Q4 (October). These dates are subject to change. Released on 10/28/2009

FAQ has been moved to the separate thread:
Veeam Backup 4.0 FAQ

[Gostev]

Also, since I expect this thread to have a lot of views... I had to place this ad here to make some money (just kidding)



Click this link to vote (takes less than 1 minute)
http://surveys.verticalresponse.com/a/show/491497/d68387378b/0

[TrevorBell]

Gostev,

Please can you clarify the thin provisioning that we can expect with Veeam. Will it be both on replication aswell as just straight forward backups ? Also the new api for FT backup is all well and good if you have an ESX cluster that supports it, alas my xeonx 3 gig cpu`s do not so i will be staying with VCB

Also please can you explain the licensing for upgrades, Do exsisting customers get a free upgrades like previous versions as i looked at the press release and i can`t make out if it is or not ? No doubt others will ask this question too so i`d thought i will get it in early


Thanks
Trev

[Gostev]

Hello Trevor,

Backup - YES
Restore - YES

Replication - MAY BE, depending on QC resources availability and overall release state, the code is ready. If not in 4.0, then with next update release.

[TrevorBell]

Gostev,

Updated my question a little

[alexr]

Fantastic!

In network mode, will it continue to run in service console and be subject of severe performance restriction of vSphere?
I realize that with dirty block tracking we should get great improvement but full backup will be as slow as it is now right?
BTW any update from VMware on the issue?

[Gostev]

Alex, no changes to network mode backup. Last thing we heard from VMware is that they are working on the fix.

[Gostev]

Trev, I've updated FAQ.

[raphael@schitz.net]

Backup of fault-tolerance enabled VM will be supported in this release ?

[Gostev]

Backup of FT VMs will be supported after vSphere update that enables ability to backup FT VMs through vStorage API is released.
http://communities.vmware.com/message/1266792#1266792

[raphael@schitz.net]

Thanks for the info.
BTW, the 4.0 new features sounds really really great ! Nice job !

edit :
I didn't understand this part : "Unlike competitive solutions that require replicated VMs to run with open snapshots (which prevent Live Migration and DRS)" ?

[dlove]

Awesome feature set! I can't wait to install it and take advantage of all the new features. So glad about our switch from vranger to veeam Keep up the pace fellas, you should be proud!!

[Gostev]

I didn't understand this part : "Unlike competitive solutions that require replicated VMs to run with open snapshots (which prevent Live Migration and DRS)"

The way DoubleTake or Vizioncore build their replication solutions makes the source VM always runs with snapshot. When replication cycle comes, new snapshot is created and old snapshot data is transferred over to the target (replica). So source VM has the snapshot present all the time. This is not acceptable architecture for many customers, because if there is at least one snapshot on VM, VMotion and DRS will not work.

[raphael@schitz.net]

I didn't understand this part : "Unlike competitive solutions that require replicated VMs to run with open snapshots (which prevent Live Migration and DRS)"

The way DoubleTake or Vizioncore build their replication solutions makes the source VM always runs with snapshot. When replication cycle comes, new snapshot is created and old snapshot data is transferred over to the target (replica). So source VM has the snapshot present all the time. This is not acceptable architecture for many customers, because if there is at least one snapshot on VM, VMotion and DRS will not work.

That's what i thought.
But snapshot does NOT prevent vmotion or DRS, it makes warning only (hostname related).