Configure / Modify the NTP Settings on Data Domain From CLI

In this post i will share you the procedure to configure or modify the NTP setting of a data domain from CLI .This procedure is very helpful for below scenarios

  • While Initial Configuration updated wrong time zone
  • Any NTP sync error on the Data Domain
  • Modify the NTP server

First we have to verify the NTP  configuration on the data domain .

Login to the data domain with admin privileges and check the NTP configuration by running below commands

# ntp show config                          -   To check the NTP Configuration .

# ntp status                                      -   To check the NTP Daemon status .

There might be Chance to show out put like below so we have to reconfigure / modify  the NTP services

Error 1

Status                                                  Enabled
Current Clock Time                         MM DD HH:MM:SS YYYY
Clock Last Synchronized                Unknown
Clock Last Synchronized With Time Server   Unknown
 Error 2

**** NTP daemon is not running.

# system show date                                          - To Check the current time in DD

# config show timezone                                 -  To check the current Timezone name 

How to Reset Time Zone

# config set timezone "Time Zone "

example  # config set timezone Asia/Dubai

Yo Check the Details of The time Zone Download Data Domain Admin Guide and View Page 41 49

How to Add NTP Server to Data Domain

# ntp disable

# ntp add timeserver <time server list>

For example: # ntp add timeserver 192.168.1.10

# ntp enable

How to Set Time Manually if  there is a Mismatch between NTP server and Data Domain

# ntp disable

# system set date <MMDDhhmmYYYY>               - Change DD time as of the NTP server:

Example to set system date/time to 0930 on 25th March 2018  the following command would be used:

# system set date 032509302018

** System date will be adjusted by xxxxxx seconds. This change can
potentially cause issues for applications running on this system.
Are you sure? (yes|no|?) [no]: yes
ok, proceeding.
Sun Mar 25 09:30:00 GMT 2018

# ntp enable

Note :- Incase the nEw Time is not  showing you may have to reboot the Data Domain  to apply the new timer

# system reboot

In case after following all the above steps the issue is not resolved or reboot is not possible at the time please contact your support provider


How to Install or Update the License on 3PAR Storage System

There are two Ways you can apply the license to 3PAR Storage one is from GUI and other is from CLI .
Before proceeding the steps make sure you have proper license file or license detils .You can obtain the license file from HP reseller or HP Portal or Hp Account Manager

In this post we are sharing information how can you apply license to you 3 PAR storage , follow below procedure

How to Apply License From GUI

Open HP 3PAR Management Console and Login

After Login On the Left pane you can see your 3PAr storage system

Right Click on the Storage System and select Set license

Once the License window opens you will have two option to add license , select the appropriate way and select the Agree to the terms and conditions and Click OK 

License File  - Browse the license file FILE.DAT which we received form HPE or Downloaded from HPE License Site

License Key  - License Key is a combination of numbers and letter you can copy form your source and paste there .

Once Apply the License you can Navigate to the software tab and check the license features from there .

 

 

 

 

 

 

 

 

You can check the License status from the CLI  by entering the command showlicense , check below image you can see before and after applying license difference

How to Apply License From CLI

Open the 3PAR Console using putty

Use the command setlicense to apply new license to upgrade

Once enter the set license command it will ask you confirm that agree to the terms and conditions by selecting Y for proceed to add license .

You can add the license keys on the CLI window and enter once again as empty line and license will applied

 

Click here to access the portal for HPE Licensing.

OR

Click here to access the portal for License Support Centers.


How to create zones from CLI on a Brocade SAN Switch

SAN zoning is a method of creating  logical groups over the physical configuration of the fabric and  allowing communication / access  of Fibre Channel devices by grouping  them .  And zoning manages  communication of hosts and storage nodes ,  zone contains WWN name of these devices . A World Wide Name, or WWN, is a 64-bit address used in fibre channel networks to uniquely identify each element in a Fibre Channel network.Normally everyone uses GUI for creating zone because looks very easy on GUI, but there is dependency JAVA with specific version. When we ran latest version java we will face difficult with GUI mode so we have to go with CLI. Here I describes the procedure that should be followed to configure zoning on a Brocade switch using the CLI.Follow the below procedure to create zone from CLI1.Run the switchshow command.

