On 26 mei 2010, at 21:11, Huebner,Andy,FORT WORTH,IT wrote:

> We found the problem.
> The Celerra allows the renaming of a file system, but does not change the 
> name of the file system, it only changes the name you see.
> For the TSM wish list; I need a command that lists the file systems on a NAS 
> node and an incremental forever NDMP dump.
> 

NDMP sucks, nothing IBM can do to fix that. As for Incremental forever: 
NetApp/N-Series and TSM 6.1 client with snapdiff....

> Andy Huebner
> 
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Huebner,Andy,FORT WORTH,IT
> Sent: Tuesday, May 25, 2010 5:46 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Celerra Backup problem
> 
> The backup fails in about 1 sec.
> Server_log does not show a backup or any errors that look like a backup 
> problem.
> The TSM activity log does not show anything other than the messages I 
> included.
> 
> Andy Huebner
> 
> 
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of John Parker
> Sent: Tuesday, May 25, 2010 1:35 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Celerra Backup problem
> 
> Hello,
> My organization backs up several Celerra filesystems with longer names
> than the one you are having troubles with. The return code is being
> returned from your datamover. Check the datamover logs for NDMP events
> using the server_log command on your control station. If the backup
> isn't failing immediately, you can check on the status from the control
> station using the server_pax command.
> 
> John C. Parker
> Clark County IT
> 702-455-3661
> jcp AT co.clark.nv DOT us
> 
> 
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Huebner,Andy,FORT WORTH,IT
> Sent: Tuesday, May 25, 2010 8:49 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Celerra Backup problem
> 
> I am having trouble backing up one file system on my Celerra, the other
> 23 work just fine.  I am using the exact same command to backup other
> file systems on the same VDM without trouble.  The only difference I see
> is this file system has a longer name.
> All the files systems are configured the same way.
> Is there a short file system name limitation?  Is there something else I
> can look at?
> 
> Does not work.
> backup node ns80_adcw_3 /root_vdm_4/FTW_GLOBALGRAPHICS_01 mode=full
> toc=yes
> ANR2020E BACKUP NODE: Invalid parameter -
> /root_vdm_4/FTW_GLOBALGRAPHICS_01.
> ANS8001I Return code 3.
> 
> Does work.
> backup node ns80_adcw_3 /root_vdm_4/FTW_SCM_01 mode=full toc=yes
> 
> 
> Celerra v5.6
> TSM 5.4.5
> Celerra is FC to tape drives
> 
> Andy Huebner
> 
> 
> 
> This e-mail (including any attachments) is confidential and may be
> legally privileged. If you are not an intended recipient or an
> authorized representative of an intended recipient, you are prohibited
> from using, copying or distributing the information in this e-mail or
> its attachments. If you have received this e-mail in error, please
> notify the sender immediately by return e-mail and delete all copies of
> this message and any attachments.
> 
> Thank you.
> 
> This e-mail (including any attachments) is confidential and may be legally 
> privileged. If you are not an intended recipient or an authorized 
> representative of an intended recipient, you are prohibited from using, 
> copying or distributing the information in this e-mail or its attachments. If 
> you have received this e-mail in error, please notify the sender immediately 
> by return e-mail and delete all copies of this message and any attachments.
> 
> Thank you.

-- 
Met vriendelijke groeten/Kind Regards,

Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622