• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1601
  • Last Modified:

veeam backup

I have installed a New Terminal server (terminal server 3) with windows 2008.
Today i got a Warning notification:
Backing up object "[Terminal3] terminal3/terminal3.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).

Direct SAN connection is not available, failing over to network mode...

Please Help...Is there something wrong?
0
apollo-13
Asked:
apollo-13
  • 4
  • 2
1 Solution
 
PaulNSWCommented:
it just means Veeam cannot connect directly to the storage connected to your terminal3, so is failing over to network backup (slower)  Your backups are still taking place.

Have you presented the new Terminal3 LUN to all VM hosts, more specifically the host running Veeam as well?  Veeam must be able to see the LUN to backup direct from SAN.
0
 
apollo-13Author Commented:
Yep They are on the diffrent LUN.I mean
VEAM Server -LUN02
Terminal 3 -Local Drive

How can i change Terminal 3 Lun from Local To LUN2 Paul? or do i need to open new question for that?
0
 
PaulNSWCommented:
ok, by the sound of it your Veeam is running in a VM, stored on the SAN. It's backing up other VMs also stored on your SAN.

You have just created a Terminal3 server, it's stored on the local hard disk of an ESX host.

If this is correct, to back up Terminal3 server using the "direct connection", you will need to move the VM to the SAN.

You can use Storage vMotion if you have that license (and are using VMWare!)
If you don't have that feature licensed, you can also just use Veeam's "Migration" option
to copy from the local storage, to an appropriate SAN LUN.  You will need to remove the orginal VM from the Inventory, then once copied, Browse the LUN, right click the VMX file and Import back in again.
0
[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

 
apollo-13Author Commented:
ok, by the sound of it your Veeam is running in a VM, stored on the SAN. It's backing up other VMs also stored on your SAN. CORRECT

You have just created a Terminal3 server, it's stored on the local hard disk of an ESX host. CORRECT

If this is correct, to back up Terminal3 server using the "direct connection", you will need to move the VM to the SAN. CORRECT

You can use Storage vMotion if you have that license (and are using VMWare!)---YES I HAVE
If you don't have that feature licensed, you can also just use Veeam's "Migration" option
to copy from the local storage, to an appropriate SAN LUN.  You will need to remove the orginal VM from the Inventory, then once copied, Browse the LUN, right click the VMX file and Import back in again.
0
 
apollo-13Author Commented:
thanks Paul -I will try
0
 
apollo-13Author Commented:
perfect
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now