ADSM-L

Re: [ADSM-L] Restore Question

2009-02-06 10:35:38
Subject: Re: [ADSM-L] Restore Question
From: Otto Chvosta <otto.chvosta AT MEDUNIWIEN.AC DOT AT>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 6 Feb 2009 16:33:16 +0100
Andrew Raibeck schrieb:
Craig, I recommend you take a look at this flash that went out around end
of October last year, to see if it applies:

http://www.ibm.com/support/docview.wss?uid=swg21322625

Best regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html


The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 02/04/2009
10:36:38 PM:


[image removed]

Restore Question

Craig Ross

to:

ADSM-L

02/04/2009 10:37 PM

Sent by:

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Please respond to "ADSM: Dist Stor Manager"

I have an annoying issue.
I have never encountered this before.

I have 6 files, three the same, all deactivated.

TSM client states the files are this large.  Which is correct.

tsm> q backup -ina "D:\data\SHARED\Systems Operating Centre\Systems
Management C
entre\Server Team - Unix\password-safe-db\*"
           Size        Backup Date                Mgmt Class A/I
File
           ----        -----------                ---------- ---
----
         *9,224 * *B*  09-01-2009 21:37:40             DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.ibak
        *13,784 * *B*  13-01-2009 21:24:00             DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.ibak
        * 9,224*  *B*  09-01-2009 21:37:40             DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.psafe3
        *13,784*  *B*  13-01-2009 21:24:00             DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.psafe3
            *48*  *B*  09-01-2009 21:37:41             DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.psafe3.plk
            *48*  *B*  16-01-2009 22:10:24             DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.psafe3.plk


Problem is once the files are restored the files are all either 0 K or 1

KB

in size.  empty files

Restore complete with no error.
There are no errors in Act log for the backup run at these times.

Has anyone ever seen these behavior before???

Thanks everyone.

Craig



Unfortunately the only way to find out which objects are affected ist to
check the logs to find objects that growed during compression and
restore/retrieve them to a different location to see the actual filesize
! And that for all client levels since 5.4.2.0 (rel. March 2008) up to
5.5.1.0

Maybe hard work if you're looking for possible affected objects and an
inactive & good copy of them.

We randomly tested out some growing objects backed up whith different
client levels and found NO bad copies. But I'm sure bad copies are out
there ...

Regards,
Otto

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