Deploying vcenter with VCSA (vcenter appliance) is like piece of cake, following are the requirement and steps to deploy vcenter 6.5

Prerequisites: –

1. Domain Controller: –

DNS record for vcenter should to created and DNS should be access from the computer where you will initiate deployment

2. Host name for vcenter
3. Ip address details (ip, gateway , dns)

Start Installation

1. Download the vcenter appliance from office VMware website
2. Mount the downloaded image to your computer
3. Browse the directory (H:\vcsa-ui-installer\win32)
4. Right client installer.exe and run as administrator

5. Accept the license and click next

6. I have selected the embedded as i have very less server to manage for ESXI, in huge environment platform service controller and vcenter can be install in separate machine

7. Enter the ESXI details where you are planning to deploy vcenter appliance and click next to processed

10. select the yes and processed with certificate warning

11. Now give Vcenter appliance name in my case I have select default only and provide the password to for vcenter appliance ( it is only appliance password) . select next to processed

12. no changes are required with size hence processed with next button

13. select the datastore to deploy the vcenter. I have select the local datastore with thin disk mode

14. assign the ip address configuration for vcenter and processed with next button

15. Review the provided details and processed with finish button

16. Relax and wait till deploying process complete, once the process completes client continue with further configuration

17. configure the SSO for local administrator as below

18. Review the summary and client finish to complete the installation

19. once the installation complete .log with    administrator@vsphere.local

Note: –

• just for reference, appliance reboot takes time,  I have seen sometimes it takes more than 30 minutes after adding domain to vcenter.
• How to join the vCSA to an active directory :- http://www.virten.net/2017/01/how-to-join-the-vcsa-6-5-to-an-active-directory-domain/

Step 1 -> install client on hana and configure a sap policy with no backup selection .

step 2 -> create node_names.txt file under location /usr/openv/netbackup/ext/db_ext/sap/ and mention the node name ( hostname ) in that. If multiple nodes are there than mention each node name top to bottom order.

step 3 -> edit the file /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle/initSAP.utl

mention master server name , client name  and policy name

step 4 -> linking backup script to hdbbackint

ln -sf /usr/openv/netbackup/bin/hdbbackint_script /usr/sap/BC3/SYS/global/hdb/opt/hdbbackint

If opt directory is not created than create it and link the hdbbackint_script.sh also give 777 permission to opt directory

step 5 -> mentioning config file location in HANA

HANA Studio Admin console -> Configuration -> global.ini -> backup

2 parameters are modified

data_backup_parameter_file   -> file name should be /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle/initSAP.utl

log_backup_parameter_file    -> file name should be /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle/initSAP.utl

>• Instance – Configuration – global.ini – backup – data_backup_parameter_file –>this should be location of initSAP.utl

>• Instance – Configuration – global.ini – backup – log_backup_parameter_file –> this should be location of initSAP.utl

>• Instance – Configuration – global.ini – backup – log_backup_using_backint –> should be set to True

In case of backup failure

>3. Backup Failure:

>• Verify Policy type is SAP.

>• Verify HANA Database is running.

>• Verify HANA Studio is configured and Database is accessible from HANA Studio.

>• Check the global.ini configuration parameters.

>• Verify that the node_names.txt file exist (/usr/openv/netbackup/ext/db_ext/sap/) on all nodes.

>• This file is created by the NetBackup administrator and should contain the names of all the nodes.

>• The node names should match the policy client.

To download the script

https://www.veritas.com/support/en_US/article.TECH209343