Netbackup warning when adding vmware clients with independent disks in backup
Created: 26 Jul 2012 | 1 comment
Netbackup should issue a warning when adding clients to vmware policies that have independent disk attached.
currently no error/warning is issued when backing up clients that have independent disk.
in a large environment backup admins might not have access to the vcenter or there might be a glitch in the transfer of information from vmware team to backup team and backups would complete successfull but be otherwise useless.
Idea Filed Under:
Comments 1 Comment • Jump to latest comment
Your idea is sound, but there is a way to proactively avoid this kind of situation
In our company in vCentre we created different folders for OS (UNIX/Windows)and within there different application folders (exchange,SQL, Oracle) and even your problem with independent disk which I'm assuming is Raw Device Mappings:
Folders would look something like:
DC-A-WIN-APP
DC-A-WIN-SQL
DC-A-WIN-EXC
DC-B-UNIX-ORACLE
DC-B-UNIX-APP
DC-B-UNIX-RDM
You could then use VMware intelligent policies to do this work for you. Configure them to look at these folders.
AND once a month you could configure an intelligent policy to identify which VM's have independent disk (RDM). This can at least let you know the VM's with RDM and check with your VM team that they have them in the correct folders until Symantec put in some kind of warning in the detailed status.
Would you like to reply?
Login or Register to post your comment.