Performing Maintenance and Troubleshooting

1. Install your new SAP Landscape Management system.

2. Run the Configuration Wizard in SAP NetWeaver Administration.

1. Export your configuration data from SAP Landscape Management 3.0

2. Deploy the following SCA files using SUM:

   • VCMCR4E

   • VCM

   • VCMENT

3. Restart SAP NetWeaver AS Java.

4. In SAP Landscape Management, check which SAP Landscape Management edition you are currently using.

5. Import the configuration data into your SAP Landscape Management 3.0.

The figure, Backup and Restore, shows the backup and restore process:

• Export SAP Landscape Management configuration data regularly via Setup → Export, Import, Reset → Export.

• The system generates an XML backup data file containing all configuration details.

• A password is required to export logon credentials to satellite components.

• Exports without a password are still possible.

• You can import a configuration XML file to restore a previous configuration by choosing Setup → Export, Import, Reset → Import.

The figure, Backup and Restore: Export, shows the export configuration.

You export configuration information to provide a backup of the configuration settings in an XML file. This allows you to restore your configuration settings or move them from one SAP Landscape Management system to another.

1. Choose Setup → Export, Import, Reset → Export.

2. Select or deselect the configuration data as required.

3. On the Summary screen, provide a description for your export, as shown in the figure, Backup and Restore: Export (Continued).

4. Enter a password to encrypt user accounts.

5. The XML backup file generates.

6. Save the generated file to your preferred location.

The figure shows the required settings.

The figure shows the idea behind the high availability of SAP Landscape Management Itself.

Example: Make use of the automatic sync of two SAP Landscape Managements in case you have a HA setup, where your secondary SAP Landscape Management runs in a different data center.

• SAP Landscape Management automatically exports the configuration data of productive system.

• Imports configuration data into stand-by SAP Landscape Management.

• Options for export: daily, weekly, expert (specify the CRON Expression).

• Synchronization type: direct (define URL and credentials of source SAP Landscape Management), upload (path to XML file is defined).

Put your SAP Landscape Management in stand-by mode when, for example, you want to keep an SAP Landscape Management in sync with another. This is shown in the figure, High Availability of SAP Landscape Management Itself: Standby Mode.

The procedure is as follows:

1. If stand-by mode is enabled, the load on the managed landscape does not increase due to duplicated monitoring calls. In addition, you avoid executing operations on the stand-by by accident.

2. Choose Setup → Settings → Expert Mode.

3. Choose Synchronization/Standby → Edit.

4. Select Enable Standby Mode.

5. Specify the background jobs you want to stop.

6. The header shows (Standby Mode) and a standby message displays at the bottom of the screen.

Keep an SAP Landscape Management in sync with another, enable and schedule a periodic synchronization of the SAP Landscape Management configuration.

• Periodic synchronization is based on the export and import functionality.

• Automatically export the configuration data of your productive SAP Landscape Management and import it into your stand-by SAP Landscape Management.

• Choose Setup → Expert Mode, then choose Synchronization/Standby → Edit and specify the sync settings.

The figure, Synchronization of SAP Landscape Management, shows the Synchronization/Standby screen.

Components of SAP system landscapes will need patching and updating over time. This also includes Management System and managed entities in an SAP Landscape Management landscape.

Depends on Adaptive Design, for example, if DB executables are shared between multiple systems and a shared DB client

Host Agent Auto-upgrade can be used to distribute new versions

SAP Landscape Management itself logs to the Java EE engine. This is relevant in case of SAP Landscape Management application issues. It uses logging categories and tracing locations.

The logging categories are as follows: {ROOT CATEGORY}/Applications/LVM.

The tracing locations are as follows:

• {ROOT LOCATION}/com/sap/nw/lm/aci.

• {ROOT LOCATION}/com/sap/tc/lm/aci.

• {ROOT LOCATION}/com/sap/tc/vm.

SAP Landscape Management provides a support information ZIP file with technical information like the following:

• SAP Landscape Management version and edition.
• Configuration parameters.
• Logs with IP addresses.

It does not contain any password data or security-relevant information.

You can download the following support information:

• System support information.
• Error support information.
• Activities support information.
• Log support information.

The figure, Download Support Information, shows how to download system, error, and activities support information.

To download system support information, follow these steps:

1. Download a support information .zip file concerning a system, to attach it to a customer incident.

2. Choose <logged-on system> → Show Basic Support Information.

