Frank I don't know I will ask the Novell administrator .
Regards Robert -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Frank Sent: Tuesday, May 09, 2006 7:30 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Novell question !!!!!! Did the volume get created new on this netware 6.5 server, or it get created earlier, on a previous version of netware (and was eventually migrated to nw6.5)? >>> [EMAIL PROTECTED] 5/9/2006 11:25 AM >>> Andrew I install TSA5UP19 and still I see in volume EV1: the filenames in Dos format , by the way in SYS: and Vol1: volumes no problem I got long filename!!!!! Thanks Robert -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Ferris Sent: Tuesday, May 09, 2006 5:57 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Novell question !!!!!! Robert The only thing I'd suggest is to make sure you're at the latest SMS update level which I believe is still TSA5UP19. There have been a bunch of fixes in the last couple of releases. 19 is newer than the modules in SP5. Hope that helps, Andrew Ferris Network Support Analyst iCAPTURE Research Centre University of British Columbia >>> [EMAIL PROTECTED] 5/9/2006 7:22:04 am >>> Unfortunately, it doesn't appear that my suggestion applies to you. EV1: is an NSS volume, and already has the LONG namespace loaded on it. In the old days on Traditional Volumes, it didn't always default to that. Might be worth opening a ticket with novell for that one. >>> [EMAIL PROTECTED] 5/9/2006 9:05 AM >>> Hi Troy Here what I got running VOLUMES in the Netware server: 3 local FAT volumes mounted Mounted Volumes Name Spaces Flags SYS DOS, MAC, NFS, LONG NSS _ADMIN DOS, MAC, NFS, LONG NSS P VOL1 DOS, MAC, NFS, LONG NSS EV2 DOS, MAC, NFS, LONG NSS EV1 DOS, MAC, NFS, LONG NSS 5 volumes mounted Can you explain a little beat more about "load long" ????? It is a novell command ???? And how to add name space long to EV1: ???? Can you send me an example !!!!! Thanks in advance ..... Robert -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Frank Sent: Tuesday, May 09, 2006 4:45 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Novell question !!!!!! sys: & vol1: appear to be getting recognized as "long filename" filesystems under the "Type" column, while ev1: isn't. Is EV1: an nss volume, or traditional? In my case, I've got a couple servers attached to ibm ds4300's (fastt600), where sys: is local, and vol1: is on the san. When I do a "q files", both sys: and vol1: are listed as type "NTW:LONG" even though vol1: isn't a local volume. If it turns out that the EV1: volume just never got the "Long" namespace added to it, you can do a "load long", then "add name space long to ev1:". If EV1: is an nss volume, I'm not quite sure what happened.....they're supposed to have the LONG namespace added by default. >>> [EMAIL PROTECTED] 5/9/2006 7:42 AM >>> Hi to all I have a Netware server with sys: and vol1: local volumes and mounted a disk on a clariion storage EV1: Here the output of the command Q FILES tsm> q files # Last Incr Date Type File Space Name --- -------------- ---- --------------- 1 00/00/0000 00:00:00 NTWFS NWCC-CL2\EV1: 2 05/06/2006 22:00:04 NovellSMS NWCC-CL2\SERVER SPECIFIC INFO 3 05/06/2006 22:34:38 NTW:LONG NWCC-CL2\SYS: 4 05/02/2006 22:34:04 NTW:LONG NWCC-CL2\VOL1: Few questions, I did an online backup of EV1: without any problems , I connect the client via internet http://xxx.xx.xx.xx:1581 and saw the directories and files on the restore panel, my first question is why when I load the backup I see just the local volumes sys: and vol1: (I have in my dsm.opt the line DOMAIN all-local EV1:) and after changes I unload and load dsmcad ...... My second question is why in the restore panel I see directories with long names (+8) in dos format xxxxxx~1. My tsm client version is 5.3.012 and my Netware server version is 6.5 Any help will be appreciate ............. Regards Robert Ouzen Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you. Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you. Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.