This will help you to identify the HBA address of both the target and initiator ports which will be required  for configuration.


admin> switchshow


Note:Any devices that connect using NPIV use nsshow command to find the WWPN addresses logged in to the port.If you cannot find the WWPN listing, you have to identify the WWPN manually from server / HBA and run “nodefindWWPN “ to verify that the WWPN is available on switch for zoning.

2.Run the cfgshowcommand


admin> cfgshow


cfgshow will display the configuration and how the zoning is currently configured. This will display two sections, Defined Configuration and Effective Configuration.

  • Defined Configuration – It is the section in which zones and aliases are listed. Any previously created zoning configurations that available are also displayed.
  • Effective Configuration – it is the current running configuration or configuration in production.

3.Run the alicreate command to create aliases for the HBA addresses that you identified by either running switchshow command or manually.


admin> alicreate "ALIAS_NAME", "WWPN"


Note :You can do this for both the Initiators and Target addresses

4.Run the zonecreate command to create the zone.


admin> zonecreate "ZONE_NAME", "ALIAS_NAME_OF_INITIATOR" 


Note :-  You may use  multiple alias's or single alias while creating zone  , multiple alias's can be added by "ALIAS1;ALIAS2"  , Also note that there should not be any space after zone name .

5.Run the zoneadd command to add the aliases of the Target ports to the zone that was created.


admin> zoneadd "ZONE_NAME", "ALIAS_OF_TARGET(S)"


6.Once zone is created, add it to an active configuration or a new configuration by running either the cfgadd command or cfgcreate


Add to an existing configuration   

admin> cfgadd "CONFIG_NAME","ZONE_NAME" 

Add the newly create zone to the configuration

admin> cfgcreate "NEW_CFG_NAME","ZONE_NAME"


7.Next you have to save the configuration by running the cfgsave And it will prompt for yes / no  you have to hit  yes at the prompt to save the configuration and this does not put the configuration into production


admin> cfgsave


 

8.To activate the created zoning, run the cfgenable And it will prompt for yes / no, you have to hit yes at the prompt to activate the configuration


admin> cfgenable CONFIG_NAME


Note: This will put the zone into the Effective Configuration and will be live in production.

Check More useful Commands on POST


Brocade useful Fabric OS Commands

This is a list of useful Brocade switch commands that will help you for administration or management operation. These commands are useful for for Zoning, Show, Port, Time/Date, License, Banner, Password, SNMP, User Config, Firmware, and Miscellaneous.

Zoning Commands

alicreate “Name”, “domain,port#” Used to create an alias
alicreate “Name”,”portname1; portname2″ To create multiple ports under a single alias
alidelete “Name” To delete an alias
aliadd “Name”, “domain,port#” To add additional ports to an alias
aliremove “Name”, “domain,port#” To remove a port from the alias
alishow “AliName” To show the alias configuration on the switch
zonecreate “Zone Name”, “alias1; alias2″ To create zones based on alias
zonedelete “ZoneName” To delete a zone
zoneadd “ZoneName”, “alias name” To add additional alias into the zone
zoneremove “ZoneName”, “alias name” To remove an alias from the zone
zoneshow “zoneName” To show the zone configuration information
cfgcreate “Configname”, “Zone1; Zone2″ To create configurations by adding in zones
cfgdelete “ConfigName” To delete a configuration
cfgadd “ConfigName”, “Zone3″ To add additional zones in the configuration
cfgremove “ConfigName”, “Zone3″ To remove a zone from the configuration
cfgshow “ConfigName” To show the details of that configuration
cfgenable “ConfigName” To enable a configuration on the switch
cfgsave To have the effective configuration to be written into the flash memory

 

Show Commands

 psshow Displays the status of the power supply
