VCB backup - Linux guest OS

[b4ndit]

Dear all,

I am using ESX 4U1 and VCenter4U1, then a virtual server, Redhat 5.2 Ent 64 bit installed in the vm environment. I want to use a LAN free backup solution for this environtment. I am going to use VCB backup as one of the solution.

A server, Windows 2003 64bit, will ac as a virtual center and a proxy backup server.

My question is:

I am going to backup file/directory in the virtual machine (Linux guest OS). how to I achive this goal ?? :smileygrin:

thanks in advance..

BR,

Gari

[dconvery]

First off. Keep in mind that VCB is not going to be supported with the next version of vSphere. If you still want to use VCB, check out my guide here -> http://www.dailyhypervisor.com/2010/01/15/setting-up-vcb-for-any-backup-software-revisited/

Since VCB is going away, check out VDR. You can set this up for LAN free backups. Xtravirt.com has a good guide on how to get it to tape.

Dave Convery, VCDX

VMware vExpert 2009

http://www.dailyhypervisor.com

Careful. We don't want to learn from this.

Bill Watterson, "Calvin and Hobbes"

[b4ndit]

thanks for the respon dave...

If I use VDR, could I backup those Virtual Machine to backup tape(s) ?

I am using VCB because VCB proxy server can backup virtual machine into tape library..

Need advice ?:|

thanks

[bitbucket]

Yes, you can do.

I am using VDR with RDM as dedupe store that is be mounted to another VM which transfers everything to a tape library. Tape performance is nearly real world.

[b4ndit]

hm? how to to that ??

I assume, VDR appliance use RDM from a LUN mapped to VDR. Then, this LUN also mapped to a server that attach to a tape library ?

based on your reply, I assume, a tape library can attached to a virtual machine ?Is that correct ?

[bitbucket]

Right.

The appliance has to be shut down when you mount the RDM to another VM. I am using a W2K8 VM for the backup to tape process. The tape library is physically connected to a dedicated SAS controller in the host. I am using a ext2/ext3 file system driver to map the RDM and read all content.

I already tested to restore the dedupe store from tape. Works great. You can even keep the original RDM as store and create a vmdk, map it to the VDR aplliance and format it. Afterwards you can use this vmdk to restore with the other VM the dedupe store from tape. This presumes that you are using a VMFS block size that can handle vmdks files in the size you need for a restore. You just have to take care that you do not mount both dedupe stores at the same time to the VDR as this could result in unexpected behaviour.

[dconvery]

http://xtravirt.com/xd10131

Dave Convery, VCDX

VMware vExpert 2009

http://www.dailyhypervisor.com

Careful. We don't want to learn from this.

Bill Watterson, "Calvin and Hobbes"

[b4ndit]

Its confuses me..

well, I try to write down all step I would take..

fyi, I am using a SAN sw with EVA 4400 SAN Storage

the backup server is W2K3 Std 64x (physical server)

- Create a LUN from EVA 4400, create a fabric zoning to the esx host, present the LUN for RDM mapping

- Install VDR, mount the RDM LUN for VDR storage and make sure the appliance is running well.

- then, backup a vm using VDR, wait until its finished

- shutdown VDR appliance

- change storage presentation to a backup server, so the LUN will recognize as a partition on the backup server

- then using 3rd party backup software, backup this LUN to tape library..

Are these steps correct ??

and are there any "best practice" sizing for VDR..(Which I recall, in the VCB, a proxy backup need at least 1.5x times the biggest VM capacity for temporary mount point)

Thanks

[bitbucket]

These steps are correct. Depending on the OS you are using for the backup to tape process you have to use an ext3 file system driver (Windows). I am using this process myself with the difference that the backup server is a VM. This gives me more options when restoring a dedupe store from tape.

If you follow Dave Convery's recommendation you have to use a network share as dedupe store. Please keep in mind that using a share as dedupe store adds some more limitations. A share bigger than 500GB should not be used as a dedupe store. With a maximum of two dedupe stores per VDR appliance this would lead to half of the capacity you could reach with a vmdk or RDM.

The most reliable target for a dedupe store is a RDM. No overhead, no IO issues and better performance for backing up to tape.

You need to use an ext3 file system driver when you are using a Windows VM to mount the RDM for the backup to tape process. Please note that the VDR does not mount the dedupe store automatically after starting. You could use a mount command in the rc.local for example and take care that a file system check is started after 30 mounts (max mount value).

[b4ndit]

ouch..

I rather chose vcb then..

how could this vdr solution become sooo complicated..?

could these steps, perform in automation ? using scripts or bacth file ? or something else ?

and, how to calculate a VDR dedupe store ?

[bitbucket]

-- deleted --

[dconvery]

First off, VCB is being deprecated in the next major release. That has already been announced by VMware, so I am not revealing any secrets. If you check out the doc on xtravirt's site, it will explain how to automate it. Its fairly simple. You just use a PowerCLI script on pre-processing to shut down the VDR appliance. Back up the VDR data. Then you use a PowerCLI script on post-processing to turn the VDR back on.

Calulating dedupe is very tricky. It depends on how much data you have that is unique. If you keep your OS and apps at a standard patch level, you can pretty much figure only one instance of each.

Dave Convery, VCDX

VMware vExpert 2009

Careful. We don't want to learn from this.

Bill Watterson, "Calvin and Hobbes"

[bitbucket · Accepted solution]

No reason to scare. You do not really think that I am keen on performing all these steps manually? Everything works automatically and observing each step isolated, it turns out to be really straight forward.

1. create a RDM

2. mount RDM to VDR and format

3. perform backups

4. shutdown VDR after backup window closes (with vCenter schedules)

5. start Backup-To-Tape appliance at time y (let's say it's a Windows VM)

6. mount RDM with ext2/ext3 file system driver (www.fs-driver.org)

7. use a third party backup software to save RDM content to tape

8. shut down Windows VM when backup has been completed

9. start VDR at time z

I am using this process for some weeks now and I already tested the recovery from tape to disk and from disk to VM. No complaints

[b4ndit]

thanks guys..I'll try this one.

Thanks for your time..nice discussion..

[JaFF]

Sorry to drag up an old thread.

bitbucket,

I have created a 2TB RDM to VDR and have formatted.

I can perform backups no worries and I am comfortable with setting up the scripts to automate the start up / shutdown of the VDR appliance during a backup to tape.

What I need assistance with is how you automate the process of presenting the LUN to your Backup server.

In my case this is a physical server with CommVault. It is attached to the SAN (FC).

Can I just present the LUN to both hosts and as long as I don't make any changes to the LUN from the Windows host while VDR is on I'll be ok or is it actually a process of only presenting the LUN to one server at a time?

Hope someone can help as I really need to get a solution in place to backup to disk and then to tape.

I have read the article on xtravirt but want to keep this process on the SAN rather than over the network.

Cheers,

J