Sorry I can't help you but just for the information.
I've spent the whole day to googling and trying to find this wery same infromation. I'm also sucessfully runing BE2010 with "nbd transport mode" but want to use SAN mode instead. I've tried to get some support on symantec forum but no result yet https://www-secure.symantec.com/connect/forums/howto-config-vmware-agent-san-backup
I have Win2008r2, Powerpath 5.3-64bit, Emc clariions, Backupexec 2010 with vmware agent enabled, and vSphere 4.0
I've done the config like we did with vcb in older setups.
diskpart automount disable and diskpart automount scrub
I haven't presented the vmfs luns to the backup server yet just because it would be nice to have some kind of documentation of how it should be done and what the requirements are
Have someone seen documentation on this or information of how to get this stuff running ?
Message was edited by: chellquist becuse of realy bad typings
You can attach your windows machine to the SAN, no problem. Just make sure it will not format the LUNs or attribute drive letters to them, you can find information on how to do that and all the process here: http://www.vmware.com/pdf/vsphere4/r40/vsp_vcb_15_u1_admin_guide.pdf
About the BE2010 support, I am really not sure if it have support for the vStorage API, so I suppose you will need to install VCB. Anyway, if you already do nbd backups I think you will not need to install any additional software, just change the nbd do san mode.
VMWare Certified Professional 310/410
Technical Support Engineer
Consider awarding points for "helpful" and/or "correct" answers.
Yes I've read the vcb documentation and changed the default resignaturing behaviour in windows so it should be saft to connect. There isn't much about win2008r2 in the vcb documentation but I already found out that standard version still uses automount enabled as default.
BE2010 uses the vStorage API and that should exists a documentation or whitepaper of this I think.
I had the time to experiment a bit this morning and I was very successful.
Here's what I did:
- I've uninstalled VCB from my backupexec / vsphere server host (same machine)
- i've put one esx server into maintenance mode
- set VMware DRS to manual
- set up a new LUN in EMC, new Storage Group, and added the new LUN, the maintenance ESX-Server and the Backup-Server into that Storage Group
- rescan host bus adapter on the ESX host, create VMFS storage on the new lun
- exit maintenance mode on ESX host
- set up a dummy VM on this new lun, install windows or something (doesn't really matter, but i prefered to actually have something to backup)
- reboot your backup exec / vsphere box. make sure the LUN gets recognized in compmgmt.msc, but DO NOT initialize the disk or even dare of giving it a drive letter. Just look if its there, no other clickies...
- Set up a Backup Job in Backup-Exec. I've used a Full VMware Backup of the VM, only activated SAN transport mode...
... and it ran like a charm with speeds up to 4000MB/min.
I however still have the same problem that the Backupjob gets slower and slower the longer it lasts ... I'm currently backing up my exchange server (all disks are on the same LUN), and what started with 3300MB/min is now down to 1400-ish after two hours, still decreasing.
indeed! I've just checked the CPU load on the backup server and it's almost 100% (which is quite remarkable on a two cpu, 4 virtual cpus system). The server is an HP Proliant DL380 G4 and has two P4 3.6GHz Xeon CPUs with Hyperthreading, but no multicore and is about 5 years old ... It's soon to be replaced with an i7 based HP Proliant DL380 G6 which should then be able to handle the load.
Thank you for the testing performed! Looks that there is not much documentation available for this process. I had setup BackupExec to use SAN transport mode and felt like I had to share with the community, so this is officially my first post to a VMware forum :).
Anyway, let me share with you guys what I did and what was the result:
I am running: VMware ESX and vCenter 4.1. On the Backup side I have Symantec BackupExec 2010 SP2, or R2 like they are calling now. My VMs are stored on a HP MSA 2000 iSCSI storage.
To setup the VMs backup using SAN transport I kind of followed the steps previously posted. The idea of having a VMware LUN published to a Windows server scared me quite a bit, perhaps, I mapped the LUN as a "READ-ONLY" LUN, so it doesn't even allow Windows to activate, assign letters, anything. As far as I understand this is the safest way to go and it works fine.
I setup a backup job to use SAN transport, backed up my VMs to disc first. I could get an average throughput of 2.5 GB/min, not bad. After that I have a duplication job that sends the data to tape.
Actually, the setup was pretty straight forward and it is working fine. I will be doing some extra tests as the week goes on and will report any issues.
Anyone done a restore yet? One of the things I found out I absolutely hate about BE 12.5 is that it would restore the entire vmdk's to local disk and then afterwards run vmware converter to restore them into the vmfs volume.
Have any errors with the vmconverter and ti would delete the damn restored files and need to start the whole process over again.
I really hope they changed that in 2010...
I was able to do a backup using the guidelines posted above. However, I am not getting an error when backing up the BE server itself. Is anyone else getting this?:
- AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11226 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot provider selected returned: "Unexpected provider error". Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details.
The following volumes are dependent on resource: "C:" "
The volume in question is my unmounted iSCSI VMFS volume. Is this normal?
Also, I'm able to backup VMs when selected underneath the ESXi host. But when selecting the same VM underneath vCenter, I get an error:
VCENTER\VCGuestVm\(DC)Irvine(DC)\vm\TestServerV-79-57344-38277 - Unable to open a disk of the virtual machine.
VixDiskLib_Open() reported the error: Invalid connection handle
What am I missing?