SAP Minimized Downtime

Minimizing Downtime in SAP Environments

You depend on SAP solutions to run your business and global operations mean SAP applications must be running round-the-clock. But every day the window for any downtime gets smaller and smaller. How do you schedule planned downtime for upgrades and maintenance without affecting the business. Sun developed the minimized downtime procedure, using Solaris Containers and Solaris ZFS, so you can perform upgrades, maintenance, and even provisions non-production systems — without worrying about downtime.

With the minimized downtime procedure, you can downsize your downtime. It's as easy as one, two, three.

• One - Create a clone of the portal environment using Solaris Containers with Solaris ZFS
• Two - Upgrade the software on the clone environment
• Three - Switch all of the users to the cloned, upgraded system

The procedure also works with Sun N1 Advanced Architecture for SAP Solutions to help automate the switch from production to newly upgraded environments.

You can use the same cloning procedure to move a container to another system so you can perform maintenance on the original system. And you can clone whole SAP environments for development, test, and QA purposes — on the fly.

With the minimized downtime procedure you can:

• Upgrade software with minimal impact to users and the production systems
• Perform maintenance on hardware, without scheduling downtime
• Provision non-production environments on the fly to help quickly take advantage of new SAP capabilities

For more information see:

• Feature Story — Minimize planned downtime in your SAP environment with the minimized downtime procedure
• SAP NetWeaver Magazine Article — Downsize Your System Downtime
• Solution Sheet — Minimized Planned Downtime on SAP Systems
• White Paper — Minimizing Downtime in SAP Environments