I have a job that backs up sharepoint.
Last successful run was July 9th.
The job has 4701 objects to back up. Right now, the job is at 4676/4701 objects backed up.
This job has been running for 102 hours and is stalling on one single sharepoint site. Everything else (Excluding a few warnings and errors) has already been backed up successfully. They all say successful. The job is essentially done and just needs to finish this last sharepoint site.
This last sharepoint site just refuses to finish. In 20 hours, the "total items processed" counter has gone up from 493901 to 493944. In 20 hours only 43 items from this sharepoint site have been processed.
The total job run time right now is 104 hours.
I'm on version 7.1 so I want to stop the job and upgrade to the latest version and hope that fixes something, but I don't know what the implications of this are. Does the job need to have a successful run before it marks certain items as complete in order to do an incremental run next? Will I lose all my progress and basically need to do a full back up again if I terminate this job before it can finish successfully?
Since this last sharepoint site has at least partially been backed up, if I stop the job and restart it will veeam know that some of these items are already backed up and just perform an incremental backup of the remaining items? Or do I need to let this back up job finish first for minimal data loss?
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Jul 22, 2025 1:40 pm
- Full Name: Brandon
- Contact:
-
- Product Manager
- Posts: 10664
- Liked: 2882 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: If I stop a long running job how much progress is lost?
Hi Brandon,
If you stop your job, no restore point will be logged in the database. You won't be able to perform a restore of any object in that job until the initial job run has finished successfully.
However, any items that have already been downloaded will not be downloaded again when you rerun your backup job (I run a test in my v8 lab).
Please note that the first run of your backup job with v7.1 may still require a significant amount of time. V8 will introduce a feature to resume interrupted SharePoint backups. However, with v7 or after upgrading to v8, the backup job will need to start enumerating all items in your SharePoint site from scratch.
I'll suggest to open a case with customer support before stopping your job, to make sure that everything works as expected with your current job.
Best,
Fabian
If you stop your job, no restore point will be logged in the database. You won't be able to perform a restore of any object in that job until the initial job run has finished successfully.
However, any items that have already been downloaded will not be downloaded again when you rerun your backup job (I run a test in my v8 lab).
Please note that the first run of your backup job with v7.1 may still require a significant amount of time. V8 will introduce a feature to resume interrupted SharePoint backups. However, with v7 or after upgrading to v8, the backup job will need to start enumerating all items in your SharePoint site from scratch.
I'll suggest to open a case with customer support before stopping your job, to make sure that everything works as expected with your current job.
Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: No registered users and 14 guests