ADSM-L

[ADSM-L] NDMP backup successful but incomplete

2008-06-12 17:43:50
Subject: [ADSM-L] NDMP backup successful but incomplete
From: Robben Leaf <robben.leaf AT USBANK DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 12 Jun 2008 16:42:39 -0500
I've got an NDMP client (Celerra) with two file systems - /vol0, and /vol1.
When I run the backup (fulls only), /vol1 gets a complete backup, but /vol0
backs up only a few kilobytes, and the process ends as Successful.

To be more specific:

06/12/08 10:17:12     ANR2017I Administrator RNLEAF issued command: BACKUP
NODE
                       SVGMN14GLBSM07 /vol0 mode=full  (SESSION: 36846)

06/12/08 10:17:14     ANR1063I Full backup of NAS node SVGMN14GLBSM07, file

                       system /vol0, started as process 552 by
administrator
                       RNLEAF. (SESSION: 36846, PROCESS: 552)

...
06/12/08 10:17:37     ANR0988I Process 552 for BACKUP NAS (FULL) running in
the
                       BACKGROUND processed 43,482 bytes with a completion
state
                       of SUCCESS at 10:17:37. (SESSION: 36846, PROCESS:
552)

and...

06/12/08 10:17:14     ANR2017I Administrator RNLEAF issued command: BACKUP
NODE
                       SVGMN14GLBSM07 /vol1 mode=full  (SESSION: 36846,
PROCESS:
                       552)

06/12/08 10:17:16     ANR1063I Full backup of NAS node SVGMN14GLBSM07, file

                       system /vol1, started as process 553 by
administrator
                       RNLEAF. (SESSION: 36846, PROCESS: 553)

...
06/12/08 15:26:39     ANR0988I Process 553 for BACKUP NAS (FULL) running in
the
                       BACKGROUND processed 620,126,384,679 bytes with a

                       completion state of SUCCESS at 15:26:39. (SESSION:
36846,
                       PROCESS: 553)

Now, the administrator of the Celerra can demonstrate that /vol0 has plenty
of data in it:

[nasadmin@us_bank_cs702_5948 nasadmin]$ nas_fs -size vol0
total = 1578910 avail = 900497 used = 678412 ( 42% ) (sizes in MB)
( blockcount = 3283714048 )
volume: total = 1603376 (sizes in MB) ( blockcount = 3283714048 ))
[nasadmin@us_bank_cs702_5948 nasadmin]$ nas_fs -size vol1
total = 1578910 avail = 985584 used = 593326 ( 37% ) (sizes in MB)
( blockcount = 3283714048 )
volume: total = 1603376 (sizes in MB) ( blockcount = 3283714048 ))

I see something similar when I look at the information TSM has about that
file space:

q filespace SVGMN14GLBSM07 /vol0 f=d

                                      Node Name: SVGMN14GLBSM07
                                 Filespace Name: /vol0
                     Hexadecimal Filespace Name:
                                           FSID: 2
                                       Platform: DartOS
                                 Filespace Type: uxfs
                          Is Filespace Unicode?: No
                                  Capacity (MB): 1,578,910.2
                                       Pct Util: 43.0
                    Last Backup Start Date/Time: 06/12/08 10:17:13
                 Days Since Last Backup Started: <1
               Last Backup Completion Date/Time: 06/12/08 10:17:36
               Days Since Last Backup Completed: <1
Last Full NAS Image Backup Completion Date/Time: 06/12/08 10:17:36
Days Since Last Full NAS Image Backup Completed: <1



I don't know what kind of settings he might have on his end that might
affect how TSM accesses, or fails to access, a file system on the Celerra.
As you can see, the commands issued to invoke the backups are identical. No
client option sets are applied to the node.

TSM server is ver 5.3.5.2 on AIX 5.3; backing up to a VTL emulating a 3584
with LTO drives. If the version of DART on the Celerra matters, I'll dig it
up.

Does anyone have a theory as to why the /vol0 backup isn't backing up the
data that's there, while the backups of /vol1 are working fine?,

Thanks in advance!

Robben Leaf


U.S. BANCORP made the following annotations
---------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



---------------------------------------------------------------------

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