fansshow Displays the status of the fans
tempshow Displays the status of the temperature readings
sensorshow Displays the status of the sensor readings
nsshow Displays information in the name server
nsshow -t Displays information in the name server
nsshow -r Displays the information in the name server along with the state change registration details
nscamshow Displays detailed information of all the devices connected to all the switches in the fabric (Remote Name Servers)
nsallshow Displays the 24 bit address of all devices that are in the fabric
licenseshow Displays all the licenses that have been added in the switch
date Displays the current date set on the switch
bannershow Displays the banner that will appear when logging in using the CLI or web tools
httpcfgshow Displays the JAVA version the switch expects at the management console
switchname Displays the name of the switch
fabricshow Displays information of all the switches in the fabric
userconfig –show -a Displays the account information like role , description , password exp date , locked status
switchstatusshow Displays the overall status of the switch
switchstatuspolicyshow Displays policy set for the switch regarding Marginal(Yellow) or Down(Red) error status
portshow To show the port status
portcfgshow Displays the speed set for all ports on all slots and other detailed port information
configshow fabric.ops Displays the parameters of the switch. Ensure all switches in a fabric have the same parameters in order to communicate
configshow fabric.ops.pidFormat Displays the PID set for a switch Core , Native or Extended edge
switchuptime OR uptime Displays the uptime for the switch
firmwareshow Displays the firmware on the switch
version Displays the current firmware version on the switch
hashow Displays the status of local and remote CP’s. High availability , heartbeat and synchronization

 

Port Settings

portcfgshow Displays the port settings
portcfg rscnsupr [slot/port] –enable A registered state change registration is suppressed when a state change occurs on the port
portcfg rscnsupr [slot/port] –disable A registered state change registration is sent when a state change occurs on the port
portname To assign a name for a port
portdisable To disable a port or slot
portenable To enable a port or slot
portcfgpersistentdisable To disable a port , status would not change even after rebooting the switch
portcfgpersistentenable To enable a port , status would not change even after rebooting the switch
portshow To show the port status
portcfgspeed , To set speed for a port#te – 0:auto negotiated 1,2,4 Gbit/sec , 1 : 1Gbit/sec , 2 : 2 Gbit/sec , 4 : 4Gbit/sec
switchcfgspeed To set speed for all the ports on the switch Note – 0:auto negotiated 1,2,4 Gbit/sec , 1 : 1Gbit/sec , 2 : 2 Gbit/sec , 4 : 4Gbit/sec
portcfgshow Displays the speed set for all ports on all slots and other detailed port information
portcfgdefault To set the port settings to default
portcfglongdistance To set the long distance mode . Default is L0(Normal), as per distance will display LE <=10 kms , L0.5 <=25kms , L1 <=50 kms, L2<=100kms , LD=auto , LS = Static
portcfgeport Used to disable a port from being a E port

 

Time and Date Settings

date Displays the current date set on the switch
tsclockserver 10.10.1.1 Instruction for the principal switch to synchronize time with the NTP server (specify the  ip address of the NTP server)
tsclockserver LOCL Instruction to stop NTP server synchronization (Local time of the switch)
date mmddhhmmyy To set the time of the switch when the NTP server synchronization is cancelled
tstimezone -5 To set the time zone for individual switches

 

License Commands

licenseshow Displays all the licenses that are added in the switch
licenseadd To add a new license to the switch
licenseremove To remove a license from the switch
licenseidshow Based on Switch WWN

Banner Commands

bannershow Displays the banner that will appear when logging in using the CLI or web tools
bannerset To set the banner which will appear when logging in using the CLI or web tools
bannerset “” To remove the bannerset (two quotes)

 

Password commands

passwd To change the password for that particular login
passwdcfg –set -lowercase 3 uppercase 1 -digits 2 -punctuation 2 -minlength 10 -history 3 To set the password rules
passwdcfg –set -minpasswordage 1 To set the minimum password age in Days
passwdcfg –set -maxpasswordage 30 To set the maximum password age in Days
passwdcfg –set -warning 23 To set a warning for the expiration Days remaining
passwdcfg –set -lockoutthreshold 5 To set the account lockout thresh hold
passwdcfg –set -lockoutduration 30 To set the account lockout duration in Minutes
passwdcfg –setdefault To restore the password policy to Factory settings (min length – 8, history -1 , lockoutduration – 30)

 

