& Configuring NetWorker to backup SAP HANA Published on December 25,2017 Bahadir Kiziltan Gartles +t Follow Principal Technology Consultant at Vertes Technologies LLC This is a quick guide to show how to configure NetWorker to backup a SAP HANA instance. The official docs published on this topic do not cover the crucial points needs to be handled. Here is the virtual lab environment I have to show how it goes... Notice that I use Data Domain as the device for data to be backed up.Instance ID: ERP While SAP HANA v1.0 SPS 12 is running on SuSE 12 SP2, I prefer to go with the most recent NetWorker version (9.2.1), which is fully supported as per compatibility list. NetWorker (Client Configuration Wizard) leverages "SAP Host Agent" to identify the instance names running on a SAP HANA host. So, the command below should return an output if executed as 'root' user,# /usr/sap/hostctrl/exe/saphostctrl -function Listinstances lnanal I Inst Info: ERP - 60 - hanab - 745, patch 35, changelist 1644855 Jhanah~ # Then check to see if required NetWorker packages (NetWorker Client for Linux and NetWorker Modules for SAP) are available on SAP HANA host. And be sure that 'nstexeed’ process is up and running. Jhanab:~ # rpm -qa | grep gto ligtonnsap-9.2.1.8-1.x86 64 figtocint-9.2.1.0-1, x86_64 - # :~ # ps -ef | grep nsr 1829 1 6 Dec22 ? 00:85:62 /usr/sbin/nsrexecd Now you would follow the steps below to have it configured. Launch NMC (NetWorker Management Console) and go to Protection tab. Right click on Clients to create a client resource through the wizard.Type SAP HANA hostname as client name. It's mandatory to use the hostname (better to put FQDN). Be sure that hostname/IP records are added to DNS or hosts file.Spec cent ntomation eee fees 3p pCortigraion ® ° ° ° ° The wizard automatically detects the operating system and the available NetWorker components installed on the host. Click on SAP HANA applicationto proceed. (lee eine Stage sec tt ° (oe) (i) (ore)Leave all options default. The "Client Direct" is super important feature that it allows SAP HANA host to access and write (also restore) directly to/from Data Domain system, over IP or FC.ooo8 i i i i Pick "Typical scheduled backup"...sect tne Contguraton pe ° Coal Ed Coe)If all goes well, you should be able to see the SAP HANA instance parameters having populated automatically. It's required to specify an user with appropriate rights to perform backup operations on SAP HANA instance. The SYSTEM user has it all by default.pean) te SA Hana nfomanon | | om | omen i Sey ne SAP HS ante ege @ cet aon @ cmccruane You would see the summary of the configuration based on the options selected.‘cent connguraton Surmary © sone te arin 2 SH Bene ontarn Oren © SiectheCrfpesten ips eosmesoeseriaik @ ote gain Sry omceseaaeOnce "Create" button clicked, the client resource should be successfully added to NetWorker.As the last step, copy the 'habbackin' binary, which is installed as part of the NetWorker Module for SAP (NMSAP), to the generic path. Just execute the following commands as 'root' user, mkdir -p /usr/sap/ERP/SYS/global/hdb/opt cp /usr/sbin/hdbbackint /usr/sap/ERP/SYS/global/hdb/opt Now you can create a Protection Group in NetWorker GUI and associate it with a Policy Workflow and start the workflow to initiate the backup jobs.Switch to SAP HANA Studio and launch the backup console. You should see the bars indicating that backup jobs are active. [Stis | | Rare) =o Lette Once it's completed, check the Backup Catalog tab to see the list of recorded backups (failed and succeeded state) performed on this intance.All done? Not yet. Up to here, we've completed mandatory configuration in case of triggering backup jobs via NetWorker. What if we also need to control backup operations through SAP HANA Studio? The HANA admins definitely consider using it.‘vere Coit] Bae 1 iy re syste Bay Staton of Carrenty Atve (Beckton orage storage shape There is a sample file called init_hana_nmsap.ut available under /ete as part of NMSAP package again. Copy it to a new file indicating the SAP HANA intance name. cp /etc/init_hana_nmsap.utl /etc/initERP.utl Edit the new one and seek for "nsx server" directive. Add your NetWorker Server hostname/FQDN and comment it out.HURSERAASHURDERANDHURDEAARSHONEEROASUURREAAREUNRDEAANSUAROEANSSUDROERUSLONRES MANDATORY PARANETERS (BACKUP AND RESTORE) HURSERANSAUREEAANSHAROERANSOREERUSSUORSESNSDUGROEASNSURROESISSUR ROE AUSIUGRER NSR_SERVER = nv9.hone. Lol] # NSR_SERVER: Default value: localhost + Valid value: The hostnane of the NetWorker server : Specifies the Nethorker server hostname to use for + backups and restores. And finally go back to Configuration tab in SAP HANA Studio and make the appropriate changes based on the variables and preferences in your environment. Remember to enable backint usage for automatic log backups.Now, we can also initiate backups from SAP HANA Studio. Report this