Archive for May, 2012

Mounting Backup Item Failed with vPower NFS with Veeam Backup 6


When you try to mount a backup job with Veeam Backup & Recovery you will be promoted with an error Failed on Checking if vPower NFS datastore is mounted on host.

On vSphere Client, you will get a failed task on Create NAS DatastoreAn error occurred during host configuration” the error in the view details is “Operation failed, diagnostics report: Unable to resolve hostname” of veeam server.

Error after second attempt:

Solution:

Since my vSphere Infrastructure sets on different subnet other that my domain and where the Veeam Machine sets, I have to edit the etc host of the ESX hosts as well as the Veeam Machine.

Ping by name and IP successful and vPower NFS successfully mounted the backup image to the ESX host and started working fine.

Note: I used Veeam 5 with ESX 4.1 and I didn’t face this kind of issue. Since I have upgraded to Veeam 6 and ESXi5 U1, I started facing this issue.

, , , , , , , ,

Leave a comment

(DUP!) Duplicate Ping when you ping VMKernel PortGroup within ESX Host


Hello,

Have you ever encountered a duplicated ping when you try to ping the iSCSI PortGroups or pinging the ESX Host Itself from vCenter?

In my case I have this issue when I try to ping from ESXi5.0 host to an iSCSI Target.

SAN Storage Configuration:

IBM DS3512 with two Controllers, each with 4 iSCSI Ports.

CTRL-1:
Port-3: 10.10.30.1
Port-4: 10.10.40.1
Port-5: 10.10.50.1
Port-6: 10.10.60.1

CTRL-2:
Port-3: 10.10.30.2
Port-4: 10.10.40.2
Port-5: 10.10.50.2
Port-6: 10.10.60.2

When I try to ping each of the iSCSI Ports IP Address, I got

64 bytes from xxx.xxx.xxx.xxx: icmp_seq=4 ttl=128 time=0.xxx ms (DUP!)

ESX iSCSI Configuration:

vSwitch with 4 VMKernels PortGroup for iSCSI.

iSCSI-30 10.10.30.x

iSCSI-40 10.10.40.x

iSCSI-50 10.10.50.x

iSCSI-60 10.10.60.x

By default, vSwitch will take Route Based on the Originating port ID.

I resolved this issue by:

Changing from Route based on the Originating Port ID to Route based on IP Hash. And I set each VMKernel Port active on one nic only instead of two “Default”

VMNIC3 active for iSCSI-30 and iSCSI-40 because this NIC connected to Switch-1 as well as both iSCSI Ports.

VMNIC9 active for iSCSI-50 and iSCSI-60 because this NIC connected to Switch-2 as well as both iSCSI Ports.

(DUP!) has disappeared after doing this :)

, , , , ,

Leave a comment

(DUP!) Duplicate Ping when you ping VMKernel PortGroup within ESX Host


Hello,

Have you ever encountered a duplicated ping when you try to ping the iSCSI PortGroups or pinging the ESX Host Itself from vCenter?

In my case I have this issue when I try to ping from ESXi5.0 host to an iSCSI Target.

SAN Storage Configuration:

IBM DS3512 with two Controllers, each with 4 iSCSI Ports.

CTRL-1:
Port-3: 10.10.30.1
Port-4: 10.10.40.1
Port-5: 10.10.50.1
Port-6: 10.10.60.1

CTRL-2:
Port-3: 10.10.30.2
Port-4: 10.10.40.2
Port-5: 10.10.50.2
Port-6: 10.10.60.2

When I try to ping each of the iSCSI Ports IP Address, I got

64 bytes from xxx.xxx.xxx.xxx: icmp_seq=4 ttl=128 time=0.xxx ms (DUP!)

ESX iSCSI Configuration:

vSwitch with 4 VMKernels PortGroup for iSCSI.

iSCSI-30 10.10.30.x

iSCSI-40 10.10.40.x

iSCSI-50 10.10.50.x

iSCSI-60 10.10.60.x

By default, vSwitch will take Route Based on the Originating port ID.

I resolved this issue by:

Changing from Route based on the Originating Port ID to Route based on IP Hash. And I set each VMKernel Port active on one nic only instead of two “Default”

VMNIC3 active for iSCSI-30 and iSCSI-40 because this NIC connected to Switch-1 as well as both iSCSI Ports.

VMNIC9 active for iSCSI-50 and iSCSI-60 because this NIC connected to Switch-2 as well as both iSCSI Ports.

(DUP!) has disappeared after doing this :)

, , , , ,

Leave a comment

Cannot reach iSCSI target after enabling iSCSI port binding in ESXi5.0


Today I have encountered funny thing which kept me out of control trying to figure it out. In my environment my ESX Servers are connected to EMC AX4-5i and I configured an iSCSI Binding to achieve Round Robin Load Balancing..

I received a new IBM DS3512 and recently put the second controller to reply the EMC SAN Storage. In IBM  Storage manager I configured the host profile and created test LUN and presented to one of the ESX Hosts. I confirm everything is correct, I can ping the targets IP Address and i can ping ESX VMkernel IP Address but when I do a rescan, nothing is added. I was pulling my hair to figure out what is wrong.

It concluded that the previous iSCSI Binding is the issue. After removing both VMKernel PortGroups that binded to the VMHBA41 and did a rescan the IBM iSCSI Target detected and LUN appear.

In vSphere Client:

  1. Click Configuration > Storage Adapters > iSCSI Software Initiator > Properties > Configure.
  2. Select the Network Configuration tab.
  3. Select the vmk which is iSCSI compliant, then click OK.

Or you can use cli in command line;

esxcli iscsi networkportal add -A vmhbaX -n vmkY

