habibalby

My name is Hussain with over 12 years of experience in IT field within Network Infrastructure, virtualization and datacenter operation. I'm a MCSA with Security, VCP3, VCP4, VCP5 and ITIL.

Homepage: http://dailyvmtech.wordpress.com

Migrating Veeam Backup 6.5.0.109 to another Physical Server


Migrating Veeam Backup 6.5.0.109 to another Physical Server

 I’m not going to make this post so complicated by explaining the bits and bytes of every step, but I’m listing below the steps in a very easy way;

  • Perform configuration backup on Veeam Server.
  • Install Veeam on the new physical server from scratch.
  • Import configuration that has been backed in step 1.
  • If you are using Veeam Backup to Backup Symantec Enterprise Vault, then you will have to install the Symantec EV Console on the new server in order to continue backing up Symantec Enterprise Vault. If not, you can ignore this step.
  • Move the scripts that run the Backup Jobs to the new Server, Export & Import.
      • Task Scheduler for all Backup Jobs Scripts;
        • Export & Import Tasks
        • Change Scripts path accordingly.
        • Re-enable the task scheduler in the new server.
        • Upgrade PowerShell to the latest version 3.0 WMI
        • Re-attach the Repository LUNs to the new server, and scan the Repositories to map the Backup Jobs.

, , ,

Leave a comment

Solution for Symantec Enterprise Vault when Unable to see the EV Toolbar in MS Outlook


Solution for Symantec Enterprise Vault when Unable to see the EV Toolbar in MS Outlook

Issue:

Unable to see the EV Toolbar in the Outlook after the Mailbox moved within Exchange Database Findings & Cause: -Found Event ID 3357 This mailbox cannot be processed until the Exchange provisioning task has processed the corresponding user’s details. Ensure that a provisioning group includes this user and run the provisioning task. To disable these warnings, set the ‘HideMissingPolicyInfoErrors’ registry value to 1.

–It appears Hidden message is corrupted in the Mailbox

Resolution:

- EV server Version 9.0.2

- Zaped user mailbox as per articlehttp://www.symantec.com/docs/TECH35614

[Directory] DirectoryComputerName = evserver.Domain.com Sitename =  EV Site [Mailbox] DistinguishedName =  /o=OrganizationName/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=MailBoxName [Folder] Name = Mailboxroot Zap = True

Run the EVPM tool in the command prompt.

Run Enterprise Vault Policy Manager (EVPM) from \Program Files\Enterprise Vault (or \Program Files (x86)\Enterprise Vault) on the EV server logged on as the Vault Service Account (VSA). The syntax for EVPM follows:

Symantec EVPM2

 
 
 
 
 
 
 
  • - Enabled Mailbox to be provisioned for Archiving.
  • - EV tool bar is appears now but VC sync button not available
  • -Checked Mailbox log, Mailbox is running in online mode not cached mode
  • -Enabled Mailbox Cache Mode [pre-request for Vault Cache]
  • -Restarted Outlook, Sync button appears now.

, , , , , , , ,

Leave a comment

Operation failed, diagnostics report: iScsi Adapter in unbound status, adding Static Target can not be done.


Hello,

You might see error in VMWare ESXi when LUN is created in EMC VNX3150 and you grant access to hosts that added to the VNXe3150.

Operation failed, diagnostics report: iScsi Adapter in unbound status, adding Static Target can not be done.

VNXe3150 Error in ESXi
This error is generated because EMC VNXe3150 try’s to add the iSCSI Servers/Targets that configured in the EMC VNX to each ESX that granted access to the LUNs. While the iSCSI Targets already added in the Dynamic/Static iSCSI Targets tab, this error is generated.

I think EMC should introduce some logic into the EMC VNXe3150 SAN Storage to initially check the Host if the iSCSI Targets already added, adding iSCSI targets via EMC should be ignored.