SNMP Commands

 

snmpconfig snmpconfig for 5.0 above fos
agtcfgset snmp config for fos below 5.0
snmpmibcapset for choosing the MIB’s for the snmp settings

 

User Configuration

userconfig –show -a / userconfig –show Displays all the account information like role , description , password expiration date , locked status
userconfig –add john -r admin -d “John Doe” To add a new account -r = role , -d = description
userconfig –show john Displays all the information for the account john
userconfig –change -e no To Disable an account , usually default a/cs like admin and user . But ensure before disabling the admin a/c there is another a/c with admin rights
userconfig –change -e yes To Enable an account

 

Firmware commands

configupload Saves the switch config as an ASCII text file to an FTP server
configdownload To restore a switch configuration from ASCII text file Note – Need to disable the switch before downloading the config file
configure => cfgload attributes : [y] => Ensure secure config upload / download : [y] Fabric OS v 4.4 & above provides Secure File Copy Protocol (SCP) during upload or download of configurations
firmwaredownload To download the firmware to be installed on the switch
firmwareshow To be run after installing the firmware on the switch
version Displays the current firmware version on the switch
fastboot Needs to be run after installing the firmware. This does not include the post.
reboot Needs to be run after installing the firmware. This includes the post.

Miscellaneous commands

killtelnet To kill a particular session which is using telnet
configure To configure a switch
quietmode To switch off the quiet mode
quietmode 1 To suppress messages to the console
switchname Displays the switch name
switchname “EXAMPLE” To assign a switch name
bannerset To set the banner which will appear when logging in using the CLI or web tools
timeout Displays the timeout time set for Telnet session on the switch
timeout 10 To set a specific timeout time for the Telnet session
switchuptime or uptime Displays the uptime for the switch
switchcfgspeed To set speed for all the ports on the switch Note – 0:auto negotiated 1,2,4 Gbit/sec , 1 : 1Gbit/sec , 2 : 2 Gbit/sec , 4 : 4Gbit/sec
fastboot To reboot the switch without post
reboot To reboot the switch with the post
switchstatusshow Displays the overall status of the switch
switchstatuspolicyshow Displays policy set for the switch regarding Marginal(Yellow) or Down(Red) error status
switchstatuspolicyset To change the policy set for the switch regarding Marginal(Yellow) or Down(Red) error status

 


3 PAR Multipathing Best Practice with vSphere 6.5

Why Multipathing ?

To maintain a constant connection between a host and its storage, ESXi supports multipathing. Multipathing is a technique that lets you use more than one physical path that transfers data between the host and an external storage device.

In case of a failure of any element in the SAN network, such as an adapter, switch, or cable, ESXi can switch to another physical path, which does not use the failed component. This process of path switching to avoid failed components is known as path failover.

In addition to path failover, multipathing provides load balancing. Load balancing is the process of distributing I/O loads across multiple physical paths. Load balancing reduces or removes potential bottlenecks.

To take advantage of this support, virtual volumes should be exported to multiple paths to the host server. For this we have to create a host definition on the HPE 3PAR Storage system that includes the World Wide Names (WWNs) of multiple HBA ports on the host server and then export the VLUNs to that host definition. For an ESXi cluster, the VLUNs must be exported to all of the host definitions for the cluster nodes, or a host set may be created containing all of the servers and the VLUNs.

Setting Round Robin path policy

VMware vSphere includes active/active multipath support to maintain a constant connection between the ESXi host and the HPE 3PAR StoreServ Storage array. Three path policies are available,

Fixed (VMware)

The host uses the designated preferred path, if it has been configured. Otherwise, it selects the first working path discovered at system boot time. If you want the host to use a particular preferred path, specify it manually. Fixed is the default policy for most active-active storage devices.

Note
If the host uses a default preferred path and the path's status turns to Dead, a new path is selected as preferred. However, if you explicitly designate the preferred path, it will remain preferred even when it becomes inaccessible.

Most Recently Used (VMware)

The host selects the path that it used most recently. When the path becomes unavailable, the host selects an alternative path. The host does not revert back to the original path when that path becomes available again. There is no preferred path setting with the MRU policy. MRU is the default policy for most active-passive storage devices.

