Agents and Components Requiring Additional Disk Space

If your environment contains any of the following agents or components, your job results directory may require more disk space than what is calculated in Job Results Directory Disk Space Calculation.

If multiple jobs are running at the same time, the job results directory must have enough space for all concurrent jobs.

Agent or Component

Feature or Option

Disk Space Requirements for the Job Results Directory

Notes

Additional Information

Microsoft SharePoint

All SharePoint agent backup jobs and all SharePoint agent restore jobs

Variable: As large as the backed up and restored data

System Requirements - SharePoint Server iDataAgent

Microsoft SQL Server

Restoring from a secondary copy with the combined stream option

Variable: As large as the restored data

You can configure a different location for the staging folder.

Configuring Data Streams for Backups Using the SQL Server Agent

Instant Application Recovery

Variable: 15% of the size of the source database, and it can be as large as the source database.

SQL Recovery Point

Backing up Analysis Services databases

Variable: As large as the backed up data

You can configure a different location for the staging folder.

Backing Up SQL Databases

Restoring an on-premise database to the Azure cloud

Variable: The staging path must have enough free disk space as large as the backed up data and additional free space to stage the Azure BACPAC file.

You can configure a different location for the staging folder.

Restoring SQL Databases from an On-Premises SQL Server to an Azure Cloud

Microsoft Windows File System

Block-Level Backup: Live Browse

Variable: 10% of the restore data, and it can be as large as the restore data

You can configure a different location for the staging folder.

Block-Level Restores

MySQL

Restore from backup copy

Variable: 10% of the restore data, and it can be as large as the restore data

Restoring a MySQL Instance to the Same Host

Table level restore

Log restore: Staging path should have sufficient space for total size of logs to be restored

Variable for recall data: 10% of the restore data, and it can be as large as the restore data

Logs will be staged to staging path and recall data will use job results directory

Restoring MySQL Tables to the Same Host

Instant Application Recovery

Log restore: Clone working directory should have sufficient space for total size of logs to be restored

Variable for recall data: 10% of the restore data, and it can be as large as the restore data

Logs will be staged to clone working directory and recall data will use job results directory

Instant Application Recovery for MySQL Server

Linux/UNIX File System

Block-Level Backup: Live Browse

Variable: 10% of the restore data, and it can be as large as the restore data

You can configure a different location for the staging folder.

Configuring Live Browse on AIX, Linux, and Solaris

Oracle

Instant Application Recovery

Variable: 15% of the size of the source database

Instant Application Recovery

PostgreSQL

Restore from backup copy

Variable: 10% of the restore data, and it can be as large as the restore data

Restoring a PostgreSQL Instance to the Same Host

Table level restore

Log restore: Staging path should have sufficient space for total size of logs to be restored

Variable for recall data: 10% of the restore data, and it can be as large as the restore data

Logs will be staged to staging path and recall data will use job results directory

Restoring PostgreSQL Tables to the Same Host

Instant Application Recovery

Log restore: Clone working directory should have sufficient space for total size of logs to be restored

Variable for recall data: 10% of the restore data, and it can be as large as the restore data

Logs will be staged to clone working directory and recall data will use job results directory

Instant Application Recovery for PostgreSQL Server

Virtualization (select hypervisors)

Block-Level Live Browse

Minimum of 20 GB

For optimal performance, the free space on the pseudomount cache should be at least 10% of the overall disk size for the cache plus the size of the data to be restored.

Live Browse, Block-Level Browse, and Metadata Collection

Virtualization (Amazon)

  • Conversion to Amazon

  • Full VM restore using proxy that is not on Amazon

Variable: As large as the size of the largest virtual machine being converted to Amazon

Converting Virtual Machines to Amazon

Restoring Full Instances

Virtualization (VMware)

Collect File Details

Variable: At least 2 percent of the total amount of data being backed up

Live Browse, Block-Level Browse, and Metadata Collection

Virtualization (VMware)

Live Recovery of VMs

The larger of the following:

  • 20 GB

  • Variable: 15% of the VM size (the sum of the sizes of all VMDKs for the VM)

You can configure a different location for the 3DFS cache.

Restoring Virtual Machines with Live Recovery

Virtualization (VMware)

Live Mount

The larger of the following:

  • 20 GB

  • Variable: 15% of the VM size (the sum of the sizes of all VMDKs for the VM) plus the expected size of writes to VMDKs during the live mount operation

You can configure a different location for the 3DFS cache.

Running a Virtual Machine Using Live Mount

Web Server

Web Console: Downloading, uploading, and previewing files

Variable: As large as the data being downloaded, uploaded, and previewed

Downloading and Uploading Files in the Web Console

Workflow

FILE_PICKER control type

Variable: As large as the files users upload to send into the workflow

FILE_PICKER Control Type

Loading...