The following objects will be provided by the Maintenance Planner:

 Stack-XML file
 SWPM and SUM
 Latest SAP Host Agent
 Latest Kernel
 SPAM/SAINT Update
 Database Backup files for products installed with SWPM 2.0
 RDBMS server software for products installed with SWPM 2.0
 RDBMS client software for products installed with SWPM 2.0
 Media for additional languages for products installed with SWPM 2.0
 Support Packages of Feature Package/Support Package Stack

The following objects need to be downloaded manually, most from

Software Download Center (SWDC):

 Latest SAPCAR
 RDBMS server software for products installed with SWPM 1.0
 RDBMS client software for products installed with SWPM 1.0
 Database Export Media for products installed with SWPM 1.0
 Media for additional languages for products installed with SWPM 1.0

Preparing the Installation Media

Installation media are available as follows:

 The software provisioning manager 1.0 archive containing the software provisioning
manager software

The media containing the software to be installed. These are the following:

 Kernel media

 RDBMS and export media.

Media Required for the Installation - Listed by SAP System Instance

This section provides a list of the media required for the installation, listed by SAP system
instance to be installed.

Media Required for the Installation - Listed by SAP System Instance

Identify the required media for your installation as listed below.

SAP Instance Required Software Packages from Installation Media
Installation

ABAP Central  Software Provisioning Manager 1.0 archive

services
 UC or NUC Kernel (folder K_<Version>_<N or U>_<OS>)
instance (ASCS
where U means Unicode and N means non-Unicode.
instance)
Note

Every new installation of an SAP system is Unicode. You can only use
the non-Unicode kernel if you perform the system copy for a non-
Unicode SAP system that has been upgraded to the current release.

Database  Software Provisioning Manager 1.0 archive

instance
 UC or NUC Kernel (folder K_<Version>_<N or U>_<OS>)
where U means Unicode and N means non-Unicode.

Note

Every new installation of an SAP system is Unicode. You can only use
the non-Unicode kernel if you perform the system copy for a non-
Unicode SAP system that has been upgraded to the current release.

 Database client software

For enabling SAP HANA SSL, at least SAP HANA Client 2.0 SPS04 is
required. For more information, see SAP Note 2784500 .

 Installation Export (folders EXP*)

Note

If you want to use SAP liveCache on SAP HANA, you must install
the LCAPPS package on the database server. For more information, see
the SAP MaxDB Administration Guide at [Link]
Application Help and SAP Note 2979266 .

Enqueue  Software Provisioning Manager 1.0 archive

Replication
 UC or NUC Kernel (folder K_<Version>_<N or U>_<OS>)
Server
where U means Unicode and N means non-Unicode.

Note
SAP Instance Required Software Packages from Installation Media
Installation

Every new installation of an SAP system is Unicode. You can only use
the non-Unicode kernel if you perform the system copy for a non-
Unicode SAP system that has been upgraded to the current release.

Primary  Software Provisioning Manager 1.0 archive

application
 UC or NUC Kernel (folder K_<Version>_<N or U>_<OS>)
server instance
where U means Unicode and N means non-Unicode.

Note

Every new installation of an SAP system is Unicode. You can only use
the non-Unicode kernel if you perform the system copy for a non-
Unicode SAP system that has been upgraded to the current release.

 Installation Export (folders EXP*)

 SAP SCM only: SAP MaxDB liveCache

Note

If you want to use SAP liveCache on SAP HANA, you must install
the LCAPPS package on the database server. For more information, see
the SAP MaxDB Administration Guide at [Link]
Application Help and SAP Note 2979266 .

 Database Client Software

Additional  Software Provisioning Manager 1.0 archive

application
 UC or NUC Kernel (folder K_<Version>_<N or U>_<OS>)
server instance
where U means Unicode and N means non-Unicode.

Note

If you install an additional application server instance in an existing

non-Unicode system, the additional application server instance is
created automatically as a non-Unicode instance. The software
provisioning manager checks whether a non-Unicode system exists and
chooses the right executables for the system type.

 SAP SCM only: SAP MaxDB liveCache

 SAP Instance Required Software Packages from Installation Media