Round Robin (VMware)

The host uses an automatic path selection algorithm rotating through all active paths when connecting to active-passive arrays, or through all available paths when connecting to active-active arrays. RR is the default for a number of arrays and can be used with both active-active and active-passive arrays to implement load balancing across paths for different LUNs.

For HPE 3PAR storage, Round Robin is the recommended policy for best performance and load balancing; however, it may not be enabled by default. The path policies can be viewed and modified from the VMware vSphere Web Client on a per datastore basis as follows:

  1. In the vSphere Web Client, select the datastore.
    2. Select the Manage tab, then the Settings tab, and then click on Connectivity and multipathing
    3. Select one of the ESXi hosts and then click the Edit Multipathing button.
    4. In the pop-up window, select Round Robin from the Path selection policy drop-down menu.
    5. Click the OK button to save the new setting.
    6. Repeat steps 3 through 5 for each ESXi host.

 

Below Picture shows HPE 3PAR StoreServ Fast Class VLUN that has most recently used  and active IO only on one path .

Change the policy to Round Robin path  and check the status of “Active (I/O)" , it will be like below

 

Setting IOPS option for Round Robin policy

Managing a Round Robin I/O path policy scheme through the vSphere Web Client on a per datastore will not allow setting . We can modify the Round Robin policy details from command line on the ESXi host. To achieve better load balancing across paths,the --iops option may be issued on the command line to specify that the path should be switched after performing the specified number of I/Os on the current path. By default, the --iops option is set to 1000. The recommended setting for HPE 3PAR Storage is 1, and this setting may be changed as needed to suit the demands of various workloads.

Set the Round Robin policy for a specific device


# esxcli storage nmp device set --device <device-name> --psp VMW_PSP_RR


To set the device specified by --device to switch to the next path after 1 I/O operation has been performed on the current path


# esxcli storage nmp psp roundrobin deviceconfig set --type=iops --iops=1 --device <device-name>


Automating Round Robin policy for all LUNs

To automate this we have to edit the SATP rule or created using esxcli commands on the ESXi host to automatically achieve aRound Robin path policy for newly discovered LUNs.

Use the following command to create a custom SATP rule that will allow the ESXi host to configure the HPE 3PAR LUNs to use Round Robin multipath policy. The command must be executed on each ESXi host that is connected to the HPE 3PAR array.


#esxcli storage nmp satp rule add -s "VMW_SATP_ALUA" -P "VMW_PSP_RR" -O "iops=1" -c "tpgs_on" -V "3PARdata" -M "VV" -e "HP 3PAR Custom Rule"


Verify the new rule using the following command:


# esxcli storage nmp satp rule list | grep “3PARdata"


Note:New rule will be effective when adding new devices to the ESXi host, For existing LUNs, either a host reboot is required, or the path policy must be set for each LUN.

Reference


HP StoreVirtual Storage VSA Nodes Configuration

This post contains a series of Configuration Steps as mentioned below .

• Find the VSA and FOM from CMC Console
• Create New Management Group with FOM
• Create and Configure Cluster
• NTP and E-mail Notification Configuration
• Configure the Shared Volume

1. Open HPE StoreVirtual Centralized Management Console


Deployment of FOM (Failover Manager)

Use the Same file which used for Deployment of VSA Applianace

HPE_StoreVirtual_VSA_2014_and_StoreVirtual_FOM_Installer_for_VMware_vSphere_TA688-10544.exe

  • Ran this file as Administrator, it is a self-extracting one. After the extraction a CMD will comes up asking, if you want to use the GUI or CLI interface.

  • Chose the GUI wizard.
  • On the welcome page simply click “Next”.

  • Accept the License Agreement and Click Next

 

  • Provide hostname or IP address and login credentials for the target the vCenter server and click Next

  • Select the host name / IP address of the ESXI host from drop down menu and click Next

 

  • Select the HPE Storevirtual FOM as shown in the below image and click Next

  • Select the Data store and click next to install the Failover Manager (FOM)

