schedule.
>
> Regards,
>
> Joerg
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> Prather, Wanda
> Sent: Sunday, February 02, 2014 12:23
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Prevent client backu
using an admin schedule.
Regards,
Joerg
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Sunday, February 02, 2014 12:23
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Prevent client backups from failing over to tape
stgpools
Oh, that's brilliant!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven
Harris
Sent: Friday, January 31, 2014 8:23 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Prevent client backups from failing over to tape stgpools
Brian
TSM
Brian
TSM will only move a backup to the next pool when the pools are disk and
sequential, not when sequential and sequential, so I suggest adding a
dummy sequential pool with no volumes assigned in the middle.
disk -> dummy -> tape
I've come across this when using an intermediate file pool. It
If the tape pool is in a separate device class from other storage pools, you
could set the mount limit on the device class to 0. That's our strategy when we
do library maintenance to allow operations to continue to/from our disk and
file pools.
On Thu, Jan 30, 2014 at 10:47:46AM -0800, Brian Ku
kups from failing over to tape stgpools
Brian -
The most common way to achieve your goal is to do an UPDate STGpool, with
ACCess=READOnly.
Richard Sims
Brian -
The most common way to achieve your goal is to do an UPDate STGpool, with
ACCess=READOnly.
Richard Sims
We’re in a situation where we want to temporarily prevent our users from ever
writing directly to our tape drives. In the event that our primary random
access stgpools hit 100% utilization, we want client backups to fail rather
than failover over to the next, sequential access stgpool. As fa
