When using Spanning to perform a bulk restore in your Salesforce organization, Spanning is inputting new data into your instance. Sometimes, this new data will push your org over the allotted storage limit, which will cause the restore to not fully complete due to a "Salesforce storage limit has been reached" error. Spanning will not be able to perform any additional restore operations until some space is freed up in your Salesforce org.
Before initiating a restore, you can ensure that your org is prepared by checking its current storage status, by following these steps:
1. Log into your Salesforce account as the admin user
2. Click the 'Setup' button in the upper-right corner of the screen
3. Navigate to Data Management > Storage Usage
Here, you will see the current storage limit for your org, and the amount currently being used.
If you have any additional questions, please email Spanning Support
Why has my Salesforce storage limit been reached?
Have more questions?
Was this article helpful?
Provide feedback for the Documentation team!
Browse this section
- Enhanced Disaster Recovery support with backup data browsing in Spanning for Salesforce
- Restore Lookup Relationships
- Can I anonymize data when seeding sandboxes using Spanning?
- How do I reduce bulk restore errors using Related Object Types?
- Can I restore metadata directly from the metadata comparison results?
- How do I import metadata into Salesforce?
- How do I restore metadata into Salesforce using Spanning Backup?
- Can I restore specific fields back into my Salesforce environment?
- Can I restore specific fields for multiple records using Spanning Backup for Salesforce?
- Can Spanning restore child records when restoring parent records?
- See more