Install SAP HANA into a VM in less than 3. Scenario You want to prototype something and you dont have the hardware available for a new prototype HANA database. Instead, you can use the power of a virtual machine to get a HANA SPS0. Well, it was supposed to be 3. As I found out, working on a slow disk, limited CPU system, extended this to 2 hours from start to finish. Heres how. Update 0. SPS0. 8 rev 8. 0 then this will also work, but people have had issues trying to perform the install with the media converted to an ISO. Instead, just use the VMWare Shared Folders feature to share the install files from your PC into the SUSE VM. What youll need SAP HANA In Memory DB 1. SPS0. 7 install media from SAP Software Download Centre. This is media ID 5. The SUSE Linux for SAP v. ISO. A valid license for the HANA database platform edition or enterprise edition. SAP HANA Studio rev 7. PC which can access the virtual HANA server youre going to create the Studio install media is contained within the HANA install media DVD, or you can download it separately. A host machine to host the virtual machine. You need at least 2. GB of RAM, although if you configure your pagefile in Windows on SSD or flash, you could get away with 1. GB I did. What were going to do Well create a basic SUSE Linux for SAP virtual machine. You can use any host OS, Im using Windows 7 6. Because most people are using VMs to maximise infrastructure, well go through a couple of steps to really reduce the OS memory footprint we disable X1. We get this whole thing running in less than 1. GB of RAM in the end. Well install a basic HANA database. We disable the XS Engine saving a lot of memory which you dont have to do if you absolutely need it. The XS Engine is a lightweight application server for hosting the next generation HANA based APPS. START THE CLOCK Create your basic VM for SUSE Enterprise Linux Im using SUSE Linux for SAP SP2. It will need the following resources More than 1. GB of RAM preferably 2. GB on the physical host machine. 8. GB of disk for the OS. 5. GB of disk for the basic HANA DB with nothing in it, plus the installed software. 2. GB of disk on the physical host for swapping if you dont have 2. GB of RAM. 2 CPUs if you can spare the cores. A hostname and fully qualified domain name. Some form of networking use Bridged if you need to access this across the network. Lets create the VM and set the CDROM to point to the SUSE Linux SP2 install DVD ISO file Confirm the VM full name, your username and your preferred password for the username and for root Set the location to store your VM files Set the initial hard disk to have 8. GB and store it in one big file its up to you really Now customise the hardware Set the RAM to 2. GB or more you really need 2. GB of RAM, but I have only 1. GB and will be ready for some serious swapping. At a minimum the VM should have 1. GB of RAM for day to day running Give the VM at least 2 cores Use bridged networking if you need to access over the network, but only if you have DHCP enabled or youre a network guru Start the VM. Were off. The SUSE install took 1. Oh look, it reckons that we have 1. Boom, SUSE is up Shutdown the VM again so that we can add the second hard disk Its SCSI as recommended We set it to max out at 5. GB set yours however large you think you will need it, but we will create this in a volume group so you can always add more hard disks and just expand the volume group in SUSE NOTE If youre going to be moving this VM around using USB sticks, you may want to choose the Split. option so that the files might fit. Give the VMDK a file name Ive added HANADB so I can potentially plug and play this disk to other VMs Also re add the CDROM drive mine went missing after the install, probably due to VMWare players Easy Install process Configure the CDROM to point to the ISO for the SUSE install DVD again. Start the VM again Notice the Kernel version we have is 3. From the bottom bar in SUSE, start YAST and select the Network Settings item Disable IPv. Global Options tab On the hostname tab set the hostname and FQDN Apply those changes and quit from YAST. Right click the desktop and open a Terminal Add your specific IP address and hostname fqdn plus the short hostname to the etchosts file using vi Save the changes to the file and quit vi. Reboot the HANA VM from the terminal using shutdown r now. Once it comes back up, you need to check the hostname resolution According to the HANA installation guide Im following, we need to apply some recommended settings following SAP note 1. So we run the command to disable the transparent huge pages. I checked the C state and it was fine on my Intel CPU. Were not using XFS so I dont need to bother with the rest, I dont want to patch my Glib. C, but feel free to if you wish. MINUTES HAVE NOW ELAPSEDTCP Ports TCP 0 Reserved TCP 1 Port Service Multiplexer TCP 2 Management Utility TCP 3 Compression Process TCP 4 Unassigned TCP 5 Remote Job Entry TCP 6. This post is a cheat sheet for most of what I think the DB2 database administrator needs to know about Symantec NetBackup as a DB2 backup, recovery and log archival. Tcpip102449151 registered port numbers. A quick recap, we should have working SUSE VM, it should be booted and you should have the SUSE DVD loaded in the virtual CDROM. Open a new Terminal window Now install the following Java 1. HANA install guide for sp. SLE 1. 1 SP2 SAP DVD x. The rest of the requirements are already installed in SUSE EL 1. SAP. Now we create the volume group for the HANA database and software. First check which disk youre using for the OS So, Im using sda as my primary disk. This means that sdb will be my HANA disk. WARNING Adjust the commands below to the finding above, so you use the correct unused disk and dont overwrite your root disk. Create the new partition on the disk. Then enter n lt return p lt return 1 lt return lt return lt return t lt return 1 lt return 8e lt return w lt return At the end, the fdisk command exits. Re run fdisk to check your new partition Create the volume group and logical volume. HANA devsdb. 1 lvcreate L 5. M n lv. HANA1 vol. HANA. Format the new logical volume. HANAlv. HANA1. Mount the new partition. HANAlv. HANA1 hana ext. Check the new partition. Filesystem Size Used Avail Use Mounted ondevmappervol. HANA lv. HANA1 5. G 1. 80. M 4. 7G 1 hana. Create the required directory locations H1. H1. 0 hanalogH1. Now set the LVM to start at boot. Now weve got somewhere to create our HANA database and put the software. To perform the HANA install, Ive converted my downloaded HANA install media into an ISO file that I can simply mount as a CDDVD into the VMware tool. Instead of this method, you could alternatively use the Shared Folders capability and simply extract the file to your local PC, sharing the directory location through VMware to the guest OS. The outcome will be the same. Mount the ISO file HANA install media, from which Ive created an ISO for ease of use. You can do this by presenting the ISO file as the virtual CDROM from within VMWare. Open the properties for the virtual machine and ensure that you select the CDROM device On the right hand side, enable the device to be connected and powered on, then browse for the location of the ISO file on your PC Apply the settings to the VM. Prior to starting the install, we can reduce our memory footprint of the OS by over 1. GB. Use vi to change the file etcinittab so that the default runlevel is 3 no X windows Also, disable 4 services that are more than likely not needed and just consume memory Disable VMware thin printing. Disable Linux printing. Disable Linux auditing. Disable Linux e. Mail SMTP daemon. Disable SMBFS CIFS. Disable NFS you might need it. Disable splash screen. Disable the Machine Check Events Logging capture. Double check the IP address of your VM. Your IP address should be listed you can see mine is 1. If you dont have one, then your VM is not quite setup correctly in the VMWare properties or your networking configuration is not correct, or you dont have a DHCP server on your local network, or your network security is preventing your VM from registering its MAC address. Its complex. Assuming that you have an IP address, check that you can connect to the SSH server in your VM using PUTTY Enter the IP address of your VM server Log into the server as root From this point onwards, it is advisable to use the PUTTY client tool to connect, as this provides a more feature rich access to your server environment, than the basic VMWare console connection. You now need to restart the virtual server. Net. Backup Appliance Release 3. Description. Net. Backup appliance software version supports direct upgrades for appliance models 5. Note Net. Backup 5. Starting with Net. Backup appliance software version 2. Red Hat Enterprise Linux RHEL replaces the SUSE Linux Enterprise Server SLES operating system. Before you upgrade appliances with versions 2. For complete details, see the. Net. Backup Appliance Upgrade Guide Red Hat Enterprise Linux RHEL Operating System. For additional information about new features, product fixes and enhancements, known issues, and the current release content included in this software update, refer to the. Net. Backup Appliance Release Notes. Note The 3. 1 release update packages and the add on packages are not attached to this file. The following procedure includes links to the Veritas SORT website where the packages are located. TABLE OF CONTENTSProduct Dependencies. Downloading and Installation Instructions. Attachments. Product Dependencies. For appliances that are configured as a media server, this upgrade requires a Net. Backup Appliance 3. Net. Backup 8. 1 master server. Master servers must be upgraded before media servers. This release supports a direct upgrade from versions 2. For complete details about upgrades to version 3. Net. Backup Appliance Upgrade Guide Red Hat Enterprise Linux RHEL Operating System. After a successful upgrade, rollback from this version of Net. Backup appliance software is not supported. Before you begin the upgrade process, make sure that there are no backup jobs currently running or scheduled to run during the upgrade. During installation of this release update, all Net. Backup services and web services are shut down and restarted automatically. Make sure that the Net. Backup master server is turned on and running throughout the duration of the media server appliance upgrade. In addition, make sure that the Net. Backup processes are started on both the master server and the media server. Downloading and Installation Instructions. Note For this release, the server, client, and add on packages are located on the Veritas SORT website, along with a text file that contains the MD5 and SHA1 checksums. The following procedure includes links to access all of these items. The following procedure describes how to download and install the Net. Backup appliance version 3. Instructions are included for the server packages only. For client and add on packages, use the following link for downloading and installation instructions. Manually downloading Net. Backup appliance server packages. Perform this task from a computer that can access the Internet and can also communicate with the appliance. Internet access is required to download the release update files from the Veritas Support web site to the appliance. Due to the unique file name extensions of the split server packages, monitor your browser behavior closely during the file downloads. When you right click a file link and select. Save link as. or. Save target as., make sure that the file names retain the. For example. To download appliance software release updates using a CIFS or NFS share. Open an SSH session and log on to the appliance as an administrator using the Net. Backup Appliance Shell Menu. Open an NFS or a CIFS share by entering the following command. MainMenu Manage Software Share Open. Map or mount the appliance share directory as follows. Windows. Map the following appliance CIFS share on your computer. Windows systems prompt you for the admin user name and its corresponding password. UNIXMount the following appliance NFS share. This step describes downloading the upgrade package files and where to find the MD5 and SHA1 checksums. Click on each of the following links to download the split tar server files from the Veritas SORT website Click on the following link to a text file on the Veritas SORT website that contains the MD5 and SHA1 checksums Verify that the downloaded MD5 or SHA1 checksums match those in the text file on the Veritas SORT website. Use one of the following commands to join and extract the release update . Windowscopy b NBApplianceNlt release version. NBApplianceNlt release version. NBApplianceNlt release version. NBApplianceNlt release version. Note This command must be entered as one string. Make sure that the only space in the name is after . In addition, lt. Use Windows Win. RAR utilities to uncompress the NBApplianceNlt. The resulting files are as follows. SYMCNBAPPupdate lt release version. UNIX cat NBApplianceN. NBApplianceN. x. NBApplianceN. x. Note This command is one string. In this example, there is one space between each split package that is identified with a lt space. The resulting files are as follows. SYMCNBAPPupdate lt release version. Note To extract packages on UNIX systems, Veritas recommends that you use GNU tar version 1. See the following article for more information about extracting images. For UNIX systems, run one of the following commands to compute the checksum value for the. SYMCNBAPPupdate lt release version. SYMCNBAPPupdate lt release version. Verify that the checksum value matches the content of the update. Copy this release update. Note During the copy process, do not run any commands on the appliance. Doing so can cause the copy operation to fail. After you have successfully copied the release update. On the appliance, enter the following command to close the NFS and the CIFS shares. MainMenu Manage Software Share Close. Note If you run any of the following commands before you close the share, the downloaded release update or client package is moved from the share directory location to its proper location. However, you must still run the Share Close command to ensure that the NFS and the CIFS shares are closed. List Version. List Details All. List Details Base. Share Open. Share Close 1. To list the available release updates on the appliance, enter the following command and note the name of the downloaded files. MainMenu Manage Software List Downloaded. Running this command validates and moves the release update or the client package from the share directory to its proper location. You are not notified that this move has occurred. If the command shows a status of. Pending, wait a few minutes and try it again. To install the software release update, run the following command. MainMenu Manage Software Install SYMCNBAPPupdate lt. Monitor the preflight check and watch for any. Check failed messages. After the preflight check has finished, proceed as follows. If no Check failed messages appear, you are prompted to continue to the next step to start the upgrade. If any Check failed messages appear, the upgrade is not allowed. You must resolve the reported failures, then launch the upgrade script again so that the preflight check can verify that the failures have been resolved. Click on the UMI links V 4. If any Check failed messages indicate that a RHEL version third party plug in was not found, you must obtain the plug in from the appropriate vendor. Refer to the following topic for installation details Net. Backup Appliance Upgrade Guide for details. After all preflight check items have passed, you may need to trust the CA certificate and the host ID based certificate to start the upgrade process. To trust and deploy the CA certificates, do the following. Verify the CA certificate detail and enter yes to trust the CA certificate, as follows. To continue with the upgrade, verify the following CAcertificate detail and enter yes to trust the CA certificate. CA Certificate Details. Subject Name CNnbatdOUrootabc. Ovx. Start Date Jul 1. GMT. Expiry Date Jul 0. GMT. SHA1 Fingerprint 3. E9 9. 7 2. E 5. C D6 2. 5 7. F 3. D. 6. B D5 3. 3 5. C 1. 1 E2. Do you want to trust the CA certificateIf the security level of the master server is Very High, you must manually enter an authorization token to deploy the host ID based certificate on the appliance, as follows. Enter token. Note If the appliance is ever factory reset or re imaged after it has been upgraded to version 3. If the security level of the master server is High or Medium, the authentication token is not required. The host ID based certificate is automatically deployed onto the appliance. For more information about security certificates, refer to the chapter Security certificates in Net. Backup in the. Net.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |