ADSM-L

Re: [ADSM-L] NAS NDMP TOC will not write

2011-02-22 20:06:09
Subject: Re: [ADSM-L] NAS NDMP TOC will not write
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 22 Feb 2011 20:04:10 -0500
Hi Joni,

Yes, if you look up the ANR4949E message (you can do "help anr4949e" or
"help 4949" from the admin command line interface), it will indicate that
extending the database size is the way to go.

Best regards,

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

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 2011-02-22
16:14:28:

> From: "Moyer, Joni M" <joni.moyer AT HIGHMARK DOT COM>
> To: ADSM-L AT vm.marist DOT edu
> Date: 2011-02-22 16:18
> Subject: Re: NAS NDMP TOC will not write
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> Hi Andy,
>
> If I did get the message I had below, what is the resolution to the
> issue?  Increasing the size of the TSM database?  Or could this be a
> different issue?  This TSM database was only allotted 25 GB and I
> can extend it if necessary.  Just let me know what your thoughts are.
>
> Thanks!
>
> Date/Time             Message
> --------------------
> ----------------------------------------------------------
> 02/22/11 08:29:43     ANR4949E The server is unable to write to table
>                        NDMP.Image.Contents(TEMP) because there is not
enough
>                        temporary space in the database.  Table of
contents
>                        operation for node NAS_SERVER_2, file space /
> root_vdm_4/-
>                        HMCH1015_G_bkup fails. (SESSION: 4253, PROCESS:
903)
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> Behalf Of Andrew Raibeck
> Sent: Tuesday, February 22, 2011 4:11 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: NAS NDMP TOC will not write
>
> Joni, Allen,
>
> A lack of available temporary space in the TSM server database could
> account for no TOC being created. But indeed, if the TOC cannot be
created
> then TSM should issue some kind of message. If nothing in the activity
log
> hints at the issue, then the only thing I can suggest would be to open a
> PMR so it can be further investigated.
>
> It might be worth trying a backup with TOC=YES to see if it forces an
error
> message to be generated (other than the backup fails).
>
> Best regards,
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Product Development
> Level 3 Team Lead
> Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS
> Internet e-mail: storman AT us.ibm DOT com
>
> IBM Tivoli Storage Manager support web page:
> http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
> Tivoli_Storage_Manager
>
> "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 2011-02-22
> 15:41:26:
>
> > From: "Allen S. Rout" <asr AT UFL DOT EDU>
> > To: ADSM-L AT vm.marist DOT edu
> > Date: 2011-02-22 15:45
> > Subject: Re: NAS NDMP TOC will not write
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
> >
> > >> On Tue, 22 Feb 2011 15:20:53 -0500, "Moyer, Joni M"
> > <joni.moyer AT HIGHMARK DOT COM> said:
> >
> > > I'm backing up a 2TB filesystem through NAS NDMP protocol and it did
> > > not write the TOC.  How can I find out why it didn't write the table
> > > of contents?  I don't see an error as to why it didn't write the
> > > TOC.
> >
> >
> > "Me Too".  But mine is 12TB, 30M files.  No suggestive log messages.
> >
> > TSM server 5.5.3, on AIX.  NAS is an EMC NSG8.
> >
> >
> > - Allen S. Rout
>
> This e-mail and any attachments to it are confidential and are
> intended solely for use of the individual or entity to whom they are
> addressed.  If you have received this e-mail in error, please notify
> the sender immediately and then delete it.  If you are not the
> intended recipient, you must not keep, use, disclose, copy or
> distribute this e-mail without the author's prior permission.  The
> views expressed in this e-mail message do not necessarily represent
> the views of Highmark Inc., its subsidiaries, or affiliates.

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