Installation

Note

If you want to use SAP liveCache on SAP HANA, you must install
the LCAPPS package on the database server. For more information, see
the SAP MaxDB Administration Guide at [Link]
Application Help

 Database Client Software

SAP Host Agent (Separate Installation Only)

SAP Instance Installation Required Media

SAP Host Agent (separate  Software provisioning manager 1.0 archive

installation only)
 UC Kernel (folder K_<Version>_U_<OS>)
where U means Unicode.

Installation Checklist

This section includes the installation steps for the following:

 Standard system

 Distributed system

 High-availability system

 Additional application server instance

Detailed information about the steps are available in the linked sections.

Note
The SAP HANA database is normally pre-installed by SAP partners before you start the
installation. For more information about how to install the SAP HANA database, see the SAP
HANA Server Installation and Update
Guide at [Link] Implement Installation and Upgrade. The
contents of the database instance are remotely installed by the software provisioning
manager from the primary application server host.

On the Database for SAP System screen, enter the Database Host and the Instance
Number for your SAP HANA database host. If the instance does not exist, a new SAP
HANA database instance will be installed on the same host as the SAP system..

Standard System

1. You check the prerequisites and run the software provisioning manager to install the
SAP system.

Note

In a Standard System, all mandatory SAP system instances except the SAP HANA database
and database instance are installed on one host. This means, that the primary application
server (PAS) instance and any additional application server (AAS) instance are installed one
host, whereas the SAP HANA database and database instance need to be installed on a
dedicated SAP HANA host. Only if your operating system is Linux, you can alternatively install
the SAP HANA database and database instance on the same host as the primary application
server (PAS) instance and all additional application server (AAS) instances.

2. You continue with Post-Installation.

Distributed System

Note

In a Distributed System, all mandatory SAP system instances except the SAP HANA database
and database instance can be installed on several host. This means, that the primary
application server (PAS) instance and all additional application server (AAS) instances can be
installed on several hosts, whereas the SAP HANA database and database instance need to
be installed on a dedicated SAP HANA host.

1. On the ASCS instance host, you check the prerequisites and run the software
provisioning manager to install the ABAP central services instance.

Note

If you want to install an ASCS instance with embedded SAP Web Dispatcher or with
embedded SAP Gateway or both, you must choose the Custom parameter mode.
When processing the screens for the ASCS instance installation, you are prompted to mark
the corresponding checkbox on the screen Additional Components to be Included in
the ASCS Instance.

If you mark the checkbox for SAP Web Dispatcher, you are prompted for the additional
parameters required for the SAP Web Dispatcher installation on the subsequent screens.

2. On the primary application server instance host, you check the prerequisites and run
the software provisioning manager to install the contents of the database instance.

3. On the primary application server instance host, you check the prerequisites and run
the software provisioning manager to install the primary application server instance.

4. If required, you install 1 to <N> additional application server instances on the

respective hosts, as described later in this section.

5. You continue with Post-Installation.

High-Availability System

1. To install a high-availability system with Microsoft Failover Clustering, you perform

the HA-specific installation steps.

2. You continue with Post-Installation.

Additional Application Server Instance

You perform the following steps on each host where you install the additional application
server instances.

1. You check the prerequisites and run the software provisioning manager to install the
additional application server instances.

Caution

In a high-availability system, you must install at least one additional application server
instance.

2. You continue with Post-Installation

MS SQL specific backup restore SWPM

[Link]
[Link]?locale=en-
US&version=CURRENT_VERSION&q=Process+Flow+on+the+Taget+System+
[Link]
c22d9ecc82ca4ab591a91942fe5c0020/[Link]?
version=CURRENT_VERSION&locale=en-US

1. Take Backup of source

2. Restore backup to the target.

3. Run the software provisioning manager to install the target system as follows: by
choosing the following on the Welcome screen:

Prerequisites for Running Software Provisioning Manager

Running Software Provisioning Manager

