Does EdbMails perform a full backup every time?

No. The first backup is full, and later runs can operate incrementally, processing only new or changed content.

Does incremental backup guarantee a fixed speed?

No. Actual performance depends on site size, changed-data volume, Microsoft 365 responsiveness, network and repository performance.

How often should incremental backups run?

Base the frequency on your RPO and how often each site changes, within the available backup window and the backup computer's availability.

Where is the incremental backup stored?

On the same customer-selected repository as the full backup — local or network storage you control.

Will incremental runs duplicate content already protected?

No. Incremental processing continues the existing protected set rather than recreating unchanged content.

When is a new full backup cycle created?

Periodically, per the application's behavior and your retention or maintenance policy. Allow repository headroom for it where applicable.

What should I check if a run seems wrong?

Confirm repository access, source connectivity, whether permissions changed, free repository space, and review logs for throttling or connectivity errors.

Can I restore from an incremental backup set?

Yes. Recovery uses the normal restore workflow at file, folder, library or site scope.

Do large sites benefit most from incremental backup?

Yes. For large sites, day-to-day changes are usually a small portion of the total, so incremental runs avoid repeatedly processing unchanged content.

Does the backup computer need to be on for recurring runs?

Yes. Scheduled runs depend on the backup computer being available and able to reach SharePoint Online at the chosen time.

Can incremental backups be limited to specific sites?

Yes. Select only the sites and content in scope; recurring runs then process changes for that scope.

Reseller
Products
EdbMails

All-in-one Recovery and Migration
- EDB Recovery and Migration
- OST, PST, MBOX, NSF, EML, MSG
- Office 365, Exchange Migration
- SharePoint, OneDrive & Teams
- Google Workspace Migration
- IMAP Migration
- Duplicate Remover
- EdbMails Data Recovery
- Backup Solutions
All Products
EDB Recovery and Migration

EdbMails lets you recover corrupted, damaged, and offline Exchange EDB files, convert EDB mailboxes to PST format, and directly migrate mailbox data to Office 365 and live Exchange Server.

EDB to PST

Recover corrupted, damaged, offline EDB files and convert Exchange EDB mailboxes to PST file format

Public Folder to Exchange

Migrate public folders from an Exchange offline EDB file to live Exchange Server

EDB to Live Exchange Migration

Directly migrate offline Exchange database (EDB) files to live Exchange server

Archive Mailbox to Office 365

Migrate archive mailboxes from offline EDB files directly to Office 365

EDB to Office 365 Migration

Directly migrate offline Exchange database (EDB) files to Office 365

Public Folder to Office 365

Migrate public folders from an offline Exchange EDB file to Office 365

OST, PST, MBOX, NSF, EML, MSG Export and Migration

EdbMails lets you to recover OST and PST files, export OST, PST, MBOX, NSF, EML, and MSG files to PST files, and directly migrate OST, PST, MBOX, and NSF mailbox data to Office 365 and live Exchange Server.

OST Recovery and Migration

Recover offline OST files, convert OST to PST, and migrate OST to Office 365 and Exchange Server

PST Recovery and Migration

Recover Outlook PST files , Export PST to PST, migrate PST to Office 365 and Exchange Server

MBOX Export and Migration

Export MBOX to PST, migrate MBOX to Office 365 and Exchange Server

NSF Export and Migration

Export NSF to PST, migrate NSF to Office 365 and Exchange Server

EML to PST Export

Convert EML files to Outlook PST files

PST to MSG Export

Convert Outlook PST file to MSG file format

MSG to PST Export

Export MSG files to Outlook PST files

Office 365, Exchange Migration

EdbMails lets you securely migrate mailboxes across Microsoft 365, Exchange, Google Workspace (G Suite), and IMAP-supported servers such as Outlook, Gmail, Zimbra, Zoho Mail, and cPanel, ensuring zero downtime.

Office 365 Migration

Migrate between Office 365 tenants, Office 365 to Exchange, Office 365 to PST, PST files to Office 365.

Exchange Migration

Migrate between any Exchange Servers, Exchange to Office 365, Exchange to PST, PST files to Exchange.

Tenant to Tenant Migration

Migrate Mailboxes, Public Folders, Archive Mailboxes between Office 365 Tenants.

Exchange to Office 365

Migrate Mailboxes, Public Folders, Archive Mailboxes from live Exchange server to Office 365.

Office 365 to IMAP

Migrate Office 365 to IMAP, Office 365 to Gmail, Office 365 to Outlook, Office 365 to Zoho etc.

Exchange to IMAP

Migrate from live Exchange Server to IMAP servers such as Gmail, Outlook, and Zoho Mail.

Public Folder to Office 365

Migrate Public Folders between Office 365 tenants with complete folder hierarchy and mailbox data integrity.

Exchange to PST

