RE: VTLs and backup time

What is the goal?
Is the production machine unavailable during the backup?

Knowing your goals can help us help you.
For example, we are using software replication to another machine. We pause replication and do the backups on that machine. No disruption of production. The BRMS recovery report tells us how to recover the production machine in case of failure and it even knows we do our backups on another machine.

Other people might talk about flash copy saves using SAN storage.

If you could share the summary results of the RTVDSKINF / PRTDSKINF *SYS combo we could also discuss some size comparisons between VTL.

For example, backup time of a system like this:
% of Size in
Description Disk 1,000,000 bytes
User libraries 68.86 3953405.32
User directories 1.35 77493.48
Folders and documents .00 .15
QSYS .07 4126.51
Other IBM libraries .87 50046.97
Licensed Internal Code .92 52576.27
Temporary space .61 34856.15
Unused space 27.20 1561562.54
System internal objects .10 5558.80
Objects not in a library .00 .02
QTEMP libraries .00 165.11
TOTAL 99.98 5739791.32

DSPLOGBRM TYPE(*BKU) PERIOD((1700 081722))
Date sent Time sent Message
8/17/22 23:30:03 Begin processing for control group TUE_FRIEDD type *BKU.
8/17/22 23:30:06 Starting SAVSECDTA to devices USSGVTL.
8/17/22 23:30:36 All security objects saved.
8/17/22 23:30:40 Starting save of list *LINK to devices *MEDDFN.
8/17/22 23:34:50 255380 objects saved.
8/17/22 23:35:29 Save of list *LINK complete.
8/17/22 23:35:34 Starting *ALLUSR backup, type *FULL.
8/18/22 1:43:54 Backup *ALLUSR, type *FULL complete.
8/18/22 1:44:05 Control group TUE_FRIEDD type *BKU processing is complete

I only pasted a few pertinent lines.

If you're predominantly IFS I have other lpars where IFS dwarves the library objects.

Rob Berendt