Or, VNXe3150 should loop through the storage pools/LUNs where it finds LUNs already presented to ESX hosts from the same Array, adding iSCSI Targets through EMC VNXe3150 should be ignored. Otherwise this fake error will keep presenting itself.

, , , ,

Leave a comment

Setting up & Configuring EMC VNXe3150 iSCSI SAN Storage with High.


Setting up EMC VNXe3150 iSCSI SAN Storage

Finally, the EMC VNXe3150 got installed and configured and almost ready to start transition from old EMC AX4 to the new VNXe3150. In the initial stage, found a bit difficulties to get it configured correctly as every EMC documentation speaks about something else specially when it comes to iSCSI High Availability, they mix between NFS HA and iSCSI HA. In reality, both Storage HA of NFS and iSCSI differ from each other. Simply, NFS uses Link Aggregations with LAG/LACP and iSCSI is not.

Equipment

  • VNXe 3150 with dual storage processors with software version 2.4.0.20932
  • Two Dell Stackable 6224 – 24 port Gigabit switches configured with Jumbo frames for iSCSI and Flow Control Enabled.
  • One – ESXi VMware ESXi 5.1.0 build-799733 host with 6 Gig pNIC’s two pNICs used for iSCSI connectivity only

Configuration on the VNXe

The configuration part is a bit of dilemma when it comes to iSCSI connectivity. In VNXe I set up two iSCSI Servers, one for Storage Processor A and one for Storage Processor B. Each SP has two IP Addresses configured for each Ethernet Interfaces, eth2 & eth3

iSCSI Server Settings-1

iSCSI Server Settings-2

iSCSI Server Settings-3

 

 

 

 

 

 

 

All the Ethernet Interfaces are configured with 9000 mtu size for Jumbo Frame;

MTU Config SPB

MTU Config SPB-eth3

 

 

 

 

 

 

 

Storage Resources Configuration

Storage Elements iSCSI Server Port IP Address MAC Address pSwitch Port VMKernel iSCSI PortGroup
iSCSI-A iSCSI_ServerA eth2 10.90.8.1 8:0:1b:57:71:3e 2/g1 iSCSI-01  10.90.8.78 vmk1
eth3 10.100.8.1 8:0:1b:82:78:dd 1/g1 iSCSI-02 10.100.8.78 vmk2
iSCSI-B iSCSI_ServerB eth2 10.90.8.2 8:0:1b:58:59:0f 2/g2 iSCSI-01  10.90.8.78 vmk1
eth3 10.100.8.2 8:0:1b:cd:f3:26 1/g2 iSCSI-02 10.100.8.78 vmk2

As you can see in the above screen shot and configuration table, each storage process have two Ethernet ports, each Ethernet port is connected to iSCSI pSwitch, eth2 in SPA matched eth2 in SPB. So since both of these interfaces are connected to the same pSwitch and same IP subnet is configured on both, single iSCSI VMkernel PortGroup on the same subnet can reach to both Storage Processors through single physical adapter “vmnic”

VNXe Connectivity Diagram

 VNXe Network Diagram

 

 

 

 

 

 

 

 

 

iSCSI Switches Configuration

Both network switches are configured as master and slave stackable switches, basically for this type of configuration you will not require to stack the switches as each of pair SP Ethernet are connected to the same switch. i;e SPA-Eth2 in pSwitch1 & SPB-Eth2 in pSwitch1. But with NFS configuration you will require to stack the Switches as you will need to configure LAG/LACP for true High Availability

Set up Jumbo Frames on the two iSCSI gig switches so that all the ports are using support Jumbo Frames. Below commands will let you configure all the ports with mtu size 9000

Console(config)#Interface range ethernet all

Console(config-if)#mtu 9000

ESXi host configuration

Each of the Gigs port in ESXi host is connected to the Physical iSCSI Switches. Two VMKernel PortGroups created in vSwitch1. Each of the iSCSI Kernels is mapped to the physical interface in ESXi.

Switch Name      Num Ports   Used Ports  Configured Ports  MTU     Uplinks