Note: You must select the Storage that is not provided by the Storevirtual installation it is protecting.

  • Provide the Name for FOM, Select the NIC & input the IP Address and VM port group for communicating to Public Network and Click Next.

  • Give a name to the VM and to select the drive type

  • The wizard allows to deploy FOM.

Note: - There will be a pop-up message for before deployment as shown in the below image

  • Before you click Deploy check the settings of Appliance. If everything is fine, click the Deploy button. The deployment will start immediately

  • Deployment started and it may take few minutes to complete

Once the deployment is finished, Click “Finish”. Start the Centralized Management Console (CMC) and add the FOM nodes.

Continue PART 4  

See - Part 1  ,  PART 2  , PART 3  ,


HP StoreVirtual Storage VSA Installtion & Configuration - PART 1

Installing the CMC

Install the CMC on the computer or virtual machine that you use to administer the HP StoreVirtual Storage. You administer the entire network of StoreVirtual VSAs from this CMC.
To obtain the CMC, download the CMC installer from the following website

The CMC installation requires 63 MB disk space and 64 MB RAM during runtime. Installing the CMC in Microsoft Windows
1. Start the CMC installer.
2. Follow the steps in the installation wizard.
3. When the installation completes, HP is added as a separate Program Group and a shortcut icon is added to the  microsoft Windows desktop.
To start the CMC:
• Double-click the icon on your desktop, or
• From the Start menu, select
All Programs→HP →HP StoreVirtual→HP StoreVirtual Centralized Management Console

 

Installing the HP StoreVirtual VSA for vSphere

The HP StoreVirtual VSA for vSphere is pre-formatted for use with VMware vSphere. We have to install VSA on all the ESXi hosts.

Download the StoreVirtual OS 12.5 from below link .And follow steps mentioned below to install and Configure VSA on vSphere Host.

Required version of VMware

  • VMware vSphere 6.0 for LeftHand OS 12.5

Configuration requirements for the StoreVirtual VSA for vSphere

  • Virtual disk(s) with up to 64 TB (for vSphere 6.0) of space per disk located on internal disk storage, or any block storage that is on the VMware HCL: internal, external and shared. (Note that the LeftHand OS software consumes a small amount of the available space.)
  • StoreVirtual VSA for vSphere virtual disks must be configured as independent and persistent to prevent VM snapshots from affecting them.
  • The VMFS datastores for the StoreVirtual VSA must not be shared with any other VMs.
  • Microsoft NET 3.5 on the installer client.
  • vCenter servers properly licensed before connecting to them using the HP StoreVirtual VSA for vSphere installer.
  • When installing StoreVirtual VSAs that use more than 8 TB of datastores, increase the VMFS heap size. According to VMware, the VMFS heap size must be increased to access more than 8 TB of VMDKs in a VM. This means that a StoreVirtual VSA that uses more than 8 TB of datastores should have the heap size increased. See the following article for more information:

Reference KB

Best practices for StoreVirtual VSA for vSphere

  • Configure the StoreVirtual VSA for vSphere to start automatically and first, and before any other virtual machines, when the vSphere Server on which it resides is started. This ensures that the StoreVirtual VSA for vSphere is brought back online as soon as possible to automatically re-join its cluster.
  • Locate the StoreVirtual VSA for vSphere on the same virtual switch as the VMkernel network used for iSCSI traffic. This allows for a portion of iSCSI I/O to be served directly from the StoreVirtual VSA for vSphere to the iSCSI initiator without using a physical network.
  • Locate the StoreVirtual VSA for vSphere on a virtual switch that is separate from the VMkernel network used for VMotion. This prevents VMotion traffic and StoreVirtual VSA for vSphere I/O traffic from interfering with each other and affecting performance.
  • HP recommends installing vSphere Server on top of a redundant RAID configuration with a RAID controller that has battery-backed cache enabled. Do not use RAID 0.

