cancel
Showing results for 
Search instead for 
Did you mean: 

Specifying specific VMDK files to backup using the VMware Vstorage API with NetBackup 7.0

Reagan
Level 5
Partner Accredited Certified

When using the VMware Vstorage API with NetBackup 7.0, is there anyway to specify backing up

specific VMDK files in the backup selection list instead of backing up all VMDK files by default using (ALL_LOCAL_DRIVES)?

================================

Example of a Virtual machine with 2 VMDK files:

VMDK_1= Operating System

VMDK_2= Database

Is there a way with NetBackup 7.0 to specify to only backup VMDK_1 in the backup selection list using the Vstorage API? 

 

 

4 REPLIES 4

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

Hi,

 

To answer your questions, no, you cannot. When you use the "Full VM Backup" or "Mapped Full VM Backup" you can only backup ALL_LOCAL_DRIVES. Individual File System backup is only possible if you use VCB. See the attachment.

 

Secondly, if there are database on the VM you should use a client installed in the VM to perform the backup (using the appropriate Database agent e.g. SQL, EXCHANGE, ORACLE)

Tim_Hansen
Level 5
Certified

The OS level VMDK is always backed up in a vstorage backup call, since it's taking a system snapshot. You can choose to mark a datastore as independent in VMware to ensure it's not included in snapshots triggered by the vstorage API, but that is about as granular as it gets.

MOHAMED_PATEL
Level 5
Partner Accredited Certified

Using the APi, and backing up ALL_LOCAL_Drives, backs up all the required and relevant  'configuration' files required for the VM - the .vmx (VM descriptive configuration file, .nvram (VM bios).

Hence, backing up just a single file (see Riaan's note regarding this) is possibly an option with consideration to Tim's note.

Anonymous
Not applicable

Interestingly I've been testing an installation of VMwares Data Recovery appliance in my vsphere infrastructure (Free - conditions apply) and you can choose to backup selective VMDK's. Might not be for production use but interesting to use. Still in version 1.x phase. Interesting where they are going with this.