Академический Документы
Профессиональный Документы
Культура Документы
TABLE OF CONTENTS
How to Handle Alert Storage snapshot is prepared .........................................................................................1
Symptom: ................................................................................................................................................................3
Environment: ...........................................................................................................................................................4
Cause: ......................................................................................................................................................................5
Resolution: ..............................................................................................................................................................6
See also: ................................................................................................................................................................10
Keywords: .............................................................................................................................................................11
2
HOW TO HANDLE ALERT STORAGE SNAPSHOT IS PREPARED
Symptom:
This Knowledge Base Article (KBA) is part of a series of HANA Operation Recommendations.
Its focus is on providing best practice instruction on handling HANA Alerts related to How to Handle Alert
Storage snapshot is prepared (Alert ID 66 - Storage snapshot is prepared).
A storage snapshot captures the content of the SAP HANA data area at a particular point in time. In this way,
storage snapshots offer an additional option to safeguard the SAP HANA data area and to recover a SAP HANA
database. A SAP HANA database can be recovered in a single procedure, either using a storage snapshot only,
or using a storage snapshot in combination with log backups.
When checking the Alert tab in HANA studio, there is an alert called The database was prepared for a storage
snapshot for longer than 392 seconds.
For HANA studio, you would find the alert by going to Administration Console Alert Show: all alert.
3
HOW TO HANDLE ALERT STORAGE SNAPSHOT IS PREPARED
Environment:
4
HOW TO HANDLE ALERT STORAGE SNAPSHOT IS PREPARED
Cause:
The user plans to create a storage snapshot, however he does not finish to confirm it or abandon it in time.
5
HOW TO HANDLE ALERT STORAGE SNAPSHOT IS PREPARED
Resolution:
PROCEDURE
1. Check Alerts
2. Monitor storage snapshot
3. Confirm or abandon the storage snapshot
PATH
HOW TO
1. Check Alerts
For HANA studio, you would find the alert by going to Administration Console Alert Show: all alert.
6
HOW TO HANDLE ALERT STORAGE SNAPSHOT IS PREPARED
To monitor storage snapshot, you could choose to Backup and recovery Open Backup Console Overview.
You can confirm that the database is now prepared for a storage snapshot and know the started time, size of the
storage snapshot.
Choose to Backup and recovery Open Backup Console Backup catalog, to look up more detailed
information.
Also, you could refer to the trace file of statisticsserver. This file has the more detailed information.
7
HOW TO HANDLE ALERT STORAGE SNAPSHOT IS PREPARED
Confirm: To confirm that the storage snapshot has been saved to a new storage location, choose Confirm.
You can specify an external ID to identify the storage snapshot later in the storage system.
Abandon: If the storage snapshot cannot be created or if confirmation fails, choose Abandon.
Optionally, you can add a comment to explain why the storage snapshot was not successful.
8
HOW TO HANDLE ALERT STORAGE SNAPSHOT IS PREPARED
Of course, you could also use the SQL command to confirm or abandon the storage snapshot.
To confirm the storage snapshot, use the following SQL command: BACKUP DATA CLOSE SNAPSHOT BACKUP_ID
<BACKUP_ID> SUCCESSFUL <EXTERNAL_ID>
If the storage snapshot was created successfully, specify an external ID to identify the storage snapshot if you
need to use it for a recovery at a later time.
The external ID can be, for example, an ID returned by an external storage tool.
Maximum length: 64
To abandon the storage snapshot, use the following SQL command: BACKUP DATA CLOSE SNAPSHOT BACKUP_ID
<BACKUP_ID> UNSUCCESSFUL [<string>]
If the storage snapshot was not created successfully, or if you do not want to use it, it is recommended to add a
comment to more easily be able to identify the storage snapshot in the backup catalog. Maximum length: 256
9
HOW TO HANDLE ALERT STORAGE SNAPSHOT IS PREPARED
See also:
10
HOW TO HANDLE ALERT STORAGE SNAPSHOT IS PREPARED
Keywords:
11
www.sap.com
Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are
registered trademarks of Crossgate AG in Germany and other
countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of
their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.