HANA DB backup using HANA studio

what is contained in the backup file?

The data backup includes not only data, but also data structure that are required for restore of DB.

why to take backup on regular basis?

To save data during disk failures

Pre-requsites:

DB user with roles: Backup Admin
                                Backup Operator

                                Catalog read

Note: same roles are enough for performing the recovery of HDB also.

SQL query for check the backup size:

select sum (allocated_page_size) from M_converter_Stastistics

select volume id, sum (allocated_page_size) from M_Converter_Stasticstics) group by volume id,

based on the out put of the above query --> make space arrangements.

Process:

Method1

• Open HANA studio.
• select the correct system for backup amomgs all systems.
• Right click
• choose backup
• choose type as full / differential /incremental 
• specify the location and prefix for the backup file.
• conform 

Method 2

• Open HANA studio.
• login to system
• open hdbsql
• execute the query:

BACKU DATA USING FILE ('/usr/sap/<SID>/HDBXX/backup/data')

Spool administration notes 1

This KBA  describes for

1. how to manage printers?

2. how to define printers ?

3. how to define spool services?

4. How to define spool & output request ?
5. how to set up central printer administration ?
6. how to configure front end printer?

7. How to lock printer in case of any physical issue with printer ?

8. How to enable print immediately ?

9. T -codes of spool administration ?

10. troubleshooting output request?

Notes:

As in SAP Application level, have various documents are available in the form of smart forms, sales order, SAP scripts. etc.., 

these documents are different from each other, it can be PDF document,SAP script document, smart form document are processed every day in through SAP Application.

  * the output request is the conversion of spool request.

* Flow of Spool services in SAP:

     Document in SAP Application --> spool request --> output request.

* It is possible to generate more than one output request for the same spool request.

    eg: in case of any physical problem with the respective printer.

* Spool request will generate , independent to the printer setting.

* temse - temporary sequence object.

* RZ11 --> rspo/store_location  --> describes the location of spool data.

                                                   --> spool data can be maintain in either DB or file system 

Database tables for spool administration :

* TST01 table for header data  of temse.

* TST03 table for Database table of spool data.

                              Data table of temse.

* TSP01 table --> spool request are available.

* TSP02 table --> output request entries are available.

* In file system storage, temse data will be send to file system /temp or /global.

*Make sure that 300 MB to 500 MB of space in disk space. As spool system will write files very quickly.

* pre- requsites for printer configuration:

     As to enable new functions in system, drivers are required.

      eg: Wifi - drivers, Audio drivers. similarly.

* drivers for the respective printer are need to make avail in SAP. to generate o/p request.

Steps for change temse location from DB to file system:

* SPAD --> output devices --> Display button --> select the printer, which need to change location --> choose edit option in the menu --> choose options accordingly to the need.

the above setting is  instance specific. this shows flexibility of SAP Application.

Types of printers:

1. local printer

2.remote printer

3. front end printer.

1.local printer: the spool wp and the operating system spool runs in same host

     if  server is unix s/m by using access method LP/LPR to get print out.

SPAD -- > output device --> Display--> double click on respective printer for UNIX.

eg: L : print  locally using LP/LPR.

      C : Direct operating system call.

Local printer is the most fast & reliable in sap.

2.remote printing: in the remote printer scenario. the SAP spool server and the OS spool runs in different hosts.

Advantages for remote printer:                                                                                                   

the workload of SAP system, will be reduces with only generating spool request and the output process will be done with another system.

Access method - ''U'' for remote printing.

In high end printer, printer it self is equipped with own network card & spool process. To process the printing with out any additional system(Host) for remote printer.

Access method:                                                                                                                         

S - SAP scripts                                                                                                             

U - remote printing.                                                                                                     

3. front end printer:     used to print, where GUI is installed (eg: end user) printer.

Access method: F

                                                                                                               

Default printer configuration in GUI installed s/m is taken in to consideration to printer using F access method.

the biggest advantages in Front end printer is NO need to think about the printer drivers.what ever the Printer configuration involved in GUI. can use the same.

• irrespective of Front end printer, the printing can be done in Front end printer configuration. 
• rdisp/wp_no_spo_Fro_max in RZ11 for dynamic changing of WP number if required. in Front end printing.

Summary notes:

front end printer: conversion of spool request to output will be taken care by local GUI system.

 Remote Printer: monitoring printer data of all the output request at single place.

T-codes in spool administration:

1. SPAD     - Spool administration.
2. SU3        - Default settings.
3. SP12       - temse inconsistency.
4. SP01       - spool req/output request.  ( To delete the old Spool request).
5. SP02       - own spool request.
6. 
   
7.                                                                                                                                

How to change file owners in LINUX and UNIX using PUTTY tool

chown SIDADM:sapsys <path of file>/filename

here 

SIDADM & sapsys  are users in the Linux machine, by running the above command file owner will change from sidadm to sapsys.

HOW to check where a system is ABAP stack or dual stack(ABAP + java).

method- 1

 sm51

  under message types, J2EE stands for dual stack

If not

ABAP stack.

Method-2
smicm-->menu bar-->GO TO --> services --> is J2EE server is there then, the system is dual stack
                     

                                                                      else

                                                                      ABAP stack