vSwitch1         128         8           128               9000    vmnic2,vmnic6

PortGroup Name        VLAN ID  Used Ports  Uplinks

iSCSI-02              0        1           vmnic6

iSCSI-01              0        1           vmnic2

vmk1       iSCSI-01            IPv4      10.90.8.78   255.255.255.0   10.90.8.255     00:50:56:6e:ea:87 9000    65535     true    STA                                  TIC

vmk2       iSCSI-02            IPv4      10.100.8.78 255.255.255.0   10.100.8.255    00:50:56:64:c0:6d 9000    65535

iSCSI vSwitch Ports

To check the connectivity is mapped correctly for each iSCSI PortGroup to reach the correct Ethernet Interface in the Storage Processor; vmkping with –I will allow you to specify the source interface to reach the destination iSCSI target; as this will test the whole path end-to-end from VNXe Storage, ESXi Hosts to Physical iSCSI Switches to make sure connectivity can flow with jumbo frame.

iSCSI Adapter Port Binding

Both iSCSI VMKernel portgroups has to be enabled for port bindings in the iSCSI Initiator adapter of ESXi.

iSCSI Port Bindings

 

 

 

Connectivity Results

# vmkping -I  vmk1 10.90.8.1 -c 50 -s 9000

PING 10.90.8.1 (10.90.8.1): 9000 data bytes

9008 bytes from 10.90.8.1: icmp_seq=0 ttl=255 time=0.596 ms

9008 bytes from 10.90.8.1: icmp_seq=1 ttl=255 time=0.575 ms

9008 bytes from 10.90.8.1: icmp_seq=2 ttl=255 time=0.548 ms

— 10.90.8.1 ping statistics —

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 0.548/0.573/0.596 ms

# vmkping -I vmk1 10.90.8.2 -c 50 -s 9000

PING 10.90.8.2 (10.90.8.2): 9000 data bytes

9008 bytes from 10.90.8.2: icmp_seq=0 ttl=255 time=0.591 ms

9008 bytes from 10.90.8.2: icmp_seq=1 ttl=255 time=0.617 ms

9008 bytes from 10.90.8.2: icmp_seq=2 ttl=255 time=0.603 ms

# vmkping -I vmk2 10.100.8.1 -c 50 -s 9000

PING 10.100.8.1 (10.100.8.1): 9000 data bytes

9008 bytes from 10.100.8.1: icmp_seq=0 ttl=255 time=0.634 ms

9008 bytes from 10.100.8.1: icmp_seq=1 ttl=255 time=0.661 ms

9008 bytes from 10.100.8.1: icmp_seq=2 ttl=255 time=0.642 ms

— 10.100.8.1 ping statistics —

5 packets transmitted, 5 packets received, 0% packet loss

round-trip min/avg/max = 0.634/0.661/0.708 ms

# vmkping -I vmk2 10.100.8.2 -c 50 -s 9000

PING 10.100.8.2 (10.100.8.2): 9000 data bytes

9008 bytes from 10.100.8.2: icmp_seq=0 ttl=255 time=0.694 ms

9008 bytes from 10.100.8.2: icmp_seq=1 ttl=255 time=0.658 ms

9008 bytes from 10.100.8.2: icmp_seq=2 ttl=255 time=0.690 ms

Add ESXi hosts to VNXe

Setup the ESXi hosts to access VNXe iSCSI SAN Storage. This can be done by browsing into the VNXe > Hosts > VMWare will allow you to find ESX hosts either by typing in the IP Address of the vCenter or the management network of the ESXi itself. Then create VMFS datastore on the VNXe and make sure you are assigning permission to the ESXi host to access the newly created LUN.

After the LUN is presented to the ESXi host and formatted with VMFS now it’s time to change the path selection through from default Fixed to Round Robin and change the Round Robin default IOPS limit in ESXi from 1000 to 1 which will allow you to utilize all the iSCSI paths.