Unsupported configurations for StoreVirtual VSA for Hyper-V

  • Use of Microsoft Live Migration, Quick Migration, or snapshots on the StoreVirtual VSA itself.
  • Use of any Hyper-V Server configuration that Microsoft does not support.
  • Extending the data virtual disk(s), the first SCSI Controller in Hyper-V, of the StoreVirtual VSA while in a cluster. Create additional disks and hot-add them instead.
  • Co-location of a StoreVirtual VSA and other virtual machines on the same NTFS partition.
  • Running StoreVirtual VSA for Hyper-Vs on top of existing HP StoreVirtual Storage is not recommended.

Deploying HP StoreVirtual

As mentioned above once you have completed the download from the webpage you may found downloaded File will be named like below

HPE_StoreVirtual_VSA_2014_and_StoreVirtual_FOM_Installer_for_VMware_vSphere_TA688-10544.exe

  • Ran this file as Administrator, it is a self-extracting one. After the extraction a CMD will comes up asking, if you want to use the GUI or CLI interface.
  • Chose the GUI wizard.
  • On the welcome page simply click “Next”.
  • Accept the License Agreement and Click Next

 

Continue  PART 2 

See - Part 1  PART 3  ,  PART 4  


HP StoreVirtual Storage VSA Installtion & Configuration

Continue of Part 1

  • Select the host name / IP address of the ESXI host from drop down menu and click Next

Note:-You may see the Datastore information form this window.

  • Select the HPE Storevirtual VSA and sub two options as shown in the below image and click Next

  • Select the Data store and click next to install the VSA appliance which the VSA should reside

  • Provide the Name for VSA – Appliance , Select the NIC , inut the IP Address and VM port group for communicating to Public Network and Click Next .This step covers the NIC setup of the VSA. Recommended to use two NICs for the VSA: One for management and a second one for iSCSI traffic .

  • Give a name to the VM and to select the drive type , Prefer same as Appliance DNS Name

Note: - Since there is no RDMs currently the option is greyed out.

  • Now we have to configure the data disks .This Data disks will be used for creating shared volume for ESXi hosts.

Note: - Also we can configure the Tiering, Select the Data store, Size and Tier, Tiering will be on differ type of disks like SSD, SAS or NL SAS. If have to use AO (Adaptive Optimization) Tiering should be configured. Refer # Step

  • Select No, I am done and click next , this option will deploy the Appliance

  • Before you click Deploy check the settings of Appliance. If everything is fine, click the Deploy button. The deployment will start immediately

  • Deployment started and it may take few minutes to complete.

  • Once the deployment is finished, Click “Finish”. Start the Centralized Management Console (CMC) and add the VSA nodes. If CMC already installed you may close the wizards else CMC is installed automatically by the wizard.

Continue PART 3 

See - Part 1  ,  PART 2 ,  PART 4  


vSphere Data Protection to Avamar Migration

This post provide information about how to migrate from VDP to Avamar.

VMware vSphere Data Protection (VDP) enables you to migrate backup and backup verification Job's configuration and data from VDP to Avamar. The Migration enables the backup group and virtual machines backup validation to be visible , and completely executable on the target Avamar server.

Below is the Support Matrix for VDP to Avamar Migration 

Configuration Prerequisites

Ensure that you meet or perform the below configuration Prerequisites

Successfully Deploy Avamar Server 7.3.1 and Configure it .

On the Avamar Virtual Edition (AVE), ensure that the value of Client-Server Communication and Authentication Type is Mixed/ Single by running the following command in the Avamar Console

enable_secure_config.sh -showconfig

Following Similar Output will appear

Register the source vCenter client to the target Avamar servrer

  •       Login to the Avamar MCGUI

 

In Avamar Administrator Login Wnidow type the same Avamar root credentails that you have speficed during the installation and Click Login

Then MCGUI appears as shown below

In Avamar Administrator Login Window type the same Avamar root credentials that you have specified during the installation and Click Login

Then MCGUI appears as shown below

  • Disable the Avamar Management Console ( MCS) Certificate authentication
  • Open command prompt and log in to the type of the server
    • Single node server - Login to server as admin
    • Multi-node server - Login to utility node as admin
  • Stop MCS by running following command

                                                   dpnctl stop mcs

  • open /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml file by using a text editor
  • In the mcserver.xml , set te value if the ignore_vc_cert key to true

