Run and Monitor Jobs¶
Run a backup job on demand with Run now, follow scheduled runs through the jobs grid and Run history, and delete jobs and archives you no longer need.
Before you begin¶
- The job exists and its Validity is Valid (see Create a Backup Job).
- You hold the MetaMiner Tenant Admin permission.
Run a job now¶
- On the Power BI Backup tab, select the job in Backup jobs.
-
Click Run now (toolbar or right-click menu).
The MMC shows Running backup... while MMS captures the content. A large workspace can take a long time.
-
Read the result.
Result What you see Success Backup completed. Run id: .... The new archive appears in Archives. Objects could not be captured An error naming every object that failed and why, with the full Microsoft responses under the details expander. No archive is written. Other failure An error with a plain-language summary; the details expander holds the full chain.
If the job is Invalid, Run now refuses with This job is marked invalid and will not run until the problem is fixed. and lists the reasons.
TODO: confirm what happens to a Run now backup if the MMC is closed or the progress is cancelled
Source to check: run a long backup and close the MMC; check whether the run finishes on the server and appears in Run history.
Follow scheduled runs¶
Scheduled runs happen on the server whether or not an MMC is open. The tab does not update by itself: click Refresh to see the latest Last run and Last result and any new archives.
A scheduled occurrence is skipped when the previous run of the same job is still running. Runs that were in progress when MMS stopped are marked Failed when MMS starts again.
Run history¶
Select a job and click Run history.... The dialog lists every run of the job, newest first, including failed runs and runs still in progress.
| Column | Shows |
|---|---|
| When | Start time. |
| Trigger | Manual or Scheduled. |
| Result | OK, OK, with warnings, Failed or Running. |
| Reason | Why a run failed, what the warnings are about, or in progress.... |
| Archive | The archive file the run produced, or - if none (failed runs, or the archive was deleted). |
| Size | Archive size in KB. |
Select a run to read its full reason in the pane below the grid; drag the divider to enlarge it.
Image of the Run history dialog with one OK run, one OK with warnings run selected and its reason shown in the lower pane
../images/backup-restore/run-history.png
Run results¶
| Result | Meaning |
|---|---|
| OK | Every selected object was captured and the archive was written. |
| OK, with warnings | Every object was captured, but data that was asked for was not (for example, a report whose .pbix Power BI would not export). The reason lists the reports and why. |
| Failed | At least one object could not be captured, or the run could not start. No archive was written. |
| Running | The run is in progress. |
Notification emails¶
When notifications apply, MMS emails the result with the subject [<environment>] Power BI backup <result> - <job name>. The body names the job, environment, owner and result, plus the reason for a failure or the archive name and size for a success. Failed runs are always emailed; successful runs only when Also email on success is on.
Delete a job¶
- Select the job and click Delete job.
- Confirm. The job is removed; its run history is kept and its archives stay on disk until you delete them or retention removes them.
Delete an archive¶
- Select the archive in Archives and click Delete.
- Confirm Delete the archive "..." from disk? This cannot be undone. The file is removed; the run stays in run history without an archive.
Warning
A deleted archive cannot be recovered from MetaMiner. Keep at least one archive you may need to restore from.
Troubleshooting¶
Last result says not authorized - the service principal can't access this workspace
The service principal lost its workspace membership. Edit the job, go to Access, grant again and save.
A scheduled job never runs
Check that Schedule is not Manual, Validity is Valid, and the schedule's end condition has not been reached. If the first Power BI environment was enabled after MMS started, restart MMS. See Troubleshooting.