ADSM-L

AW: [ADSM-L] AW: [ADSM-L] Fw: JBB Question(s)

2006-12-14 06:36:57
Subject: AW: [ADSM-L] AW: [ADSM-L] Fw: JBB Question(s)
From: Otto Chvosta <otto.chvosta AT MEDUNIWIEN.AC DOT AT>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 14 Dec 2006 12:36:24 +0100
Sorry, but I don't know. We are also interested where to get dbviewb.

We've got our copy in case of a Service Request ...


-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag von
Larry Peifer
Gesendet: Mittwoch, 13. Dezember 2006 19:46
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: [ADSM-L] AW: [ADSM-L] Fw: JBB Question(s)

Where can I find the tool dbviewb for JBB 5.3?  I'd like to check our
journal states with it.




Otto Chvosta <otto.chvosta AT MEDUNIWIEN.AC DOT AT> Sent by: "ADSM: Dist Stor
Manager" <ADSM-L AT VM.MARIST DOT EDU>
12/13/2006 07:13 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
[ADSM-L] AW: [ADSM-L] Fw: JBB Question(s)






Hi again,

First, thanks for all of your advices in this case.

In my department the prefered server operating system is AIX but
unfortunately I've no influence on the choice of OS at our client servers
:-(

I also heard about the new disk chaching mechnism announced for TSM 5.4 and
hope that is a possible solution for this problem ...

But first I'd to find a solution in 5.3 ...

We did a successful incremental with 'MEMORYEFFICIENTBACKUP YES' last night
(processingtime ~ 18 hours) . MemEFF seems to be the right way against
ANS1030E, but dbviewb still reports an invalid journal state. So my primary
problem is to get the journal state valid.

<Prev in Thread] Current Thread [Next in Thread>