esxcli storage nmp psp roundrobin deviceconfig set –type=iops –iops 1  –device=naa.6006048c2fb691695617fc52e06065a2

Once it’s change you will see all the paths with Active(I/O) for each LUN that changed from Fixed to Round Robin.

Path Round Robin

 

 

 

Failover – Failback Testing Scenarios

For the failover testing I have presented 500 GB LUN and created two Virtual Machines, and installed Windows 2008 R2 Enterprise Edition. Roles installed on this guest machine;

  • Microsoft Active Directory Role Services
  • Microsoft DNS Server Services
  • Exchange Server 2010 with all the Roles.

The second Virtual Machines are a Windows 7 Professional client with Microsoft Outlook 2010 connected to the Exchange 2010 MAPI profile. Sending and receive emails internally is operational in normal mode.

Testing Networking

I have tested failover with network issues scenarios by disconnecting one pNic “vmnic2” from the vSwitch1 that mapped to iSCSI-01 portgroup and at the same time vmkping –I vmk1 was running against both VNXe iSCSI Target IP’s SPA-Eth1 “10.90.8.1” & SPB-Eth2 “10.90.8.2” and ping continues well.  If a Storage Processor (SPA) fails/rebooted on VNXe, the working Storage Processor (SPB) picked up the workload that was handled by SPA.

Testing Networking-1

  • As you can see in the above screen shots, Virtual Machines Windows 7 Client continued pinging the Exchange Server and Exchange Server continued to ping Windows 7 Client.
  • Vmk1 = iSCSI-01 which mapped to vmnic2 stopped pinging to the SPA-Eth2 & SPB-Eth2.
  • LUN Paths both links mapped to vmnic2 subnet 10.90.8.x dead and 10.100.8.x paths mapped to vmnic6 ‘vmk2’ “iSCSI-02” are live and Active(I/O).

Path Round Robin-Failuer

 

 

 

 

 

Ping  “vmnic6” via vmk2 to 10.100.8.1 & 10.100.8.2

# vmkping  -I vmk2 10.100.8.1

PING 10.100.8.1 (10.100.8.1): 56 data bytes

64 bytes from 10.100.8.1: icmp_seq=0 ttl=255 time=0.229 ms

64 bytes from 10.100.8.1: icmp_seq=1 ttl=255 time=0.192 ms

64 bytes from 10.100.8.1: icmp_seq=2 ttl=255 time=0.238 ms

— 10.100.8.1 ping statistics —

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 0.192/0.220/0.238 ms

~ # vmkping  -I vmk2 10.100.8.2

PING 10.100.8.2 (10.100.8.2): 56 data bytes

64 bytes from 10.100.8.2: icmp_seq=0 ttl=255 time=0.235 ms

64 bytes from 10.100.8.2: icmp_seq=1 ttl=255 time=0.245 ms

— 10.100.8.2 ping statistics —

2 packets transmitted, 2 packets received, 0% packet loss

round-trip min/avg/max = 0.235/0.240/0.245 ms

Relink vmnic2 to vSwitch1 and ping resumed back to SPA-Eth2 & SPB-Eth2

ReLink vmnic2 vSwitch1

 

 

 

 

 

 

 

 

LUN paths resumed

Path Round Robin-Path Resumed

 

 

 

 

 

 

Testing Power Failure of VNXe Storage Processors-A & Storage Processor-B

The second test was done by removing the physical power from Storage Processor-B and initiate vmkping to both Ethernet Interface of SPB from both VMKernel vmk1 & vmk2, as a result vmkping continues as the traffic routed peer SP port.

Testing Power Failure

 

 

 

 

 

 

Result of ping after

Below result shows that Exchange VM continues to ping the Client VM during Storage Processor-B shutdown.

Result of Ping after SP-B Power Failure

 

 

 

Did the same with Storage Processor-A and initiated ping to both Ethernet Interfaces of SPA. Ping continues to both Ethernet Interfaces as well as pings inside each VM “Exchange Server to Client” and vice versa continues as well and Exchange Server VM didn’t give any freeze / errors in event viewer.

