Outlook PST file backups are failing with UNKNOWN MAPI ERROR or PST file is locked during backup.

book

Article ID: 100008726

calendar_today

Updated On:

Description

Error Message

Job Log on the DLO Client:

Backup - c:\mail\UserName.pst\Sent Items\000000000B0328BB443E384AB2B93415B32BFE37647E2300 - Mapi unexpected error.  (The Desktop Agent cannot back up this personal folder file because the file has reached its maximum size. ) (Unknown Mapi error )  -
Backup - c:\mail\UserName.pst\Sent Items\filename.pptx FAILED to copy to the network user data folder. The Desktop Agent cannot back up this personal folder file because the file has reached its maximum size.   

Error when Outlook PST files are locked:

Cannot start Microsoft office outlook cannot open outlook window the set of folders cannot be opened. the file D:\My Documents\.... pst is in use and cannot be accessed. close the application that is using this file, and then try again. you might need to restart your computer.

Cause

This issue is generally seen when MAPI based PST backup is used and the option "Enable message level incremental backups ONLY to desktop user data folder and perform file backups to network user data folder after every xx minutes" is used.

Resolution

With effect from SDLO 7.0, VSS enabled PST backups are supported. Use this option for the PST backups and enable "Delta File Transfer" to perform incremental backups of PST.

  1. In Profile properties go to Options tab
  2. Check "Enable VSS backups of Outlook PST files after every xx minutes"
  3. Check "Ignore PST files which have not been configured in Outlook" to ignore the PST files from backup which are not configured in Outlook
  4. Go to backup Selections Tab and highlight Outlook PST Files and click on Modify...
  5. Go to Options Tab and Check "Delta File Transfer"
  6. Apply the changes and run the backups again.
 

Applies To

 

Issue/Introduction

The backup of PST files using Veritas Desktop and Laptop Option (SDLO) 7.0 or later Agent locks Outlook PST or fails with the following error: