Hi all,
Just started evaluating VeeamBR.
Configuration (Testlab)
ESXi hosts v4.0.1 (2)
Starwind SAN v5.2 (1)
Connected through 1Gb switch
Network
Enabled flow control & jumbo frames on:
ESXi vSwitches, vNics,kernel ports +
NIcs in VMs +
Ports of switch
Starwind SAN
VM's stored on Raid0 disk (4x WD RE 500Gb)
Veeam backup disk on Raid1 disk (2x WD Caviar black 640Gb), size .img 100Gb
Multiple iSCSI sessions (R/W for now) allowed on .img VM files and Veeam backup disk.
Veeam B&R v4.1.1
installed on VM
W2K8 with all fixes/patches/updates
2 vCPUs
4Gb memory
MS iSCSI initiator
Connection with source VM datastores
Connection with destination target
Problem:
- Not able to backup in SAN mode
Backup job log:
Backing up file "[W2K3Shares] W2K3FILE1/W2K3FILE1-flat.vmdk"
Unable to establish direct connection to the shared storage (SAN).
Please ensure that:
- HBA is properly installed in the Veeam Backup server computer, or software iSCSI initiator is configured correctly.
- SAN volume can be seen by operating system in the Windows Disk Management snap-in on the Veeam Backup server.
- Read access is allowed for the Veeam Backup server computer on the corresponding LUN (refer to your SAN documentation).
BackupDisk failed
Client error: Failed to open VDDK disk [[W2K3Shares] W2K3FILE1/W2K3FILE1.vmdk] ( is read-only mode - [true] )
Failed to open VMDK.
Logon attempt with parameters [VC/ESX: [10.16.0.40];Port: 443;Login: [administrator];VMX Spec: [moref=vm-534];Snapshot mor: [snapshot-1199];Transports: [san]] failed because of the following errors:
Server error: End of file
Backup in mode SAN/NBD end up fine, although slow performance (network).
- VM not powered on
Just set it up today, must be missing something with SAN mode.
Any suggestions?
Greetz Jaap
PS1.
Great performance with virtual appliance mode !!
PS2.
Had to install first:
Windows Powershell for Veeam B&R
Windows IIS 5+ with extra's for Veeam BEM
VMware View for FIle restore
Not mentioned in requirements as far as I 've read (Evaluation doc)
Especially missed the MS iSCSI initiator setup nessecity. Imo should be in the doc.
-
- Novice
- Posts: 8
- Liked: never
- Joined: Mar 09, 2010 8:58 am
- Full Name: Jaap Laaij
- Contact:
-
- VP, Product Management
- Posts: 27357
- Liked: 2788 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Not able to backup in SAN mode
Hello Jaap,
Actually all requirements are documented in the release notes document As for your issue please review the existing thread that should help you in setting up SAN mode: Configuring new VEEAM Backup Server for SAN
Thank you!
Actually all requirements are documented in the release notes document As for your issue please review the existing thread that should help you in setting up SAN mode: Configuring new VEEAM Backup Server for SAN
Thank you!
-
- Novice
- Posts: 8
- Liked: never
- Joined: Mar 09, 2010 8:58 am
- Full Name: Jaap Laaij
- Contact:
Re: Not able to backup in SAN mode
Hi Vitaly,
Thanx for you answer.
A novice mistake
It was right in front of me in the backup job log: "Failed to open VMDK".
Forgot to have a connected MS ISCSI connection towards the second disk.
Corrected it and backup was allright.
One question though.
In case of a VM with an attached (second) vmdk.
How can you see that both vmdk have been backed up
As far as I could find this is only possible if you start: Restore VM files
Greetz Jaap
Thanx for you answer.
A novice mistake
It was right in front of me in the backup job log: "Failed to open VMDK".
Forgot to have a connected MS ISCSI connection towards the second disk.
Corrected it and backup was allright.
One question though.
In case of a VM with an attached (second) vmdk.
How can you see that both vmdk have been backed up
As far as I could find this is only possible if you start: Restore VM files
Greetz Jaap
-
- Chief Product Officer
- Posts: 31773
- Liked: 7274 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Not able to backup in SAN mode
If some VMDKs cannot be backed up, the job will have error status (until it is able to backup all VMDKs). So if the job status is success, you do not need to check anything else. But of course you can always check backup content through Restore VM files.
Who is online
Users browsing this forum: Baidu [Spider], dwesterman, Google [Bot], Gregor and 61 guests