Currently I have a Windows 2003 server with a tape library attached. I mount snapshots of my data volumes to this server and back them up using Backup Exec v9.1. also have the agent for Exchange installed on the Exchange 2000 server for that, and the remote agent installed on one other server for backing up the only data that is not on my SAN.

With my new VirtualIron infrastructure I am thinking of using NTBackup to create an image of the management server to a USB drive. Thoughts on this?

My data I will continue to backup the same way, mounting the snapshot to the backup server. It works, it's in place and it's pretty fast.

I think for most of the servers I will create a snapshot through the VI management. I should be able to mount that snapshot to a separate virtual server and back it up like any other files, this would require an agent and network bandwidth and scripting as reboots are required. Suggestions are welcome here, does this make sense or would you do it diferent? I'm also contemplating making snapshots and leaving them there, or just shutting the virtual server down and backing up the virtual disk to USB.

Exchange 2007 is the big question. Exchange agent probably but what about the entire server?

What product should I look at, given my familiarity with Backup Exec means I am definitely leaning Symantec's way but there's BE or System Recovery?

This person is a verified professional.

Limey, does this backup scheme give you the ability to restore files easily? Seems like you would have to restore a snapshot from backup (huge file), then mount that on a test VM and copy the file(s) out.

Since this kind of restore is the VAST majority of what we restore I'd look into upgraded BE and using the disk to disk backup feature (continuous protection server comes with BE and is very cool--it even has a Google like interface for doing single file restores).

As for the DR restores, sounds like the scheme you have is fantastic. BESR is a great product but really meant for image level backups of live servers, so might be an option instead of the NTBackup thing (certainly quicker, but MUCH more expensive).

@J-159, sorry, USB hard drive is correct. I don't see me making an image very often anyway, but it seems like a 500GB USB drive is a reasonable way of having a backup on the shelf.

Martin, by mounting the snapshot on the backup server it appears just like it would to the server it normally is on, so Backup Exec backs up the files. This means single file restores from tape are the same as normal.

Oh, wait, are you talking about if I make snapshots of the servers and mount them to back those up as files? If so you are probably right except I don't see that as needing to restore single files.

Basically I want to save money on agents by not backup up every virtual server to BE or BESR, and also reduce the bandwidth that would take. But I still want to have a backup just in case the virtual server goes pear-shaped.

The management server will be probably one of only two physical servers, the other being the backup server, so actually an agent for that may be OK, or just the USB image.

My original thought when I started down the VM path was to just have a copy of the virtual machine on disk or disc ready to copy back in case of disaster.

This person is a verified professional.

OIC now. So just scripting the mount of the snapshot on the backup server and then backup the files from there. LOL, this is exactly how VMware's VCB works -- attaching to the snapshot so the production machine isn't affected at all.

We use backup exec with our virtual and physical servers. We use the exchange agent to backup the entire exchange 2007 server, which is one of a the few physical servers we have. Our file/print/AD servers are on VMware, we just backup the file shares of those machines with BE.

We use esxi to make snapshots of the vms in case something happens there, but we also have backup vms that we can turn on and slap the file shares on if anything were to happen to our main virtual servers.

Then to update users network drives we would just push out a group policy with the new drive mappings.

This person is a verified professional.

Make sure not to hang onto snapshots for too long. ESX has problems with snapshot files that get larger then the original VMDK.

Also remember that a snapshot is NOT a backup. It freezes the original disk and then creates a new VMDK and puts all the changes in there. When you delete the snapshot it merges the changes back into the original file.

Oracle, I mean VI, doesn't support virtualising the management server as it has to provide the DHCP addresses for the nodes. Actually it's booting the nodes from the management server, no install needed on the node.

Momurda, that's probably what I'll end up with. New version of BE on the physical backup server, back all my data up just like I do now and backup the Exchange server entirely. Have copies of the VM's in case of disaster. Actually I could just have a clone of the exchange server and backup the emails instead.

Well, with all the acquisition stuff I ended up at VI's website and they have a new Virtual Vignette on Backing Up, so I watched it.

Basically I am going to upgrade to new version of BE for the physical backup server. Get the Exchange agent and use that for Exchange data. For all virtual servers, that I wouldn't just rebuild, I'll manually create a snapshot, export to VI-Center as a VHD and back up to external HD or possibly tape. May need an agent for the management server at that point.

Snapshot and proxy backup host, backup key files not full disk image. Create snapshot, move to another VS, mount the snap and backup to physical backup server, delete snapshot. Need agent/license for PBH but only one for many VSs to be backed up. Requires use of logical disks, manual multi-step process.

VI cloning- create full copy of full disk image. Point and click, can also export disk to VHD file on VI Center, VS must be shut down.

Points to remember:

Use a snapshot to roll back a VS or feed a backup. With Copy-on-write snapshots if the original disk fails so does the snapshot.

VSs with a snapshot cannot be LiveMigrated, LivePowered, or LiveRecovered

Don't leave snapshots on a VS indefinitely, they take up memory. Use them on a temporary basis.

Limey, the only issue with DR is if you have tape backup, you need a tape deice to restore with, that can lengthen your windows to an operational platform.

Really, it is only the data which you need constant protection of, backup to disk arrays that are removeable is the easiest method IMO. I would only bother to sanpshot backup of VM once a month, the O/s isnt going to change that much in that time....

0

This topic has been locked by an administrator and is no longer open for commenting.