- Data Backup Procedures and Restore recovery
- What is Backup/Restore Recovery
- Are costs involved to recover data?
- SuccessFactors can restore lost data?
- Can I request a backup previous to an activity?
- What is the process and steps?
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
- SAP SuccessFactors HCM Suite
- SAP SuccessFactors Learning Management
- It is strongly recommended to request a backup prior to major configuration changes or activity (KBA 2568976).
- Remember to take Manual backups prior to making any imports or deletions that have the possibility of overwriting or deleting existing data.
- The SuccessFactors application is continually being backed up, primarily for data protection.
- Data is protected this way for both loss and corruption.
- The product is fully backed up to a point in time for both Production Data Centers and Preview Data Centers.
Data Backup Procedures
- In the event a full restore of data is needed to a point in time, clients typically turn the system off to end users until the restore has been completed.
- SuccessFactors keeps up to 30 days worth of backups of customer data.
- The Product is a full database backup on a weekly basis and incremental backups are taken daily.
- The goal is to have the ability to restore data at any point in time within the 30 day window.
- Every effort is made to fulfill requests to recover customer data due to customer or application error.
- Prior to requesting a restore from Operations, Customer Product Support will first evaluate all options to recover the data using other means (i.e. re-importing data or extracting data from the customer's test instance).
- Each restore request is evaluated on a case by case requests by Operations Management.
Note: The restore process is an entire instance restore! There is no ability for us to restore specific pieces of data into a live instance systematically. Clients should be aware once an entire copy of an instance is restored to a second instance they will be responsible for extracting the data needed and for copying said data back into production.
Important: Learning Management (LMS) and BizX require seperate restore requests to the dedicated module teams (KBA 2535588).
- There are no costs required to request for an instance restore.
- Each restore request is evaluated on a case by case basis by Operations Management and SuccessFactors Product Support.
- It typically takes 5-10 business days to perform a restore of a company instance.
- More complex or very large instances can take longer.
- Business Impact will be taken into account.
How to Request a Restore
- Determine if the data was lost within 30 days.
- Make sure the data is not recoverable using other means.
- Do you have original copies of import files? (such as listed in the first section of this article)
- Does your test instance possibly have the data? (possible if you had cloned/refresh your production data into test for example)
- Can you simply reimport new data by:
- Re-creating same data and manually uploading it to the system
- Importing again from third part systems
Note: In such situations, remember to always evaluate other alternatives on top of Restore Process, you can recover your data faster.
- Contact Cloud Product Support and submit a Support Incident using component LOD-SF-PLT-BKP. All information provided will be used when opening an internal ticket with the Operations Team.
Be sure to provide ALL of the following information:
- Business Impact
- Company Instance
- Restore Date and Time
- Data Center
- 1. We will identify the database that needs to be restored (based on data center location of the company instance)
- 2. Identify the Date and Time that it needs to be restored to. It is very important that we go back in time far enough to ensure the data we restore will contain the information needed.
3. Determine the size of the database and amount of space needed for the restore.
4. Work with the storage team to provision the storage for the restore.
5. When the storage is available, restore the whole database to a separate temporary instance.
6. (The client is responsible for this step!) Extract the data from the instance and import it into the production instance. The data may be recovered using the Export Functionalities available in the instance (KBA 2087990) and be imported back to the restored instance/environment after the restore process is completed. Note: This step is only done for data added after the restore point which the customer wishes to keep in the instance.
SF success factors biz x PLT platform LMS retrieve loss , KBA , LOD-SF-PLT-BKP , Backup, Database Restore & Disaster Recovery , LOD-SF-PLT , Platform Foundational Capabilities , How To