Export live Exchange Server mailboxes, public folders, and archive mailboxes to Outlook PST files.

SharePoint, OneDrive & Microsoft Teams Migration

EdbMails lets you migrate SharePoint sites, OneDrive data, Microsoft Teams, teams, channels, chats, permissions, and documents between Microsoft 365 tenants while maintaining the existing folder structure and data integrity.

SharePoint Online Migration

Migrate documents, lists, files and folders from SharePoint sites.

OneDrive for Business Migration

Migrate documents, lists, files, folders, private chats from OneDrive.

Microsoft Teams Migration

Migrate Teams, chats, channels, documents, files and folders etc.

Google Workspace / G Suite Migration

EdbMails offers secure Google Workspace migration to Office 365, Exchange, or IMAP, and export to PST covering emails, contacts, calendars and tasks.

Google Workspace Migration

Migrate emails, calendars, contacts, tasks from Google Workspace to Google Workspace, office 365, Exchange and IMAP. Export to PST

Google Workspace to Office 365

Migrate emails, calendars, contacts, tasks from Google Workspace / G Suite to Office 365

Google Workspace to Exchange Server

Migrate emails, calendars, contacts, tasks from Google Workspace / G Suite to on-Premise Exchange Server

Google Workspace to IMAP

Migrate emails, calendars, contacts, tasks from Google Workspace / G Suite to IMAP, Outlook, Zimbra, Zoho etc.

Google Workspace to Google Workspace

Migrate emails, calendars, contacts, tasks between two Google Workspace / G Suite tenants

Google Workspace to PST

Export emails, calendars, contacts, tasks from Google Workspace / G Suite to Outlook PST files

IMAP Migration

EdbMails IMAP Migration tool lets you easily migrate emails from IMAP servers such as Outlook, Gmail, Zoho Mail, Zimbra, cPanel, and more. Supports IMAP to IMAP, Office 365, Exchange Server, PST, and bulk PST to IMAP migration.

IMAP Email Backup & Migration

Backup and migrate emails from IMAP servers to PST, Office 365, and On-Premises Exchange Server

IMAP to Office 365

Migrate emails, folders, and attachments from IMAP servers to Office 365

IMAP to Exchange

Migrate emails, folders, and attachments from IMAP servers to on-premises Exchange Server

IMAP to PST

Export emails, folders, and attachments from IMAP servers to Outlook PST files for backup

PST to IMAP

Migrate emails, folders, and attachments from bulk PST files to IMAP servers

Duplicate Remover

EdbMails Duplicate Remover lets you easily remove duplicate items from Office 365 and Exchange Server, and from IMAP, Outlook, Gmail, Zimbra, Zoho Mail, etc., ensuring a clean and organized mailbox.

Remove Duplicates

Easily clean up your Office 365, Exchange, Outlook and IMAP accounts by removing duplicate emails.

Remove Duplicates from Office 365

Remove duplicate emails, calendars, contacts, journal tasks, etc. from Office 365.

Remove Duplicates from Exchange Server

Remove duplicate emails, calendars, contacts, journal tasks, etc. from live Exchange Server.

Remove Duplicates from IMAP, Outlook

Remove duplicate emails, attachments from IMAP, Outlook, Gmail, Zimbra, Zoho Mail etc.

Exchange, SharePoint, OneDrive, Teams and Office 365 Backup

EdbMails enables secure, automated backup and recovery for Microsoft 365 services including Exchange Online, SharePoint, OneDrive, Teams, and Live Exchange Server with complete data protection and restore flexibility.

Office 365 Backup

Incremental, Granular, Encrypted and Compressed Office 365 Mailboxes Backup

Exchange Server Backup

Incremental, Granular, Encrypted and Compressed Exchange Mailboxes Backup

SharePoint, OneDrive & Teams Backup

Backup Online site collections, Team sites, Office 365 groups, all documents etc.

EdbMails Data Recovery

EdbMails Data Recovery Software lets you recover permanently deleted data, including photos, videos, documents, and archived files, from partitions on hard drives, SSDs, USB drives, SD cards, and external storage devices.

EdbMails Data Recovery

Recover and restore permanently deleted data from hard drives, SSDs, USB drives, SD cards, and etc.

Whitepaper

Request a Demo

Sign Up

SharePoint Incremental Backup

Protect new and changed SharePoint content after the first backup

EdbMails supports full and incremental SharePoint Online backup, so after the first full copy exists, later runs process only new or changed content instead of rebuilding the entire backup every time. This keeps the protected copy current without repeatedly handling unchanged files.

Just $299 for 100 sites

Restore SharePoint Sites OneDrive Backup Restore OneDrive Data Office 365 Groups Backup Office 365 Backup Exchange Server Backup

SharePoint, OneDrive and Teams Backup Tool Now on Azure Marketplace!