On the Welcome screen, run the options under < Product> <Database> System
Copy Target System <System variant(Standard/Distribution Option/HA)> Based on AS
ABAP.

Choose the installation options exactly in the order they appear.

Note that after completing the <Product> <Database> System Copy Target
System <System_Variant> Based on AS ABAP Database Instance option, you must
subsequently run the <Product> <Database> System Copy Target
System <System_Variant> Based on AS ABAP Primary Application Server
Instance option as well. Otherwise you run the risk that the installed system is in an
inconsistent state, because if you do not run the <Product> <Database> System
Copy Target System <System_Variant> Based on AS ABAP Primary Application Server
Instance option, some mandatory ABAP reports that are integrated in this option have not
been executed in the primary application server instance.

For more information, see the MS SQL Server installation guide for your SAP system at:

[Link]
System Provisioning Installation Option of the software provisioning manager 1.0.
Standard System
Note
1. You install the MS SQL Server database software silently as part of the installation
of the respective SAP product. Do not install the database software separately
prior to the SAP [Link] a standard system, all mandatory instances are
installed on one host. Therefore, if you are installing a standard system, you can
ignore references to other hosts. on the host where you install the SAP system.
Note
If you want to use AlwaysOn where multiple SQL Servers host one database, see Database
High-Availability with SQL Server Always On.
2. You check the prerequisites and run the software provisioning manager to install
the SAP system.
Note
In a standard system, all mandatory instances are installed on one host in one installation
run.
3. You continue with Post-Installation.

Distributed System
1. On the database instance host, you install the MS SQL Server database software.
Note
If you want to use AlwaysOn where multiple SQL Servers host one database, see Database
High-Availability with SQL Server Always On.
You have to input Kernel & DB client software
2. On all hosts except the database instance:
 SQL Server 2012:
 install the MS SQL Server Native Access Client (SNAC) software.
 SQL Server 2014 and higher:
 install the ODBC Driver for SQL Server.
For more information, see 1902794 .
3. On the ASCS instance host, you check the prerequisites and run the software
provisioning manager to install the ABAP central services instance. You have to
input Kernel
Note
If you want to install an ASCS instance with embedded SAP Web Dispatcher or with
embedded SAP Gateway or both, you must choose the Custom parameter mode.
When processing the screens for the ASCS instance installation, you are prompted to mark
the corresponding checkbox on the screen Additional Components to be Included in
the ASCS Instance.
 If you mark the checkbox for SAP Web Dispatcher, you are prompted for the additional
parameters required for the SAP Web Dispatcher installation on the subsequent screens.
4. On the database instance host, you check the prerequisites and run the software
provisioning manager to install the database instance. You have to input Kernel
5. On the primary application server instance host, you check the
prerequisites and run the software provisioning manager to install the primary
application server instance.
Note
SQL Server 2012, make sure that you have installed the MS SQL Server Native Access
Client (SNAC) software on this host.
For SQL Server 2014 and higher, install the ODBC Driver for SQL Server. For more
information, see 1902794 . You have to input Kernel
6. If required, you install 1 to <N> additional application server instances on the
respective hosts, as described
Additional Application Server Instance
You perform the following steps on each host where you install the additional application
server instances.
1. SQL Server 2012:
 install the MS SQL Server Native Access Client (SNAC) software.
For SQL Server 2014 and higher:
 install the ODBC Driver for SQL Server.
For more information, see 1902794 .
Note
If you install the additional application server instance on the same host as the standard
system, this step is not required.
2. You check the prerequisites and run the software provisioning manager to install
the additional application server instances. You have to input Kernel
Caution
In a high-availability system, you must install at least one additional application server
instance.
3. You continue with Post-Installation.

4. When the software provisioning manager prompts for the database copy method,
choose Homogeneous System Copy & proceed further

Using Backup/Restore

Using Detach/Attach

Oracle-Specific Procedure
Purpose
In an SAP system environment, you can create a homogeneous copy of an Oracle database
by copying database files. This method is suitable for creating an exact copy of an existing
database. The source of the copy can be an online or offline backup, or the file system of
your source host.

