Backup for SAP

This Blog talks about the ways and the significance of backup.

Storage is energetic to any computer system. It is doubly vital to an ERP system which serves as the memory for the business. Lose that memory and you’re out of business.

Backups are copies of all the important data on your system taken and preserved in such a way that you can recover your data no matter what happens. Making backups and being sure you have good ones is a best business practice. Typically an SAP system will have one or more storage administrators to take care of storage and backup systems. However as manager of the SAP system it’s important that you understand the basics of backup because it is so intimately connected with running a successful SAP system

Basically, ‘backup’ refers to three different things, only one of which is truly backup. There is short-term backup, which preserves a copy of the document for a short time, typically a week or two. There is true backup which saves a copy for a year or so. Then there is archival backup which saves important data permanently – or at least for five years.

FIX Protocol develops standards for European consolidated tape

In a move billed by the standards-setting body as a key milestone in the development of an EU-wide consolidated tape, Fix Protocol Limited has released a set of standards for the consolidation of trade reports and market data for European equity markets.

The recommendations from the group aim to identify where the trade was issued, in what currency, and where it was executed, down to the nearest microsecond.

Oracle R12 Applications Using LoadRunner

The Challenge

We recently load tested our first Oracle R12 release (All modules for nationwide and international wide of Oracle ERP R12). The company was upgrading to R12 from 11.5.8 largely for performance reasons.

We knew we’d be “cutting new ground” with LoadRunner on R12. This became evident with our first testrecord-and-playback, which failed even after finding and fixing all the missing correlations. We raised a ticket with HP (SR# #4622615067), and with their initial help, step by step we overcame all the nuances of coaxing vugen to record successfully, and then creatively working around its inability to recognize the full set of identifiers for a new java ITEMTREE object.

Configuring Oracle Unified Directory (OUD) 11g as a Directory Server

I used Oracle Unified Directory (OUD) Version 11.1.1.5.0 during my test deployment locally here. I tried to collect as much information possible in this post for configuration.

Ideally, there are three possible configuration options for OUD:

• as a Directory Server
• as a Replication Server
• as a Proxy Server

Directory Server provides the main LDAP functionality in OUD. Proxy server can be used for proxying LDAP requests. And Replication Server is used for replication from one OUD to another OUD or even to another ODSEE (earlier Sun Java Directory) server. You can my previous posts on OUD here and here.

In this post, we will talk about configuring OUD after installation as a Directory Server. You can read about OUD installation in my previous post here.

HP DIAGNOSTICS

Overview
Identifying and correcting availability and performance problems can be costly, time consuming and risky. IT organizations spend more time identifying an owner than resolving the problem.
HP Diagnostics helps to improve application availability and performance in pre-production and production environments. HP’s diagnostics software is used to drill down from the end user into application components and cross platform service calls to resolve the toughest problems. This includes slow services, methods, SQL, out of memory errors, threading problems and more.