Product Menu

SharePoint Incremental Backup

Download View SharePoint Backup

What is an incremental SharePoint backup?

The first run for a backup set establishes the full protected copy. Consecutive runs for that same set then process the content that was added or changed since the previous protected state. Because SharePoint sites change continuously as users add and edit files, incremental processing avoids repeatedly copying content that has not changed.

Full vs incremental backup

Type	Purpose	When used
Initial full backup	Creates the baseline protected state for the selected scope	First run for the backup set
Incremental backup	Processes new or changed content after the baseline	Recurring runs after the first backup
New full cycle	Establishes a fresh baseline per the application and your policy	Periodic repository maintenance or retention

Why incremental backup matters

Reduce repeated processing

Large SharePoint sites contain many unchanged files. After the baseline exists, incremental runs avoid treating every unchanged file as new work.

Control storage growth

Incremental processing adds changes to the protected set rather than recreating unchanged content on every run, which helps keep repository growth proportionate to real change.

Keep the protected copy current

Running incremental jobs on a schedule narrows the gap between the latest protected state and the live site, which is the whole point of a recovery point objective.

How EdbMails incremental backup works

Step 1Create the SharePoint backup job and select the sites and content scope.

Step 2Run the first backup to establish the full protected copy.

Step 3Run the same job again later.

Step 4Allow EdbMails to process the changed content against the existing protected state.

Step 5Review the logs to confirm the expected content was processed.

Incremental backup and recovery point objectives

The frequency of recurring backups should be driven by how much recent change the organization can afford to lose — its RPO. Highly active project sites may justify more frequent runs than low-change archival sites. A tighter RPO means more frequent incremental runs; a looser one allows longer intervals. Meeting any RPO depends on scheduling the jobs accordingly and verifying that they complete.

Scheduling guidance

Match the schedule to real site activity and to the available backup window, rather than applying one fixed interval to every site.

Fit runs to when the backup computer is available and able to reach SharePoint Online.

Revisit the schedule when site activity, the number of protected sites or recovery requirements change.

When to consider a new full backup cycle

Organizations may periodically establish a new baseline as part of repository maintenance, retention or operational policy. The exact behavior should follow the current EdbMails application and your backup procedure rather than an assumed fixed interval. Allow repository headroom for a new full cycle where applicable.

Repository maintenanceRetentionOperational policy

Performance factors

Number and size of protected sites.

Volume of new or changed content since the previous run.

Microsoft 365 responsiveness and throttling.

Network throughput between the backup computer and Microsoft 365.

Repository read/write performance.

Incremental processing reduces repeated work, but it does not guarantee a fixed speed; actual duration remains environment-dependent.

Monitoring and troubleshooting incremental runs

After each run

Review the logs after each run to confirm the expected content was processed.Logs

Watch for runs that process far more or far less than expected, which can indicate a scope or connectivity change.Change size

Verify access to the same backup repository used by earlier runs.Repository

Confirm source-site connectivity and whether site permissions changed.Connectivity

Check for throttling or connectivity errors and confirm sufficient free repository space.Throttling & space

Restore from an incremental backup

Protected SharePoint content can be selected and recovered through the normal restore workflow at file, folder, library or site scope, to the same or a different tenant. See SharePoint Online backup and restore.

Related SharePoint Backup resources

Frequently asked questions

Does EdbMails perform a full backup every time?
No. The first backup is full, and later runs can operate incrementally, processing only new or changed content.
Does incremental backup guarantee a fixed speed?
No. Actual performance depends on site size, changed-data volume, Microsoft 365 responsiveness, network and repository performance.
How often should incremental backups run?
Base the frequency on your RPO and how often each site changes, within the available backup window and the backup computer's availability.
Where is the incremental backup stored?
On the same customer-selected repository as the full backup — local or network storage you control.
Will incremental runs duplicate content already protected?
No. Incremental processing continues the existing protected set rather than recreating unchanged content.
When is a new full backup cycle created?
Periodically, per the application's behavior and your retention or maintenance policy. Allow repository headroom for it where applicable.

What should I check if a run seems wrong?
Confirm repository access, source connectivity, whether permissions changed, free repository space, and review logs for throttling or connectivity errors.
Can I restore from an incremental backup set?
Yes. Recovery uses the normal restore workflow at file, folder, library or site scope.
Do large sites benefit most from incremental backup?
Yes. For large sites, day-to-day changes are usually a small portion of the total, so incremental runs avoid repeatedly processing unchanged content.
Does the backup computer need to be on for recurring runs?
Yes. Scheduled runs depend on the backup computer being available and able to reach SharePoint Online at the chosen time.
Can incremental backups be limited to specific sites?
Yes. Select only the sites and content in scope; recurring runs then process changes for that scope.