# Backup creation failed

Last updated: July 24, 2026

## Problem

You cannot create a backup of the database. The error message that you see on the screen is, 'Database backup failed'.

## Cause

You cannot create a backup of the database because of one of the following reasons:

Specified directory is write-protected, invalid or inaccessible.

Insufficient space in the specified drive.

Temp Folder is full.

## Resolution

You are required to identify why you are not able to create the database. Follow the relevant resolution:

***Specifying a valid folder name that is not write-protected***

Specify a valid folder name for the backup directory path. If you're using a network share, the directory should have write permission for everyone in the network.

**Scenario**

Assume that you have created a folder called Database Backup in a computer (not the computer where the Mobile Device Manager Plus server is installed) in your network. This folder will be used to store all the database backup that is created every week. To enable all the users in your network to access this folder to store their database backup, you must give them share permissions. To share a folder and give share permissions to everyone in the network, follow the steps given below:

1. Navigate to the required folder.
2. Right-click on the folder.
3. Click **Properties**.
4. Click **Sharing**.
5. Click **Share this folder**.
6. Enter a name for the folder.
7. Click **Permissions**.
8. Click **Add**.
9. Choose **Object Types**.
10. Enable **Computers**.
11. Click **OK**.
12. Under **Enter Object Name**, specify the server name and the username with administrator privileges.
13. Click **Share Permission** and select **User** and **Computer**. Ensure **Full Control** is enabled.
14. Click **OK** to complete the process.

**Note**: Repeat steps 13 and 14 to complete the process.

**Note:** Ensure that you share the folder with the server machine that has the required permissions to transfer data.

***Ensuring that there is enough space in the required drive***

Check the amount of free space in the drive. If there isn't enough space do one of the following:

- Delete or move unwanted files.
- Extend the hard drive capacity.
- Change the backup directory to another drive.

**Changing the backup directory to another drive**

To change the backup directory to another drive, follow the steps given below:

1. Click the **Admin** tab.
2. In the **Tools** section, click **Database Backup**.
3. In the **Backup directory** field, specify a new drive to save the backup in.
4. Click **Save Changes**.

You've changed the backup directory to another drive. Follow the steps given in the follow up section below, to check if you can create a backup.

***Clear Temp Folder***

Ensure that you clear up the temp folder in the Server machine before trying to take a back up. To clear the folder, follow the steps mentioned below.

1. Click **Start->Run**.
2. Type **%temp%** and press **Enter**.
3. Clear the temp folder's content.

## Follow Up

After using the required solution, mentioned in the section above, you can check manually whether the database backup takes place successfully. To create a backup of the database manually, follow the steps given below:

1. Click **Start->Run**.
2. Enter cmd.
3. Click **OK**.
4. Navigate to <Install_Directory>/MDMServer/bin directory.

   **Note:** This is where the folder MDMServer is stored. For example, the path could be D:\>MDMServer.

5. Run backuprestore.bat to view the Backup/Restore Graphical User Interface (GUI).
6. Click the **Backup** tab.
7. Select the location where you want to save the backup file.
8. Click **Backup**.

   **Note**: Mobile Device Manager Plus first estimates how much space is available in the specified drive where you want to store the backup file.

You have created the backup file. The backup file is stored at the location you chose. The naming format is buildnumber-date-time.zip. For example, 70117-Jul-23-2010-11-26.zip

**Applies to:** Database backup, Creation

**Keywords:** Database backup-creation failure, Version incompatibility