Idea ID: 1638649

Backup a single file system with multiple streams

Status: Accepted

Brief description:

While file systems continue to grow and the underlaying disk subsystems become faster the backups of large file systems are still one of the major concerns for traditional backup environments. The Data Protector Disk Agent should support multiple streams on a single file system that can be configured similar to device concurrency to drastically speed up the backup and the restore operation.

Picture1.png

Existing Enhancement Requests:

QCCR2A62413: Support multiple disk agents per volume

Benefit:

Reduce the complexitiy of subdividing file systems manually into smaller pieces. Optimize for backup and restore performance using multiple streams even on large file systems with millions of files and folders.

Tags:

Parents
  •  I would think that the multi-thread read would be effectively transparent to the existence of a single object.  That is to say, if a VBDA for WINFS object "F:/Users" or a VBDA for FILESYSTEM object "/var" decides to multi-thread for read efficiency during backup,  the objects "F:/Users" and "/var" should remain monolithic objects in the IDB and for the purposes of object copy, restore, and verification.  Otherwise, you'll have what you see now with manual divide and conquer where a restore context presents multiple "F:/Users" objects or multiple "/var" objects for restore, and you have to pray that you used good object descriptions in the backup spec to give yourself a clue which rabbit hole to jump down for restoring a specific folder or file.

Comment
  •  I would think that the multi-thread read would be effectively transparent to the existence of a single object.  That is to say, if a VBDA for WINFS object "F:/Users" or a VBDA for FILESYSTEM object "/var" decides to multi-thread for read efficiency during backup,  the objects "F:/Users" and "/var" should remain monolithic objects in the IDB and for the purposes of object copy, restore, and verification.  Otherwise, you'll have what you see now with manual divide and conquer where a restore context presents multiple "F:/Users" objects or multiple "/var" objects for restore, and you have to pray that you used good object descriptions in the backup spec to give yourself a clue which rabbit hole to jump down for restoring a specific folder or file.

Children
No Data