Solution : https://service.sap.com/sap/support/notes/1297986 (SAP Service marketplace login required)
Summary :
During on-site or remote SAP services (TFC/TIC/SMA), customers might find that their backup and restore plan needs adjustments or is altogether absent. This SAP Note underscores interventional strategies in high availability and recovery frameworks, specifically for MS SQL Server-incorporated SAP applications (versions 2000, 2005, 2008). It recommends maintaining backups daily and preserving transaction logs for sound data retrieval, complemented by regular test restores. Additionally, geographically distributed storage is advised for disaster resilience. Critically, a budget-effective yet reliable backup strategy is integral, balancing between direct and indirect financial losses related to system downtime against the Total Cost of Ownership (TCO) of the backup solution.
Key words :
terms db backup restore recovery high availability corruption cluster mscs reason, long retention period increases total costs, single full db backup set guarantees, usual backup excludes empty pages, native atomic t-sql command, store multiple full db backups, called microsoft cluster services, store full db backups, achieve effective high availability, provide true high availability
Related Notes :
| 1597910 | Handling of database corruptions on SQL Server |
| 1420452 | FAQ: Restore and recovery with MS SQL Server |
| 1101017 | Log shipping on SQL Server 2005 |
| 965908 | SQL Server Database Mirroring and SAP Applications |
| 437160 | MS Disaster Recovery Articles for MS SQL Server |
| 434645 | Point-in-time recovery: What must I be aware of? |
| 193816 | Restore with SQL Server |
| 81692 | Suspect database |
| 50990 | DB-Backup/Restore of Microsoft SQL Server |
| 44449 | Backup strategies with the SQL server |