Performance is often a concern in any medium or large database.
Backup performance is often a delicate issue, because resource usage may need to be limited to within certain boundaries. There may also be a restriction on the maximum runtime for the backup, for example, if the backup runs every Sunday.
Again, restore performance may be more important than backup performance, even if backup is the more obvious concern.
If performance is a concern or is likely to be, then you should read the Planning backups recipe first.
Backup and restore performance can be improved in different ways, depending on the backup type:
Physical backup: Improving the performance of a physical backup can be done by taking the backup in parallel, that is, copying the files using more than one task. The more tasks you use, the more it will impact on the current system. When backing up, you can skip certain files. You won't need the following:
Any files...