Conclusion

The VNXe3150 high availability feature at storage level and networking level ensures data protection against any single component failure in Storage Level and Networking Level.

, , , , , , , , , , ,

Leave a comment

Configuring NTP for VMWare vSphere Environment


NTP is a critical component in every network environment, especially when it comes to Virtualization. Because the entire Virtual Machines are relaying on the host to get the time. When the Domain Controller itself running as a Virtual Machine, cares must be taken of time synchronization between hosts, Virtualized Domain Controllers and other Virtual Machines.

In my environment, since the server vLAN has got access to the Public Internet, this wasn’t a big issue to get the synchronization done properly to the Domain Controllers.

Luckily, I have got two Domain Controllers one running as a Physical Server (PDC) and the second running as a Virtual Machine (ADC). In the initial stage, all the FSMO roles was configured on the Virtual Domain Controller, so the Virtual DC it’s holding the PDC emulator which is responsible for the domain hierarchy which means it’s responsible of the time service as well.

To get this done without the hassle of Time Protocols errors, below is the entire configuration.

  1. Backed up the Virtual DC with Veeam Backup & Replication”.
  2. Transferred the FSMO Roles from the Virtual DC to the Physical DC
  3. Configured the Physical DC to be responsible for the time service as per the MS article http://support.microsoft.com/kb/816042
  4. Configured the Virtual DC to obtain time from Physical DC.
  5. Now, since the majority of our servers are virtual running on VMWare vSphere the ESX configured to obtain the time from the same Physical DC
  6. In vSphere Client, configured the ESX with the Physical Domain Controller as NTP Server.
  7. Ran the ntpdate -q 192.168.10.20 in ESX Server against the Physical Domain Controller
  8. Restart the ESX NTP Service ” service ntpd restart”
  9. Then watch “ntpq -p” to watch time drift in ESX Console.
  10. Domain Members Virtual Machines has been configured not to obtain the time from ESX host, but it’s configured on other VMs that are not member of the Domain.
  11. The time is probably synchronized from the Internet to our Virtual and Physical Servers.

, , , , , , ,

Leave a comment

Steps to Upgrade Veeam Backup & Replication v6.1.x to v6.5.0.109


Hello,

I don’t want to go through a step by step procedure to upgrade from your current version of Veeam Backup & Replication to the latest version, but I would like to go through the procedure that I have followed in my environment and hope you will be benefit.

1. Stop Veeam Services.
2. Backup SQL Database
3. Upgrade SQL Express 2005 to SQL Express 2008 R2 by initiating this in the CMD SQLEXPR_x64_ENU.exe /action=upgrade
4. Once it’s done, start veeam Services.
5. Upgrade Enterprise Manager first if you are using it.
6. Upgrade Veeam Backup & Replication.
7. Launch Veeam Console and you will be prompt it with agent upgrade to upgrade the Repository Servers and Proxy Servers.
8. Just make sure everything is back to normal, jobs, logs, configuration run a job test to make sure everything is fine.

, , , ,

Leave a comment

Cannot add Windows PowerShell snap-in VeeamPSSnapin


You may encounter an error Cannot add Windows PowerShell snap-in VeeamPSSnapin when you run PowerShell scripts on Veeam Backup & Replication to start Backup Jobs after an upgrade from Veeam  Backup v6.x to v6.5

Symptoms:

  • PowerShell Scripts scheduled via Task Scheduler doesn’t start automatically.
  • If you run the script manually via Veeam PowerShell snap-in VeeamPSSnapin, you will receive an error. Cannot add Windows PowerShell snap-in VeeamPSSnapin. But the job will start.

Solution:

Upgrade to PowerShell 3.0 by installing Windows Management Framework 3.0 (http://www.microsoft.com/en-us/download … x?id=34595) which supports .Net 4.0 natively.

, , , , , , , ,

Leave a comment

Follow

Get every new post delivered to your Inbox.