Where X is the vmhba device number, and Y is the vmkernel port configured to access iSCSI storage.

, , , , , ,

Leave a comment

Integration Veeam Backup with Symantec Backup Exec 2010


Integration Veeam Backup with Symantec Backup Exec 2010

Introduction:

This document highlights some necessary steps required to setup a successful Veeam Backup and Symantec Backup Exec 2010 for tape integration and off-site storage.

Steps to a successful integration:

Veeam B& R v6.0.0.181 is installed on a Virtual Machine running guest operating system Windows 2008 R2 64bit with 8 GB of Ram and 2 Virtual vCPU Sockets and 4 Cores for each socket. The Veeam resources it depends on the environments and workload that put on the backup during backup operation.

All backup repositories’ are mapped through iSCSI Initiator with MPIO. The sizing of the repositories also it depends on each environment and how much data needs to be restored from disk and for how long. Again, this retention period plays a big role in the repository storage and how big your storage is.

In my environments, I have multiple targets;

No

Repository Target

Size

1. IBM iSCSI – DS3500 2.0 TB
2. IBM iSCSI – DS3500 745 GB
3. EMC iSCSI – AX4-5i 800 GB
4. OpenFiler iSCSI 2.3 1.4 TB
5. IBM iSCSI – DS3500 2.0 TB
Total 6.9 TB

Veeam Backup Configuration:

All the above repositories are added to the Veeam Backup & Replication v.6.0.0.181. Backup jobs configured for each VM to one of the above repositories.

Due to lack of disk space in the repositories and which limits the number of days  ofbacked up VMs should remain on disk, all the backup jobs are configured as follows;

Categorizing the backup jobs based on roles of the Virtual Machines helps a lot from backing up static Virtual Machines which doesn’t change very often.

No

Backup Category

Descriptions

1. Critical Virtual Machines Virtual machines are changing dynamically, such as Mail Server, file Server, Archive Server, Sharepoint, etc..
2. Non-Critical Virtual Machines Virtual machines are not changing on a daily basis, such as AntiVirus, Proxy Servers, WSUS, Deployment Serves

Critical Virtual Machines Job Settings:

Since those Virtual Machines are changing dynamically and daily, weekly and monthly backup requires for them backup job settings are configured based on the disk space and how long we can restore from disk.

Restore points to keep on disk: = 5

Deleted VMs data retention period: = 5

Backup Mode set as Incremental and Weekly Friday Active Full Backup. And schedule backup Sunday through Friday.

This settings result 1 Full Backup on Friday .vbk file and Sunday through Thursday is incremental which will gives 5 .vibs files.

Note: Since the Deleted VMs data retention period set to 5, CheckDataValue() when it reaches to 5 days, the full last backup chain will be deleted from disk and will have a new .vib file changed with last .vbk file.

Example:

Full Backup runs on 27th April, 2012 it will have a chain of Sunday through Thursday.

Week#1

No

Backup Date

Day

Backup Mode

1. 04/27/2012  02:43 VM001012012-04-27T143033.vbk Friday Full
2. 04/29/2012  02:37 VM001012012-04-29T143033.vib Sunday Incremental
3. 04/30/2012  09:42 VM001012012-04-30T093346.vib Monday Incremental
4. 05/01/2012  02:37 VM001012012-05-01T143039.vib Tuesday Incremental
5. 05/02/2012  02:37 VM001012012-05-02T143047.vib Wednesday Incremental
6. 05/03/2012  02:38 VM001012012-05-03T143029.vib Thursday Incremental

Week #2

No

Backup Date

Day

Backup Mode

1. 05/05/2012  11:18 VM001012012-05-04T143026.vbk Friday Full
2. 05/06/2012  02:36 VM001012012-05-06T143052.vib Sunday Incremental
3. 05/07/2012  02:36 VM001012012-05-07T143038.vib Monday Incremental
4. 05/08/2012  02:36 VM001012012-05-06T143052.vib Tuesday Incremental
5. CheckDateValue()
6.

When CheckDateValue() reach next week Wednesday, the previous backup chain will be deleted entirely.

Non-Critical Virtual Machines:

The same applies to the non-critical virtual machines backup jobs, except those backup jobs are set to 1 for both values, Restore points to keep on disk:= 1 && Deleted VMs data retention period:= 1.

This will allow only one restore point on disk.

Symantec Backup Exec 2010 Configuration:

All traditional backup software, the well-known backup methods are Full, Incremental or Differential. With Symantec Backup Exec 2010 and Veeam Integration there is a caution in here to select which backup methods to use when you Backup the Veeam Images *.VBK or *.VIB files.

In Symantec when Full Backup is configured to backup Veeam Images it will Backup everything on the drive and will reset the file Archive Bits.

When Veeam Backup runs again and created a VIB file or VBK file and again Symantec Runs as Incremental against veeam files, only the last changed files will be backed up.

But, when Symantec Full backup runs against Veeam, it will backup everything on the drive, means all Full *.VBK Files along with all *.VIB files. This increase the possibility of taking long time to finish the backup as well as doubling the backup twice.

The best option in here to backup Veeam Image using Symantec is to set all the backup methods as Incremental with Reset-Archive-Bit including Daily, weekly and Monthly Backup.

Also, Since Veeam Backup & Replication doesn’t have the option to set a monthly Backup, the last Wednesday of Last Week in the month can be considered as monthly backup and again the Backup Method has to be Copy otherwise backup will not backup anything to tapes because the Archive-Bit has been reset already.

In my example, Wednesday is my CheckDateValue() that configured on the Veeam backup jobs. So, all previous chain will be deleted.


, , , , ,

12 Comments