# Additional Considerations

+ It is recommended to deploy `BR` on a node with at least 8 cores `CPU` and 16 `GB` memory
+ If `TiDB` cluster is in the public cloud or have direct connection to public cloud, save backup data to the cloud object storage
+ Allocate sufficient resources for backup and restoration

----------------------------------------------------------
`BR`, `TiKV` nodes, and the backup storage system should provide network bandwidth that is greater than the backup speed. If the target cluster is particularly large, the threshold of backup and restoration speed is limited by the bandwidth of the backup network.

The backup storage system should also provide sufficient write/read performance (`IOPS`). Otherwise, the `IOPS` might become a performance bottleneck during backup or restoration.

`TiKV` nodes need to have at least two additional `CPU` cores and high performance disks for backups. Otherwise, the backup might have an impact on the services running on the cluster.

If no `Network File System` (`NFS`) is mounted to a `BR` or `TiKV` node, or if you use external storage that supports `Amazon S3`, `GCS`, or `Azure Blob Storage` protocols, the data backed up by `BR` is generated at each `TiKV` node. Because `BR` only backs up the leader replica, you need to estimate the space reserved on each node based on the leader size. Because `TiDB` uses the leader count for load balancing by default, leaders can greatly differ in size. This might result in the issue that the backup data is unevenly distributed on each node.