<entry key-"ignore_vc_cert" value="true"/>

  • save the mcserver.xml file and close it.
  • Restart MCS by running by following below command

dpnctl start mcs

  • Restart the schedule by running the following command

dpnctl start sched

Add the vCenter Client

  • In the Avamar Administrator windows, click the button or icon that opens the Administration windows
  • In the Administration windows , on the Account Management tab ,Select the roor (top-level) domain  and then select the Action > Account Management > New Client
  • In the New Client dialog box , specify the follwoing fields and click OK
    • Client Type : Select vCenter
    • New Client Name or IP - Type the FQDN or IP of the vCenter
    • Port : Type the Port number of the vCenter web services listener ,Default value id 443
    • User Name: Type the Username of vCenter Client user account
    • Password : Type the password of the client user account
    • Verify the Password : Type the same password of the client user account you have typed in the password field
    • Contact,Phone,EMail and Location : Specify the optional fields as required .

Deploy the VMware image proxy on the target Avamr server and configure it.

  • Log in to Avamar MCGUI
  • In the Avamar Deploy Manager window , select the vCenter client , and click Create Recommendation
  • In the tree pane , reviw the VMware topology , and ensure that there are no recommended proxies that are labelled as new proxy
  • In the Proxy Deployment Manager window , locate and select the host :
    • Click New Proxy
    • In the New Proxy window , specify te Proxy Name, Domain Name , IP , Datastore , Network , DNS , Gateway and Netmask as required and click Save
    • Click Apply

New Proxy will be deployed and registered , if operation ails reclick Apply

Migrating the Backup Jobs From VDP to Avamar

Prerequisite

  • On the vDP Appliance , disable all the backup and automatic backup verification jobs
  • Replicate all the backups from the VDP appliance to the target Avamar server
  • The Creating a Replication Job and Running Exiting Replication Jobs Immediately sections in the vSphere Data Protection 6.1 Admin guide provide information
  • On the VDP appliance , apply the VDP migration hotfix
    • Copy the VDP-migration.tar file to the /tmp on the VDP appliance
    • Go to the /tmp directory and extract the vdp-migration-hotfix.tar file by running below command:
      tar-xvf vdp-migration-hotfix.tar
    • Go to the vdp-migration-hotfix directory ,which you have extracted,and run teh follwoing command
      sh vdp-migration-hotfix.sh
      Note: The replaced files are backed up to the location that the hotfix installer specifies in the execution logs

Migrating the Backup Jobs

Prerequisites

  1. Unregister the VDP extensions or plug-ins from vCenter Server
    • Log in to the vCenter Server by follwoing URL
    • https://<venter-server>/mob2.
  2.        2.Locate the content as shown in the following figure and click it
  3. Locate the com.vmware.vdp2 and com.vmware.vdp2.config plug-ins as shows in following figure
  4. Click com.vmware.vdp2.config for removal , following page will appear
  5. Note down the value of the plug-in key
  6. Go to previous page , and click Unregister Extension ,as shown un the following figure
  7. In the Window that appears , type the value of the plug-in key that you have noted down , and click invoke Method
    • The plug-in is removed
  8. Unregister or remove the com.vmware.vdp2 plug-in by follwoing the sub-steps of 5,6,7 and 8 step 1
  9. Refresh the plug-in page to ensure that both the plug-ins are unregistered or removed
  10. Refrsh the plug-ins page to ensure that both plug-ins are unregistered or removed
  11. Restart the vSphere client to see that the plug-ins are removed

 

  • On the VDP appliance , go to the /tmp/vdp-migration-hotfix directory and stop the Tomcat server by running below commands

sh stop-vdp-tomcat.sh

Note : After you stop the tomcat you cannot perfomr any operation by using VDP UI Install the Avamar 7.3.1 client and register the Avamar 7.32.to the Vamar 7.3.1 Server .

  • On the Avamar 7.3.1 client , install the package that is specific to the microsoft application plug-in
    Log in to the Avamar Administrator UI and enable the migrated backup verification jobs
  • The avamar server is ready for backup and restore operations