3. In the dialog box, download the .zip file.

To download error support information, follow these step: When an error message displays in a dialog box, choose Support Info, then download the .zip file.

To download activities support information, follow these steps:

1. Download a support information .zip file concerning a specific activity, to attach it to a customer incident.

2. Choose Monitoring → Activities → Support Info.

3. In the dialog box, download the .zip file.

The figure, Download Log Support Information, shows how to download log support information. This procedure is as follows:

1. Download a support information .zip file concerning a specific log, to attach it to a customer incident.

2. Choose Monitoring → Logs → Support Info.

3. In the dialog box, download the .zip file.

SAP Landscape Management shows log entries from external components. This is shown in the figure, Troubleshooting External Components.

Outputs are logged to the Operation Log. This also works for Custom Operations and so on.

For more detail, check the log files of the external component:

• Host Agent

• ABAP PCA

• LMauto (Java PCA)

• Storage Connector

SAP Host Agent runs a suite of programs:

• Connection to SAPSTARTSRV.
• ACOSPrep
• SAPOSCol
• Executes custom hooks and operations.

You can find the log files in the following location: /usr/sap/hostctrl/work/ (UNIX)

The most important log files are the following:

• dev_saphostexec (used by saphostexec executable)
• sapstartsrv.log (used by sapstartsrv executable)

The Software Provisioning Manager provides System Rename functionality. It writes multiple log files to a separate directory, as follows:

• Unix: /tmp/sapinst_instdir.
• Windows: C:\Program Files\sapinst_instdir.

The most important files are the following:

• sapinst.log
• sapinst_dev.log
• summary.html

SAP Landscape Management automatically packs the appropriate log files into a downloadable archive, which can be accessed directly through the SAP Landscape Management web interface. If an error occurs, all relevant log files are packed into the SUPPORT.SAR archive

For more information, see the SAP System Rename Guides section at http://help.sap.com/lvment20.

ABAP Post Copy Automation:

• Standard ABAP monitoring tools.

• Writes output of task list execution to the Task List Monitor (transaction code STC02).

• File system level logs:

  • R3trans

  • R3load

LM Automation Standalone Java PCA:

• Writes log files to its log/ directory.

• Execute PCA tasks manually through the web interface: http://<hostname>:50099/.

• Without a properly configured SAP Host Agent, almost any operation in SAP Landscape Management fails.
• In mass operations in particular, SAP Host Agent issues may not be visible directly.
• Check for Host Agent issues on all hosts included in the operation.
• Maintain consistent host agent patch levels across your landscape.

• Problems with prepare and unprepare operations usually come from processes that are still running within mounted directories.
• Check open files on the hosts, and end the related processes.

• Preparing an instance requires you to set the host on which the instance is supposed to run.
• Setting a Preferred Host in the instance configuration automates this process.

The figure, ABAP PCA: Troubleshooting (First Indication), illustrates how to troubleshoot an issue:

1. Review the log of your task list run in STC02.

2. To open the documentation, double-click the question mark.

Proceed as described in the following documentation sources:

• ABAP Post-Copy Automation Installation Guide.
• ABAP Post-Copy Automation Configuration Guide.
• SAP BW Post-Copy Automation Configuration Guide .
• Java Post-Copy Automation - Installation and Configuration Guide.

Review the following SAP Notes:

• 1614266 - System Copy: Post-Copy Automation (PCA) / LVM
• 1707321 - BW System Copy: Post Copy Automation (BW-PCA)
• 1709155 - System Provisioning with SAP Landscape Virtualization Management
• 1891353 - Central Note for Standalone Task Manager for LM Automation 1.0

The following are also useful sources of information:

• Check the ABAP PCA Troubleshooting Guide on the SAP Community Wiki under SAP Community Wiki → Development Topics → (JSTTSG) Main Page → ABAP Post-Copy Automation.
• Search for the following Frequently Asked Question pages on the SAP Community Wiki:
  • FAQ - ABAP Post-Copy Automation (SAP Community Wiki).
  • FAQ - Java Post-Copy Automation (SAP Community Wiki).
  • SAP Landscape Management FAQ (LVM,LaMa) (SAP Blog).
• Search for the Post-Copy Automation page on the SAP Community Wiki.
• Raise an incident for ABAP Post-Copy Automation with the SAP Incident Wizard, as described in How-to Raise an Incident for ABAP Post-Copy Automation (to find this guide, use the search function).