Method - 3

 if Operating system level access is there then, this method will be applicable, where as for the above 2 methods GUI access is enough.

access

usr/sap/sid/instance/J2EE


is J2EE file is present then, system is dual stack otherwise ABAP stack only.

System monitoring in solution manager 7.2

One of the best ways to think about SAP Solution Manager is as a tool to align business with IT. Most companies still treat ERP like a business facility. You design and layout your SAP landscape with enough space for your team, with offices, conference rooms, storage areas and other functional areas, and you run your business there. Renovations are rare and expensive — the goal is to build something where you won’t have to knock out walls or make new additions anytime soon.

SAP Solution Manager 7.2 has the tools to make your ERP work more like a business plan. You lay out your plan as a strategy based on the state of your company and your market, but you revisit it frequently. If you move into a new market or grow rapidly, you might have to make some major changes, but that’s okay — having that flexibility is what lets you stay so competitive.

Technical Monitoring Benefits of SAP solution manager 7.2 

• system monitoring of solution manager 7.2 makes it easier to keep sap servers healthy, allowing to improve performance, reduce downtime and reduce needless duplication through reusable templates.
• Technical monitoring has always been a focus of Solution Manager, but SolMan 7.2 is the first version designed with SAP HANA single-stack deployment in mind. That improvement has been a big help, allowing HANA customers to simplify their deployment and simplifying migration for SAP ECC users.
• The System Monitoring application provides an overview of the current status of technical systems, including their associated instances, databases, and hosts.

• Advantages of Technical Monitoring of solution manager 7.2.
1. SAP solution manager minimizes Downtime.
2. SAP SolMan 7.2 Provides Application-Specific Monitoring.
3. The Ability to Reuse Templates.

1. SAP solution manager minimizes Downtime: Barring a few scenarios like major natural disasters and attacks, unplanned downtime means someone has screwed up. More often than not, this is the result of insufficient Technical Monitoring, or a disconnect between the team who monitors your ERP, and the people who make decisions about upgrades. But even if you manage to avoid unplanned outages, you’re likely still paying for inadequate monitoring with long-planned downtime. When businesses prioritize the wrong things or put off needed changes, they can’t plan SAP implementations, upgrades and migrations Sooner or later, they have to play catch-up, which increases cost, complexity, and disruptive downtime.SAP Solution Manager 7.2 helps businesses develop a more strategic approach to SAP, with its powerful Technical Monitoring capabilities. Its ongoing monitoring and alerting functionality are complemented by deep reporting on system health and performance through SAP Earlywatch, allowing businesses to take a more strategic approach to SAP and reduce downtime.
2. SAP SolMan 7.2 Provides Application-Specific Monitoring:

                compare to solution manager 7.1 to 7.2. technical monitoring is one of the best advantages.

through Technical monitoring all the solution manager dashboards data can be monitoring.

which includes Application-specific Monitoring.

for any Additional specific Application specific and cross-application dashboards, create new dashboards option will be provided with solution manager 7.2.

by Fiori technology, the monitors will be the same from device to device, so it is easy for the sap end user to report the changes. to achieve this strong technical person required to monitor the system, so to avoid effects to other parts of solution manager.

Practically:System Monitoring is based on automated checks in regular time intervalls in the four categories Availability, Performance, Exceptions, and Configuration. In each of these categories, several metrics and corresponding thresholds can be defined per managed object

System Monitoring is based on automated checks in regular time intervalls in the four categories Availability, Performance, Exceptions, and Configuration. In each of these categories, several metrics and corresponding thresholds can be defined per managed object.

The System Monitoring application provides information about the current status according to the last measurement of each metric. In addition, alerts will be created and can be handled via the Alert Inbox in case thresholds are violated.


SETUP:

1. from the solution manager system, run the T-code: SOLMAN_SETUP.
2.navigate to SAP SOLUTION MANAGER -->CONFIGURATION(All Configurations).

3.navigate to Application operation -->system monitoring.

 4.

5.General Approach:

•     for the first time configuration and any changes to the previous configuration, need to proceed with step 2 and its subprocess.
• To add/remove/changes to monitors can directly proceed with step 4 followed by 5 and 6.
• To activate the monitor to the particular server or several services can proceed directly with step 5.

6.

7.

8.

9.

10.

MY references

https://wiki.scn.sap.com/wiki/display/TechOps/Solution+Manager+7.2+-+System+Monitoring
Extractor framework: https://wiki.scn.sap.com/wiki/display/TechOps/EFWK_Home

ANST - Automatic Note search Tool

HOW to update SPAM/SAINT version

WHY : 

• while updating Support packages to SAP erp system. some time system through the error as the Spam/saint version is too low.
• it is recommend to maintain spam/saint version to maximum version.

How: 

software required

• SAPCAR.
• spam/saint update file.

• check the SAP AP release and download based on RELEASE version.

• download path for Spam/saint file.         

 

                                                                                       

• current version of my system with T-code: spam.

• download the softwares and uncar the files.                                                                                     
• login with 000 client and access Spam T-code.                                                                             

• the initial screen of Spam is as below. which shows about maintenance certificate.      

• click on continue.                                                                                                                  

• load packages.                                                                                                                                  
• follow as shown below.