MVSFORUMS.com

[jsrueg]

We recently completed a DASD refresh and we opted to migrate off 3390-3's to 3390-9's and 3390-27's. We have had to change our daily and weekly volume backups from a physical to logical dump with the following additional sub-keywords of SHARE and WAIT(1,2). This however causes some datasets to not get backed up as we do not get standalone time for our backups. We were forced into this as the physical dumps were causing RESERVE's (converted to global ENQUEUES by CA-MIM) spent hours thrashing due to the ongoing batch. Apparently this occurred on the smaller devices but it happened in such a short time (1/9th the # of datasets) that it did not cause a problem.
Doe's anyone have any similar experiences to share?
_________________
OLDMVSER

[expat]

Depending on the DASD sub system you have, the number of volumes defined and in in use, and any additional features that have been purchased, you can start by taking a look at using CONCURRENT copy.

If you have Flashcopy / Snapshot / SRDF / TIMEFINDER / REPLICATOR installed, take a look at the the product documentation to see how you can use the hardware and software functions to get the backups done without problems.
_________________
If it's true that we are here to help others,
then what exactly are the others here for ?

[jsrueg]

Thanks for the reply. How does one backup to tape from a "snap" copy...(duplicate volser) as I't can't be online witht the source volume at the same time?
_________________
OLDMVSER

[kolusu]