You use the software provisioning manager for the installation on the target system host
as described in the installation documentation for your SAP component. Only the software
provisioning manager steps for setting up and loading the database steps are different.

Oracle Storage-Based System Copy Methods Available in the software provisioning

manager

You can choose between the following methods:

 Database already recovered, continue with database-specific post activities

You have already performed backup/restore with Oracle-specific methods. In this

case, the software provisioning manager does not need to perform the backup/restore.
You just have to ensure that the restored Oracledatabase on your target system is up and
running.

 Performing Online or Offline Recovery with saphostctrl

 Using a [Link] File Created by the ORABRCOPY Tool

Performing Online or Offline Recovery with “saphostctrl”

This section describes how to perform a recovery using saphostctrl.

For the offline recovery method, we recommend that you shut down the database.
Alternatively, the software provisioning manager can also make an instance recovery
of the database if it has not been shut down before the copy process.

For the online recovery method, you have to set the database to a backup mode
and the backup control files and the Oracle archives will be copied to an existing shared
directory.

A “shared directory” can be any directory path

which the source system and the target system can access. The archives and
also the init<SID>.ora files from the source system will be saved in this directory

Restrictions

You cannot change the database schemas SAP<SchemaId> and SAP<SchemaId>DB. There is
no “move” schema.

The <DBSID> can be changed because the rename process is able to create new control
files with a new <DBSID>.
The <SAPSID> can be also changed.

Performing Offline Recovery

For the offline recovery method, you have to proceed as follows.

Procedure

1. Shut down the source database.

2. Back up the data files, for example using image copy or snapshot technology.

3. Start the target system installation and follow the instructions on the software
provisioning manager screens.

Start the target system installation as described in the Installation Guide - Installation of
SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to
7.52 on Windows : Oracle (see Accessing the Installation Guides).

4. On the Performing Oracle Storage Based System Copy screen, select option Online
or Offline Recovery Method with saphostctrl.

5.

6. Leave the dialog field of the <shared_directory> empty while performing an offline
recovery while no additonal files from the source system are needed.

7. When the software provisioning manager stops for database restore, copy all saved
files to the target System.

Make sure that you also copy either the source spfile<DBSID>.ora file - which must contain
parameters and not only the entry spfile=… - or the source spfile<DBSID>.ora file.

Creating a Backup

Create a backup if required. Choose between the following possibilities: Performing an

offline backup manually or an offline or online backup with BR*Tools.

Creating an Offline Backup

Create an offline backup, if required. There are different possibilities for

preparing the actual transfer of the database files:

 If you have an up-to-date offline backup, you can use it (provided that redo
logs were cleaned up with forced log switches).

 If you want to transport the database file (for example, on tape) or if you have to
perform the database shutdown at a certain time, stop the database (normal
 shutdown) and perform a complete offline backup. You can use the trace
file [Link] created by OraBrCOPY to determine the file system trees that
have to be saved.

 Stop the database (normal shutdown) and copy the database files when the actual
transfer to the target system takes place. You do not have to perform any
preparations for the actual transfer now. Proceed with the next steps.

Creating an Offline or Online Backup with BR*Tools

You can use any backup strategy supported by BR*Tools as the basis for
a system copy: offline or online, with or without BACKINT, with or
without RMAN, complete or incremental, and so on. The backup strategy
must simply be valid for restore and recovery. This means that a complete
restore and recovery of the source database must be possible. In
addition for BACKINT and RMAN, the external backup tools must be
configured so that a restore is possible on the target host.

Procedure
Proceed as described in the SAP Library for your release at:

Note

Navigate to the SAP Help Portal page for the SAP NetWeaver release your
SAP product is based on as described in section Accessing the SAP Library,
and then continue the navigation as described below.

SAP NetWeaver Library: Function-Oriented

View Administration of Databases Database Administration for
Oracle SAP Database Guide: Oracle BR*Tools for Oracle
DBA BR*Tools in Action Backup and Database Copy with
BR*Tools