SAP Netweaver Landscape Virtualization Management Backup

Recently asked about the backup and restore procedures for LVM, I’ve done some reading and also asked the SAP Product Management team, and here are my findings.

LVM has a functionality that enables to export its full configuration to an XML file. It is described here: http://help.sap.com/saphelp_lvment20/helpdata/en/d4/132955ba874eb9a43778b69a3ca1e7/frameset.htm > Section “Backup and Restore”

Is this needed in all backups? No. This is an “additional” functionality. Standard SAP Netweaver AS JAVA backup best practices are enough to ensure the safe guard of LVM. Nevertheless, in specific situations it may be necessary to keep just the configuration data. One of those cases is when upgrading from LVM 1.0 to 2.0, where SAP explicitly recommends to export the configuration before the upgrade and import it back afterwards.

As for SAP Netweaver AS JAVA backup practices, standard best practices apply:

• Build a standard “28 days cycle” backup strategy;
• Include on your backup both the database and the filesystem;
• Take into consideration the special needs of the AS JAVA, in particular the recommendation to freeze deployments before starting a backup. 

Check out more info on this here: http://help.sap.com/saphelp_nw73ehp1/helpdata/en/AB/A24C409CEF4F4FA21F9777CE360B06/content.htm

Summary: SAP NW LVM is an add-on installed on top of a standard Netweaver AS JAVA, and all the backup&restore principles of AS JAVA apply also to LVM.

All details on EMC integration with LVM at our page in the SAP Community Network: http://scn.sap.com/docs/DOC-43343