Forum Discussion

LucSkywalker195's avatar
12 years ago

Backuping up raw device mapped disk attached to a VM client

I need some knowledge: I'm using Netbackup 7.5.0.3 on Windows Server 2008 with a master and 2 media servers that are my VMWare backup hosts. I. - Backing up VM's with attached RDM disk: I've read the VMWare and snapshot client documentation but I'm still a little unclear about how to backup RDM (raw device mapped) disk. From what I read, I have 2 options: 1. - Install Netbackup client within the VM and backup the VM as I would a physical server. (not preferred.) 2. - Create an alternate backup client that has same OS and patch rev (or higher) that has access to the RDM to utilize offhost snapshot backups. My questions are: a. - Why can't I backup the RDM disk with a VMWare policy? b. - Can I backup the OS filesystem with a VMWare policy and the RDM disk with an alternate client so I can utilize offhost snapshots? c. Are there any differences if the RDM disk is physical or virtual?

  • Why can't I backup the RDM disk with a VMWare policy?

    Simply because VMware snapshots don't work. Open vSphere Client GUI and see if you can snapshot the VM. So, this is a VMware limitation - not NBU.

  • This is what I've decided to do. VSphere is only a passthru for the physical RDM. I'm going to backup the VM with a VMWare policy from the datastore and backup the attached RDM space from within the VM. The manual says to use the alternate client method to backup the RDM space, but I don't see how I can associate that space with the primary client name when it comes time to recover it if I ever had to.

  • There is an appendix B in the NetBackup for VMWare Guide that talks about different ways to protect the RDM disk.

    One of these methods is to install NBU inside the VM and use a MS-Windows or FlashBackup-Windows policy type.  The other is to use an alternate client backup.
    I have not done the latter so cannot describe to you what that looks like.  During a restore, you may have to restore the disk then manually add it back to the virtual machine.