EMC-NETWOKER backinit HANA BACKUP RESTORE 19.X HANA 2.>=0

 

This Blog explain the restore steps of using backint from Dell EMC netwoker software

Expample:

Source machine name: s4hhdb1
Source Bakup pool: S4HPRD
Source tenant DB: SH1
Target machine name: testdbr2
Backup media server name: emcbackup137
Target tenant DB: SH1

FQDN= yoonus.local

 

The following  Changes to be made in source client GUI.. login Networker
> select source> modify the property t go to global2 add target machine host name, IP FQDN for full permission of access ( Full Permission= *@* )

 

Changes in Target machine (.utl)Files

Go to Target machine ( initSID.utl) file location and edit the file /usr/sap/TST/SYS/global/hdb/opt

 

##NSR_CLIENT=testdbr2.yoonus.local( target)
NSR_SERVER=emcbkp137.yoonus.local
NSR_CLIENT=s4hhdb1.yoonus.local ( source Client name)
NSR_RECOVER_POOL=S4HPRD (update source machine backup pool, the backup which need to restore from)
NSR_PARALLELISM=20
NSR_DEBUG_LEVEL=9
NSR_DPRINTF=true
NSR_DIAGNOSTIC_DEST = /nsr/applogs ( keep more space for this path)
NSR_DATA_VOLUME_POOL=TEST (optional)

 

Opt Location Files: /usr/sap/SID/SYS/global/hdb/opt
Following files should be in opt location: ( give full permission)
hdbbackint
initSID.utl
nsrsapsv.cfg

 

(nsrsapsv file details)

DATABASES=SYSTEMDB,TST (tenantdb)
HANA_BIN=/usr/sap/TST/HDB00/exe
HANA_DYNAMIC_PREFIX=FALSE
HANA_INSTANCE=00
HANA_MDC=TRUE
HANA_SID=TST
TENANT_ADMIN=FALSE

 

 

CHANGES IN HANA STUDIO SOURCE AND TARGET

Apply the below parameters based on respective source and target( HANA parameter in studio)

Global.ini>>backup>>

Catalog_backup_parameter_file = /usr/sap/SID/SYS/global/hdb/opt/initSID.utl
Catalog_backup_using_backint= true
Data_backup_parameter_file= /usr/sap/SID/SYS/global/hdb/opt/initSID.utl
Log_backup_parameter_file= /usr/sap/SID/SYS/global/hdb/opt/initSID.utl
Log_bakup_using_backint= true
Parallel_data_backup_backint_channels= ( based on sessions you need for fast restore)

 

HANA STUDIO CONSOLE STEPS
——————————

Restore select as tenant database

select :Recover the database a specific data backup

select: Search for the backup catalog in backinit only

Tick: Backinit system copy

SH2@SH2

DB will restart

after it will fetch the available backup logs to select and restore.

ALTER SYSTEM RECLAIM LOG;

 HANA LOG RECLAIM

TO STOP GENERATING LOG  FOLLOW THE STEPS

TAKE BACKUP OF DB

run below script to see the status of log  from tenant and Db

select b.host, b.service_name, a.state, count(*) from "PUBLIC"."M_LOG_SEGMENTS" a join"PUBLIC"."M_SERVICES" b on (a.host = b.host AND a.port = b.port) group by b.host, b.service_name,a.state;

if result show free recalim the log

ALTER SYSTEM RECLAIM LOG;

BAJUO LOG PATH  /usr/sap/SID/HDB01/backup/

set BELOW PARAMETER as below paramter to stop generating logs

log_mode = no

enalbe_auto_log_backup = overwrite

How do you cancel a running backup in HANA

 

Sunday, 25 August 2019

How do you cancel a running backup in HANA

To cancel a running backup, please use the following 3 SQL statements in HANA studio:

1. Get the backup_id of your running backup:

select BACKUP_ID from "SYS"."M_BACKUP_CATALOG" where entry_type_name = 'complete data backup' and state_name = 'running'  order by sys_start_time desc

2. Cancel the backup

backup cancel <backup_id>

3. Confirm the backup has cancelled

select state_name from "SYS"."M_BACKUP_CATALOG" where backup_id = <backup_id>

4. Check to  make sure there are no running backups still

select * from  "SYS"."M_BACKUP_CATALOG" where STATE_NAME = 'running';

If the backup still exists, you can try to cancel the thread through the commands:

ALTER SYSTEM CANCEL SESSION <Session_ID> ;

ALTER SYSTEM DISCONNECT SESSION <Session_ID> ;

From backend Linux

1. As per the SAP Note 2452735 confirm there are no backup currently running.

select * from "SYS"."M_BACKUP_CATALOG" where STATE_NAME = 'running';

2. Run the ps command to get the listing of zombie hdbbackint processes belonging to the database backup

ps -ef | grep hdbbackint | grep COMPLETE

Sending signal 9 using the "kill" command will destroy the process running on the client. 

kill -9 PID

where PID is the process id of the zombie hdbbackint process. 

You will need to be a root user to execute the kill command

FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()

 

Environment

SUSE Linux Enterprise Server for SAP Applications
SUSE Linux Enterprise Server 12

Situation

In the logs there are entries like

018-06-28T03:45:42.719624+02:00 unsinkable_02 lrmd[40931]:   notice: rsc_SAPHana_HAL_HDB00_monitor_61000:211324:stderr [ Error: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen() ]

and the SAP Instance cannot be operated by the Cluster for example.

This can affect normal SAP Instances like ASCS/ERS as well as HANA.

Resolution

Most likely reason for this is that the sapstart service is not running, it can be checked via

   unsinkable_02:~ # /bin/systemctl --no-pager --all list-units | grep sapinit

     sapinit.service        loaded    active   running   LSB: Start the sapstartsrv

or


     sapinit.service        loaded    active   exited   LSB: Start the sapstartsrv

and in case this returns something like

   sapinit.service       loaded    inactive dead      LSB: Start the sapstartsrv

   sapinit.service          loaded    failed   failed    LSB: Start the sapstartsrv

this can be fixed with

   unsinkable_02:~ # /bin/systemctl restart sapinit.service

Cause

The process sapstartsrv which is used for operating the SAP Instances was either killed, stopped or otherwise not available

Not able to open 'Memory Overview' Editor

Symptom

• When you choose the option, "Open Memory Overview" under system context menu in HANA studio, below error appears in the studio.
• Error while opening 'Memory Overview' editor; Reason: You do not have the required privilege.

Environment

SAP HANA Revision 70 and above

Reproducing the Issue

1. Open HANA studio
2. Run "Open Memory Overview" under SYSTEM menu
3. You face the error: "Error while opening 'Memory Overview' Editor."

Cause

The user is missing a privilege which is "sap.hana.admin.roles::Monitoring"

Resolution

You can execute statement below in HANA Studio.

call GRANT_ACTIVATED_ROLE('sap.hana.admin.roles::Monitoring','<userName>');