SAP Landscape Management 3.0, Enterprise Edition

Consistency

You choose a database consistency option and you can schedule the execution of the cloning volumes step.

Prerequisites

  • The database must not be in backup or suspend input/output mode when you start the process.

  • Log archiving must be enabled.

Context

SAP Landscape Management uses the following consistency methods for the database types:

Database Type Consistency Method
DB2 Consistency done by storage adapter
DB4 Not supported
DB6 Suspend input/output mode
Independent Not supported
INFORMIX Not supported
liveCache Suspend logwriter
MaxDB Database snapshot (online)
MSSQL Suspend input/output mode
Oracle Backup mode
SAP HANA Database snapshot (online)
Sybase Suspend input/output mode
Sybase IQ Not supported

Procedure

  • Choose one of the following options for the database consistency:
    Option Description

    Online: Clone Running DB

    To carry out the cloning process while the source database is running, select this radio button. An automatic crash recovery of the target database is triggered afterwards.

    Online: Backup/Suspend IO Mode

    To put the source database into backup mode during storage cloning, select this radio button and enter the timeout in seconds. An automatic recovery of the target database is triggered afterwards.

    Offline: Stop and Restart System

    To stop the source system before storage cloning and start the source system after storage cloning, select this radio button.

    Offline: Database already stopped

    Selected if the source database is already stopped. No changes are made to the source database.

    Database was stopped during system snapshot

    Selected if you clone from an existing system snapshot. No changes are made to the source database.

  • To schedule the execution of the cloning volumes step, select the Schedule execution of cloning step checkbox and enter an execution date and time.

    You schedule execution for synchronized cloning.

    The system provisioning activity will be executed immediately until it reaches the cloning volumes step. When the scheduled time is reached, the system provisioning activity continues and the cloning step is executed.