# Restore options ```yaml restore: batchSize: numInsertionWorkers: numParallelCollections: numDownloadWorkers: maxDownloadBufferMb: downloadChunkMb: mongodLocation: mongodLocationMap: "node01:2017": "node03:27017": ``` ### restore.batchSize *Type*: int
*Default*: 500 The number of documents to buffer. ### restore.numInsertionWorkers *Type*: int
*Default*: 10 Specifies the number of insertion workers to run concurrently per collection. ### restore.numParallelCollections *Type*: int
*Default*: number of CPU cores / 2 The number of collections to process in parallel during a logical restore. The default value is half of the number of CPU cores. By setting the value for this option you define the new default. Available starting with version 2.7.0. ### restore.numDownloadWorkers *Type*: int
*Default*: number of CPU cores The number of workers that request data chunks from the storage during the restore. The default value equals to the number of CPU cores. ### restore.maxDownloadBufferMb *Type*: int
The maximum size of the in-memory buffer that is used to download files from the S3 storage. When unspecified or set to 0, the size cannot exceed the value calculated as `numDownloadWorkers * downloadChunkMb * 16` MB. By default, the number of CPU cores * 32 * 16 MB. ### restore.downloadChunkMb *Type*: int
*Default*: 32 The size of the data chunk in MB to download from the S3 storage. ### restore.mongodLocation *Type*: string The custom path to `mongod` binaries. When undefined, Percona Backup for MongoDB uses the default path to make database restarts during physical restore. ### restore.mongodLocationMap *Type*: array of strings The list of custom paths to `mongod` binaries on every node. Percona Backup for MongoDB uses the values to make restarts of the database during physical restore.