Hi All,
We are in the process of migrating an AIX TSM server from 5.5.3 to 6.2.x.
Now I know that IBM only specifies 12GB for the server (no dedup), but I was
wondering if there is some calculation on how much memory really is
required.
The server has about 500-550 clients and will get a Diskpool
I ran into that problem a few years back. You will have to reduce your volumes.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Mueller, Ken
Sent: Thursday, April 07, 2011 9:00 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Pr
On Apr 7, 2011, at 11:07 PM, Paul_Dudley wrote:
> I currently have a lot of copypool storage tapes which are between 50 - 60%
> utilization. Expiration runs daily and I run reclaimation daily on this
> copypool, set to 50.
>
> Is there anything I can do to try and consolidate the data onto fewe
Richard,
I allocate 32 GB for a TSM 6.2 AIX server, this value is aligned with IBM TSM
specialists.
Best regards,
Kurt
-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Richard van
Denzel
Verzonden: vrijdag 8 april 2011 10:29
Aan: ADSM-L@VM.MA
>>is that the case? tdp manages the inactivating of the prior full on the TSM
>>side? so this can be related to be akin to similar to a file backup where
>>once the file is deleted (or marked inactive by TDP) the backup falls under
>>the 30 day expiration window.
<<
With rman and TSM for DB (o
Hi Timothy, yes, the ANS5283E would trigger the rc 12. The next step would
be to review the dsmerror.log for messages between the time the backup
started (around midnight?) and 00:01:42 when ANS5283E was issued to see if
there are further details about the error.
Best regards,
Andy Raibeck
IBM So
Thanks Andy,
.
Yes..the backup started around midnight
Regards
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Andrew
Raibeck
Sent: Friday, April 08, 2011 9:20 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: ANS1417W Protected system state file
'C:\
Yes, so make sure you are checking all messages between the time the backup
started and occurrence of the ANS5283E, I would think there should be
something there indicating an issue. Also note that the ANS1959I message
(from the output below) also implies that the previous system state backup
was u