Sharepoint list - backup

(1) Share

Report

Posted on by gikido

1,032

Hello everyone,

I have a Power Apps canvas application whose database is a SharePoint list, and I would like to know if there is a backup option similar to SQL Server. If not, what other options are available to roll back in case of an error?

Thank you

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

WarrenBelz 155,838 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @gikido,

A couple of choices here - if you are simply concerned about errors, SharePoint has version control, so you can go back on any record and restore a previous version. If the record was deleted in error, it will be in the recycle bin for 90 days.

Going a bit further, you could manually export the list to Excel or CSV (from the native SharePoint interface), or have a regularly timed Flow (daily/weekly) to copy it to a backup sharepoint list.

It really depends what you are trying to achieve here.

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥
Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No
Suggested answer

Haque 3,653 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @gikido,

Unfortunatley, SharePoint lists don’t have a built‑in backup/restore mechanism what you would think if it could be triggered from Power Apps! Additionally, there’s no “transaction log” or rollback option in the same sense as a relational database. But, we do have differetn practical options to prevent data loss in case someting happens erroneous.

What you can do inside SharePoint:

Enable Versioning: SP list supports version history, if enabled, every modification creates a new version what you can plan for roll back to.

Utilize recycle bin's retention period - as deleted items go there, you can restore them until retention period expires (there is a default 93 days retention).

EXIM - export the list regularly to Excel or csv as a manula backup, you can re-import if needed. You can utilize power automate to schedule exports to OneDrive/another SP list - simplistic automation.

A SP site admin task which is site collection backup - SP online supports Site Colleciton Backup/Retore, if it is in practice - it is broader than list but prevents data!

Automation:

Already mentioned in point-3 above, you can build a flow that copies new/updated items into a secondary backup list. You desitnation source can be one of many - like file storage (OneDrive), Datavere, SQL serverm, also Azure blob storage.

Tools like AvePoint or ShareGate offers SPO backup solutions with granular restore options - if you need enterprise-grade level rollback - you have the option to spend!!

Please let me know which one you pick and where additional help is needed, mention @Haque.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!
SharePoint (Online) does NOT provide SQL-like full backup/restore (point-in-time rollback)

Instead, it provides partial recovery mechanisms

Available options

Version History → Restore previous versions of individual items

Recycle Bin → Recover deleted items

Microsoft backup (internal) → Only via support, not practical

Recommended approach

Enable versioning (must-have)

Use Microsoft Power Automate to create regular backups (Excel / another list)

Maintain a backup/shadow list for rollback

Key limitation

No full list/database rollback like SQL — recovery is item-level only

Best practice

Combine Versioning + Backup Flow + Backup List for safety

Thanks
Manish

Visit my blog : https://powerappbuilder.blogspot.com/

Was this reply helpful? Yes No
Suggested answer

DP_Prabh 381 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @gikido,

Native Microsoft retention isn’t enough: Recycle bins and short retention windows don’t deliver full compliance or ransomware protection.

Third‑party backup is essential for safeguarding SharePoint Online and on‑premises data against accidental deletion, corruption, and cyberattacks.

Business continuity and disaster recovery (BC/DR) are different but complementary: Continuity keeps operations running, DR gets things back up after major incidents.

Regulatory compliance requires verifiable backups: Immutable storage and audit‑ready recovery logs prove readiness.

Automation and orchestration cut recovery time: Policy‑driven jobs and one‑click testing ensure service level agreements (SLAs) are met.

Reference: Best Practices for Backing Up SharePoint | Veeam

SharePoint Backup and Restore (Native + Third-Party Options)

I hope this works for you!

Was this reply helpful? Yes No
WarrenBelz 155,838 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

@gikido,

A quick follow-up to see if you received the answer you were looking for. Happy to assist further if not.

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥
Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No