Google+ SAP CRM Backup and Restoring System - SAP ABAP

SAP CRM Backup and Restoring System

In an SAP CRM Panorama, information is exchanged using the Distant Function Call (RFC) technique.Mainly two varieties of RFCs are used for knowledge change: Synchronous RFC and transactional RFC.With synchronous RFC (sRFC), the caller of a distant perform at all times waits for the answer or consequence from the target system. Thus, knowledge consistency is at all times assured as a outcome of the remote operation is both executed utterly or the calling process receives an error code and should take applicable actions. This is true each for software errors within the target system or if the target system is not out there at all.

Transactional RFC (tRFC) and queued RFC (qRFC) are each executed asynchronously whereas the calling course of continues without waiting. qRFC is a variant of tRFC that maintains the order in which the functions are executed within the target system and thus, can be used for serialization of tRFCs of various SAP LUWs (Logical Unit of Work). The tRFC protocol ensures for each tRFC and qRFC that the perform is executed precisely as soon as in the goal system.Information exchange between the CRM Server and the Back-finish System is done using tRFC and qRFC communication.Manual deletion of queue entries causes inconsistencies between the sending and receiving systems.To ensure information consistency between sending and receiving system, by no means delete queue entries. As an alternative, attempt to clear up the problem that brought about the hanging queue and reprocess the queue request.

Application data

Normally, all techniques that maintain originals of software data should be backed up carefully to avoid the loss of essential enterprise information. Then again, techniques that maintain only replicated knowledge may be rebuilt from the original information sources so there could be no have to do a backup. Often it isn't clear at a first glance whether or not a component solely holds replicated information or if there are also unique items of data. So the variety of knowledge must be rigorously analyzed for each system component before the choice for this component’s backup technique could be made.The backup technique for use for the element then depends upon the sort of knowledge management: It could be a database and log backup in case of database-managed software data or a file system backup in case of file-primarily based knowledge managed by the application itself. In all cases, points of data consistency between the system elements should be regarded for system components that exchange data.The backup method then additionally is dependent upon the next factors:
  1. Does the element hold authentic data (which means the element is the leading system for some items of information) or replicated data? When speaking of replicated information, we imply both data that is merely replicated from another system and information that's derived from another system’s data.
  2. The time wanted to duplicate knowledge: Depending on the time it takes to restore duplicated information from the originals, it may not be necessary to back up the replicates.
  3. The sort of information and the sort of system managing the info

For replicated information, there could be three alternatives concerning the backup strategy:
  1. No Backup: Which means the info have to be utterly re-replicated in case of the elements failure. This different could possibly be used if the replication speed is adequate to satisfy the deadlines required of a restore procedure.
  2. Common Backup: Regular backup of the data utilizing an acceptable backup technique database or file system backup, full or delta backup). In case of a failure, this backup can be restored.
  3. Restore Using A quantity of Cases: Because of this in case of a number of installations of the identical part holding the same information, each might function a data backup of the other. This various in fact requires that the information format between the situations is compatible and that it is doable to copy the data onto one other instance and make it out there there.
Software and Data Configuration

Aside from business vital utility data, the system and software software program itself may be price being backed up. This can stop from a new set up in case all or components of the software have been destroyed. As a new set up will at all times be attainable, this backup just isn't mandatory. A basic advice is to back up the applying software no much less than once after it has been put in or after it has been upgraded. Be aware that restoring a backup of the system or utility software program is usually only doable whether it is restored to precisely the same hardware.Installing the software typically requires a large amount of configuring and customizing. Due to this fact, saving this kind of info may also be necessary to supply a fast restore and to keep away from effort and time after doable failures of a component. As the configuration might change more usually that the software program, the configuration files should generally be backed up on a regular basis or each time the configuration has been modified.

Consistent Landscape Back up

A consistent backup of two or extra techniques, which exchange information with one another, is a backup that ensures application knowledge consistency between the components. If such a Constant Landscape Backup is restored on all parts, the appliance knowledge is logically constant in the entire system landscape.A Consistent Landscape Backup can be used to create copies of the landscape, for example, for check environments. Additionally it is useful in making a Constant Landscape Backup as a fallback point earlier than doing massive system modifications such as upgrades or knowledge migrations. It's not usually essential to create a Consistent Panorama Backup during normal operation.A Consistent Panorama Backup cannot be achieved by performing a time limit restoration of all involved components. It is because there is more likely to be differences in the native machine time, which makes it unimaginable to get well the elements to the very same time limit with out having inconsistencies. This happens because some transactions have been committed on one system however not on the other.

Multiple Components in one data base

An alternative choice for making a Constant Landscape Backup is to put in all involved databases in a single database administration system. When utilizing this installation type, each backup of the database is a Consistent Landscape Backup.For productive techniques, this selection will in all probability mostly not be practical as a outcome of it imposes some restrictions on scalability, flexibility, and improve possibilities.The next things have to be taken into consideration when contemplating this feature:
  1. All elements are affected by a crash or a restore
  2. A part’s efficiency correlates to that of all different components
  3. Resource consumption may be fairly difficult
  4. On most database platforms, it isn't possible to do a point-in-time recovery for much less than one of the installed components
  5. Database administration can't be executed independently
  6. On most database platforms, upgrades cannot be finished with logging switched off

Multiple components in one database set up is not a solution that is usually relevant for all installations. Its use is probably restricted mostly to check, demo and development environments. A productive use could also be thought-about for methods with very sturdy consistency necessities in an setting that gives enough performance capacity (for example, together with parallel database techniques).

Related Posts

Mobile Scenarios in SAP CRM
CRM Middle ware Software Distribution
CRM Middle ware System Architecture
CRM Software Logistics and Support

SAP OOPS ABAP PART 6
SAP OOPS ABAP PART 7

No comments :

Post a Comment