sun storage 7000 unified storage systems and xml-based archiving for sap systems

Sun Storage 7000 Unified Storage Systems and XML-Based Archiving for SAP SystemsApril 2010
Sun Storage 7000 Unified Storage Systems and XML-Based Archiving for SAP Systems
Oracle White Paper—Sun Storage 7000 Unified Storage Systems and XML-Based Archiving for SAP Systems
Introduction........................................................................................ 1
Changing Storage Economics ....................................................... 2
Infrastructure ................................................................................. 9
Customize XML Archiving.............................................................11
Glossary ...........................................................................................30
Introduction
This guide provides information on how to quickly setup the Sun™ Storage 7000 Unified
Storage System for use as a target for SAP´s WebDAV-based XML archiving. This document
assumes that users are familiar with the Sun Storage 7000 Unified Storage System and
general SAP archiving concepts and functions, including the appropriate transactions. Figure 1
shows a typical system configuration with an application server, central instance, and
database.
1
Sun Storage 7000 Unified Storage Systems
Sun created the Sun Storage 7000 Unified Storage Systems to respond to requirements for effective,
manageable, and scalable data storage. Sun's open-systems approach carefully selects the best general-
purpose servers and storage components, combines them with innovative technologies, and unifies
them with storage software. Sun Storage 7000 Unified Storage Systems offer performance and
scalability while providing a powerful and intuitive interface.
Changing Storage Economics
reducing the time required to troubleshoot storage issues. Resulting systems deliver high performance
at lower cost, in less space than competitors, and with simplified management of complex storage
architecture. Sun Unified Storage Systems with integrated enterprise flash technology combine open-
source software with the OpenSolaris Operating System and the ZFS file system. The results are a
scalable infrastructure with intuitive monitoring and management, predictable performance, and
flexible services designed to meet the needs of modern organizations.
Sun Storage 7000 Unified Storage Systems promise to do for storage what open systems did for
servers. Ideal for new and fast-growing storage build-outs where organizations need to simplify and
speed storage administration, these storage appliances exploit the power of today’s multicore,
multithreaded processors to increase application performance. Together with advanced features such
as Solaris Dynamic Tracing (DTrace) and the ZFS file system, these appliances provide unprecedented
real-time performance and debugging analysis, high computational scalability, strong security, and end-
to-end data integrity.
• Quick installation and configuration — Sun Storage 7000 Unified Storage Systems provide up to 10-
times faster installation, requiring as little as four minutes for a full install. Click-and-drag
administration is provided with no training required and an installation wizard makes configuring
and deploying clustered scenarios quick and easy.
• Intelligent analysis and optimization — Sun Storage 7000 Unified Storage Systems offer simple-to-
use graphical tools and detailed analytics software that provide real-time visibility of CPU, memory,
data, data protocol, disk, and network performance. An instant RAID rebuilder provides
comprehensive self-healing capabilities, meaning that the system can be rebuilt in minutes, not days.
• Easily scalable storage infrastructure — Hybrid storage pools optimize the way in which storage is
spread across memory, solid state devices, and disks, enabling you to easily perform non-disruptive
adds, moves, or changes to the storage infrastructure. Automated data placement and migration is
provided and a single software stack across the entire product family eliminates the need for script
re-writes when moving from one platform to another. In addition, data services can be added easily
with no additional software license to manage or buy.
2
• Rapid diagnosis and troubleshooting — Real-time analytics let you visualize system health and
manage read and write I/O performance. Real-time visibility is provided throughout the system.
• Comprehensive service portfolio — Sun's comprehensive service portfolio provides organizations
with the help they need to seamlessly integrate their next-generation unified storage solution into
their business environment. Sun believes that open source is the ideal development and business
model for modern organizations and offers a full spectrum of services for businesses that seek
performance without incurring burdensome hardware and licensing costs.
Configuration
The configuration examples in this document feature a Sun Storage 7210 Unified Storage System. All
configuration steps are performed using the Bus Unit Interface (BUI) but can also be executed on the
command line using ssh. Note: It is not necessary to have the Sun Storage 7210 Unified Storage
System and all involved servers in the same domain or subnet to successfully complete the
configuration steps in this guide. However, all units must be able to communicate over the network.
Supporting text should contain benefit/solution information such as which business problems exist
and how they are solved, the ROI/value produced by addressing the problem, and which solution(s) or
pieces of the solution Oracle provides.
Services
To configure the services:
1. Log into the appliance using the URL (https://<appliance-ip>:215), the screen, or the area to
configure the services (for example, access protocols.)
The services window is displayed, as shown in Figure 2.
Figure 2. Services window
2. In the Services window, select HTTP to see a list of the properties that can be set. The
Services/HTTP window is displayed, as shown in Figure 3.
Figure 3. Services/HTTP window
Note the following:
• If the Require client login option is enabled, clients that do not supply valid authentication credentials
for a local, NIS, or LDAP user are denied access. Active Directory authentication is not supported.
• Only basic HTTP authentication is supported. As a result, user names and passwords are transmitted
unencrypted unless HTTPS is used, which might not be appropriate for all environments.
• Authenticated users have the same permissions with HTTP as with NFS or FTP. Files and
directories created by an authenticated user are owned by that user, as viewed by other protocols.
• For access control, privileged users (those having a uid less than 100) are treated as nobody. Files
created by privileged users are owned by nobody.
• If the Require client login option is disabled, the appliance does not attempt to authenticate clients even
if they supply credentials.
• Newly created files are owned by nobody. and all users are treated as nobody for the purposes of access
control.
• No permissions are masked from created files and directories, regardless of authentication.
• Created files have UNIX permissions 666 (readable and writable by everyone), and created
directories have UNIX permissions 777 (readable, writable, and executable by everyone).
• HTTP service is disabled per default after installation or a factory reset and must be enabled
explicitly.
4
Network
No special network requirements are mandated for WebDAV based-XML archiving. However, for
best results, it is recommended that you configure a private network to handle storage traffic between
SAP systems archiving their data and the Sun Storage 7000 Unified Storage System.
To display the Network Interface window and edit the network interface properties:
1. From the Configuration menu, select Network.
The Network Interface window is displayed, as shown in Figure 4.
2. Click the pencil icon to edit the interface properties.
Figure 4. Network Interface window
Storage Pool
Successful configuration of the storage pool RAID layout requires a balance between availability,
capacity, and performance and the advantages of each should be weighed carefully before selecting a
data profile. For example, the Mirror profile provides distinct performance benefits, but can
significantly impact capacity. Additionally, depending on the Sun Storage 7000 Unified Storage System
model being used, it might be necessary to select a data profile for log SSDs present in the
configuration. Removing the log devices can supply the best performance, while mirroring the log
devices can provide improved availability. For a description of the relative tradeoffs related to
availability, capacity, and performance, refer to the Sun Storage 7000 Unified Storage System BUI. The
Configure Storage window is shown in Figure 5.
5
Figure 5. Configure Storage window
Projects and Shares
For best results, configure the project and shares to be accessible by the HTTP protocol. The number
of projects and shares is dependent on such business factors as snapshot and cloning granularity. If
replication is implemented, utilize project layouts. Note that the Sun Storage 7000 Unified Storage
System replicates at the project level.
For differing replication schedules for archived data, configure multiple projects, thereby enabling each
to replicate on its own schedule. To create multiple shares under the same project, change the
properties at the project level to enable them to be inherited by all shares. Note that individual
properties can be overridden at the share level as needed.
To display the All Projects window, select All Projects from the Share menu. The All Projects window
is displayed as shown in Figure 6.
Figure 6. All Projects window
6
Shares
1. Go to the Shares section.
2. Select Archive_SAP from the project menu. The Archive_SAP window is displayed.
3. Click on the plus (+) sign to create a new file system. The Archive_SAP Create Filesystem window
is displayed, as shown in Figure 7.
4. Define the share by entering the names and permissions.
Figure 7. Archive_SAP Create Filesystems window
After defining the share, set the additional properties by clicking the pencil icon, which is displayed
when the mouse pointer is moved to the Share menu option. To apply a different name to a share, de-
select Inherit from project, then modify the other properties or set them on a share level as shown in
Figure 8.
7
Figure 8. Projects/Archive SAP window
Analytics
To observe the workload on the Sun Storage 7210 Unified Storage System, refer to the following
analytics:
• Protocol: HTTP/WebDAV requests broken down by:
• Type of operations
• Raw statistic
To view the analytics, use the Add statistic window, shown in Figure 9.
8
Figure 9. Add statistic window
Configuring SAP — The XML Direct Archiving Service
XML-based data archiving is used to move business data that is no longer current from the database
into an offline archive for potential future access. XML archiving utilizes XML standards, an XML
schema, the platform-independent Java™ language, and WebDAV to validate and describe the
structure of archived objects. HTTP(s) provides secure communication between the application
system(s) and the data archiving service.
Infrastructure
XML-based archiving commonly involves two logically and physically separate systems. The first is the
application system that includes a database containing the objects (or records) to be archived, and the
XML DAS Connector, which communicates with the data archiving service using HTTP or HTTPS.
The second is the archiving system on which XML DAS runs.
The configuration steps presented in this section differ from a typical SAP configuration in that a
ABAP and a Java instance are installed together on one common central system (or double stack), while
the XML Data Archiving Service and XML DAS Connector are configured on the same server. A
typical default archiving landscape is shown in Figure 10, while the single server configuration used in
this document is shown in Figure 11.
9
Figure 10. Default archiving landscape
Figure 11. All-in-one configuration landscape
10
Customize XML Archiving
• XML DAS administration
• Configure the logical home path (Where logical home path reflects
the physical home path to be used.)
• Configure XML DAS (connector)
• Synchronize the home path
• To perform this step, use a web browser. To reach the appropriate service, use the following URL
structure:
http://<Host of SAP J2EE Engine>:<HTTP port>/DataArchivingService/DAS
The following example displays an authenticating window where a user with the assigned role
XMLDAS will be authenticated.
To access the data archiving service:
• Go to http://<Host of SAP J2EE Engine>:<HTTP port>/DataArchivingService/DAS. The
Authentication Required window is displayed, as shown in Figure 12.
• In the Authentication Required window, enter the username and password for user XMLDAS and
click OK.
• In the window, authenticate user XMLDAS by assigning an existing or a new user role. (Although
creating a user, role, or assigning roles to users is not part of the XML DAS configuration, it is
described here to illustrate the steps needed to complete XML DAS administration using a browser.)
Figure 12. Authentication Required login prompt
11
Create Users
The steps used to create new users depends on the system stack being used. If the system stack is a
pure Java system, use the Netweaver user management window shown in Figure 13. If the system is a
double stack utilizing both Java and ABAP, use transaction SU01 and the User management ABAP
window, shown in Figure 14.
Figure 13. NetWeaver user management window
Figure 14. User management ABAP
12
Create Role(s)
After creating the XMLDAS user, create a role for Z_XMLDAS_ADMIN using the transaction
PFCG, then assign the role to the new user XMLDAS using the Display Roles window, as shown in
Figure 15.
Security Roles
In this step, assign a security role for user XMLDAS using the Visual Administrator. To assign a
security role for user XMLDAS:
1. From the operating system level, logon as user <SID>adm, then start the Visual Administrator.
The Visual Administrator window is displayed, as shown in Figure 16.
2. In the System Security Provider section of the Visual Administrator window, select a security role
for user XMLDAS.
13
Figure 16. Visual Administrator
After assigning a security role to XMLDAS, create a technical communication user for the actual
archiving process, by repeating the steps above for user XMLCLIENT with the assigned role of
Z_XMLDAS_CLIENT and a security role of XMLDASSecurity. When the above steps are completed,
login to the XML DAS administration service and start customizing.
XML Data Archiving Service
During this phase, the archive stores are defined and tested. To define and test the archive stores, login
to the XML DAS. The XML Data Archiving Service window is displayed, with possible tasks listed on
the lower left side, as shown in Figure 17.
14
Figure 17. XML Data Archiving Service window
Define Archive Stores
To define the archive stores:
1. Click on Define Archive Stores in the XML Archiving Service window. The Define Archive Stores
window is displayed, as shown in Figure 18.
Figure 18. Define Archive Stores
15
2. In the Define Archive Stores window, scroll down in the list of available stores and click New.
Figure 19. Define Archive Stores window
3. Edit the credentials to define the archive stores, as shown in Figure 19, then click Insert Archive
Store to check that the archive store is available and is registered in the system, as shown in
Figure 20.
Figure 20. Overview of checked and registered archive stores
To test the inserted archive, click on Test on the left side of the XML Data Archiving Service
window. The Test Archive Stores window is displayed, as shown in Figure 21. A check symbol
indicates that the archive store is accessible and is available for XML archiving.
Figure 21. Test Archive Stores window
16
XML Archiving ABAP Stack — RFC Definitions
SAP uses internal RFC connections to communicate with other systems and objects. To establish
communication, define the RFC communication between the XML DAS connector and the XML
DAS. In the next example, transaction SM59 is used to define the RFC definitions.
To create a new RFC connection:
1. Open the RFC Destination window.
2. In the Connection Type field, select HTTP Connections, as shown in Figure 22.
Figure 22. RFC Connection window
Next, provide credentials for the technical communication and administrative user. To provide the
credentials for the technical communication user, enter the user credentials in the user field of the RFC
Destination window, as shown in Figure 23.
17
Figure 23. RFC Destination window
During the initial test of the connection, you are asked if you wish to accept cookies now and in the
future from the server running the XML Data Archiving Services. It's recommended that you click
Yes, as shown in Figure 24.
Figure 24. Accept Cookies
18
If the communication test is successful, OK is displayed in the Status Test field, as shown in Figure 25.
For a detailed view of the test results, click the Response Header Fields tabs, as shown in Figure 26.
Figure 25. RFC Connection test result
Figure 26. RFC Connection detailed test results
19
Transaction SARA
In this section, transaction SARA is used to customize the XML Data Archiving Service connector of
the ABAP stack and to define rules for setting the home path. To customize the XML Data Archiving
Service:
2. In the Archive Administration: Initial Screen window, select BC_SBOOK_X (provided by SAP
for training purposes), as shown in Figure 27.
Figure 27. Archive Administration: Initial Screen window
Basis Customization
After selecting the object to be archived, customize the basis. In the Archive Administration: Initial
Screen window, click on Customizing, as shown in Figure 28.
20
Figure 28. Archive Administration: Initial Screen — Basis customizing within SARA transaction
Configure Home Path
In this step, you specify a path to represent the logical home path. SAP recommends that you use the
following naming conventions in this window:
• To avoid potential conflicts with other archiving objects, all objects should start with the same
notation, for example:/<SYSID>/<CLIENT>/<OBJECT>/, where OBJECT is substituted by an XML
archiving object.
• Only keywords are identified by <> are recognized.
• Default for the logical home path is DEFAULT_WITH_CLIENT and should not be changed. For
example, the home path /<SYSID>/<CLIENT>/<OBJECT>/7210_Walldorf/ becomes
/ARC/444/BC_SBOOK_X/7210_Walldorf/ after synchronization with XML DAS from system
ARC, client 444, working with the archiving object BC_SBOOK_X. The Change View Customizing
Home Paths window is shown in Figure 29.
21
Figure 29. Change View Customize Home Path window
Configure XML DAS
During this phase, define the XML DAS by providing the following information:
• RFC Destination — HTTP connection that was created using transaction SM59.
• Active — XML Data Archiving Service that XML DAS Connector utilizes to archive objects. It's
possible to make multiple entries, but only one is active at a time.
• Check Sum — Indicates if a check sum is to be verified when resources are read. If this indicator is
activated, a check is run during the reading of a resource to ensure that it has not been changed or
modified since it was archived and that the resource is the same one that was originally archived.
Because it ensures that the archived object was not modified and because it does not impact access
performance, SAP recommends that this indicator should always be activated.
Figure 30 shows the New Entries: Overview of Added Entries window.
22
Figure 30. N ew Entries: Overview of Added Entries window
Synchronize Home Paths
During this phase, the home paths that are used by the XML archiving objects are created, thereby
enabling data to be archived. Figure 31 shows the Synchronization of Home Paths for XML-Based
Archiving window.
23
Figure 31. Synchronization of Home Paths for XML-Based Archiving window
If the home path creation is successful, the run is repeated in productive mode, as shown in Figure 32.
24
Figure 32. Synchronization of Home Paths for XML-Based Archiving (productive mode)
Next, assign an Archive Store to the newly created home paths. Click to the XML Data Archiving
Service window at http://<DAS server>:50000/DataArchivingService/DAS. A list of archive stores
and home paths are displayed, as shown in Figure 33.
Figure 33. Assign Archive Stores window
25
To see a listing of all available archive paths, click List Archive Paths in the lower left side. A listing of
available paths is displayed, as shown in Figure 34.
Figure 34. List Archive Paths window
To verify the home paths using the BUI:
1. Click on the Write button within the SARA transaction to archive the SAP provided sample
BC_SBOOK_X. The BUI verifies the creation of the home paths, as shown in Figure 35.
Figure 35. Home paths seen with the BUI
Data can now be archived. The Archive Administration window is shown in Figure 36.
26
Figure 36. Archive Administration:Create Archive Files window
Sun Storage 7000 Unified Storage Systems
The Sun Storage 7000 Unified Storage Systems provide a number of services to protect archived data,
including NDMP support and clustering. Snapshot and replication services are also supported and are
discussed below.
Snapshot
Snapshots can be taken at the project or share level. When using the BUI, perform the following steps
to take a snapshot:
1. Select Shares.
2. Select the share or project to be created for a snapshot.
3. Select the Snapshots tab.
27
4. Click the plus sign (+) to add a new manual snapshot or select the Schedule tab and Click (+) to
add a new scheduled snapshot, as shown in Figure 37.
5. Click Apply.
The snapshot is created and can be used as input for other activities, such as creating a re-writable
clone.
Cloning a Snapshot
Before the snapshot can be accessed as a readable/writable file system, it must cloned and mounted on
the origin server or on the server assigned to work with the clone. To clone a snapshot:
1. Select Shares.
2. Select the share or project that contains the snapshot to be cloned.
3. Select the Snapshots tab.
4. Select the snapshot to be cloned.
5. Click (+) to Clone snapshot as a new share.
6. Give the clone a unique name to identify it as separate from the snapshot (example: fs1- clone.)
7. Click Apply.
Replication
Replication is configured at the project level only. All file systems or SCSI luns contained within a
project are asynchronously replicated on the same schedule to the target system. To enable replication
to another Sun Storage 7000 Unified Storage System:
1. Select Shares -> Projects.
2. Select the project to be replicated and click the Edit Entry icon.
3. Select the Replication tab.
28
4. Click (+) to add a new replication target.
5. Fill in the target address and root user password. Select Continuous Scheduled mode.
6. Click Add.
Accessing Replicated Data
Before the replicated data on the target system can be accessed, the system must complete at least one
successful replication. To access the replicated project:
1. Login to the target system.
2. Select Shares > Replication.
4. Click (+) to clone this replica.
5. Assign a clone project name to the replicated project.
6. Optionally change the mount points of any file systems in the project by using Override
Mountpoint.
7. Click Continue.
The project, including all file systems, is now available to be accessed on the server where replicated
data is attached.
Reference
For detailed information on SAP archiving, see the embedded wiki that can be called from each screen
using the Help button or directly using https://<appliance-IP>:215/wiki/index.php/Main_Page, as shown
in Figure 38.
Additional information is available from the following resources:
• http://www.sun.com/storagetek/open.jsp
• http://docs.sun.com/hardware/diskstorage
• http://docs.sun.com/app/docs/prod/uni_storage
• http://www.sun.com/storageteck/solutions.jsp
http://help.sap.com/saphelp_nw04/helpdata/en/23/e58b7cac80e44c869f2e8805a65de4/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/fa/2250e2bc4b1442a39265abba676cd9/frameset.htm
Glossary
Resource
Archive Path
Archive Store
A location or area within a WebDAV or file system used in XML data archiving. Before archiving can
begin, an archive store must be assigned to either a home collection or application collection.
Collection
Repository where resource resides. A collection can contain other collections or sub-collections.
Home Collection
Data objects from a specific application are archived only in or under the home collection of the
archiving object to which they belong.
Home Path
The archive path of a resource must begin with the home path. Access rights are checked by the XML
DAS Connector.
Logical Home Path
The home path represented by a logical home path is defined separately by customizing of the home
paths. A logical home path is similar to the usage of an alias.
SAP J2EE
URI
Format used in XML Data Archiving to address resources or collections. Not an URL although it
looks similar. A collection can be addressed using an URL.
XML DAS
31
XML-Based Archiving for SAP Systems
April 2010
Oracle Corporation
World Headquarters
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.
This document is provided for information purposes only and the contents hereof are subject to change without notice.
This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed
orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose.
We specifically disclaim any liability with respect to this document and no contractual obligations are formed either
directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their
respective owners.
AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered
trademark licensed through X/Open Company, Ltd. 0310
Services
Network
Transaction SARA
Basis Customization

sun storage 7000 unified storage systems and xml-based archiving for sap systems

Documents