About the Epic-Large-File policy type
The Epic-Large-File policy uses multistreaming to speed up backup and restore performance for large files. The policy is targeted for the applications such as the medical record application EPiC Database for a single large file or a few large files.
Things to consider:
An Epic-Large-File policy supports the MSDP storage units and the AdvancedDisk storage units. Some options in policy settings may apply only to MSDP storage units. For example, client-side deduplication applies only to MSDP storage units.
We recommend that you use the same storage type with the similar capabilities such as performance, capacity, and network bandwidth. If the storage is WORM, all of them must have the same retention settings.
Settings to allow the parallel streams:
On the primary server, set to the appropriate value.
On the storage unit, set to the appropriate value.
For the Epic-Large-File policy, one backup selection may be split into multiple jobs. Each child job displays one file path under the File List in the Activity monitor.
Create bpstart_notify and bpend_notify scripts for an Epic-Large-File policy.
An Epic-Large-File policy ignores the generic bpstart_notify and bpend_notify scripts. You must include the .<policyname> or .<policyname.schedule> suffix to the script name or it does not run at the start or end of the policy.
Examples:
UNIX
/usr/openv/netbackup/bin/bpstart_notify.epic_file
/usr/openv/netbackup/bin/bpend_notify.epic_file.full
Windows
<installation_directory>\NetBackup\bin\bpstart_notify.epic_file.bat
<installation_directory>\bin\bpend_notify.epic_file.full.bat
For more information about the scripts, see the NetBackup Administrator's Guide, Volume II.
To restore the Epic-Large-File policy backups, use nbepicfile command. For more information, see the nbepicfile command in the NetBackup Commands Reference Guide.