ADSM-L

Novell issues during upgrade from 3.1 to 4.1

2001-05-14 09:20:13
Subject: Novell issues during upgrade from 3.1 to 4.1
From: Alan Davenport <alan.davenport AT SELECTIVE DOT COM>
Date: Mon, 14 May 2001 09:17:02 -0400
When upgrading from ADSM 3.1.2.50 to 4.1.0 on MVS/390, we've encountered
the following errors on some Novell clients going from short to long
file names:

FS011/vol001 - did not convert to long name in TSM database, error
ANS0327E
"a duplicate object was found, operation can not complete".

Date/Time
Message
--------------------
----------------------------------------------------------
----------------------------------------------------------
05/13/2001 11:15:23      ANR9999D SMINV(2002): Duplicate object
05/13/2001 11:15:23      ANR9999D SMINV(2002): Duplicate object
encountered during
                          import or rename.

Upon searching the archives, I found the following solution below. My
question is "Will renaming the exisiting filespace cause ALL of the
files in the filespace (FS011\VOL001) to back up during the next
incremental?"  I believe it will, I just need to be sure.

Also, can anyone offer any other solutions to this problem?

  Al

= Marc,

= There seems to be an upgrade problem to long file name space with the
3.7.x servers and up.
= Work around: Rename the old filespacename.


= Marc David wrote:

 > Ever since I've upgraded from ADSM 3.1.07  for Novell. I'm now
running the
 > latest client  TSM 4.1.2.
 >
 > I have volume that were converted to LONGFILE names. And some that
didn't
 > the new client was to be the fix.
 >
 > But  the backup still dies very quick with errors.  When i do a q
files in
 > DSMC the volume still has NTWFS  for file space name.
 >
 > Activity Log
 > ------------
 > Date and Time       Message
 >
------------------------------------------------------------------------------------------------------------------
 > 12/20/2000 13:38:15 ANR9999D sminv.c(2005): Duplicate object
 > 12/20/2000 13:38:15 ANR9999D sminv.c(2005): Duplicate object
encountered
 > during import or rename.
 > 12/20/2000 13:38:17 ANR0403I Session 3810 ended for node SSTARFLE
 > (NetWare).
 > 12/20/2000 13:38:19 ANE4952I (Session: 3809, Node: SSTARFLE)  Total
number
 > of objects inspected:      228
 > 12/20/2000 13:38:19 ANE4954I (Session: 3809, Node: SSTARFLE)  Total
number
 > of objects backed up:        0
 > 12/20/2000 13:38:19 ANE4958I (Session: 3809, Node: SSTARFLE)  Total
number
 > of objects updated:          0
 > 12/20/2000 13:38:19 ANE4960I (Session: 3809, Node: SSTARFLE)  Total
number
 > of objects rebound:          0
 > 12/20/2000 13:38:19 ANE4957I (Session: 3809, Node: SSTARFLE)  Total
number
 > of objects deleted:          0
 > 12/20/2000 13:38:19 ANE4970I (Session: 3809, Node: SSTARFLE)  Total
number
 > of objects expired:          0
 > 12/20/2000 13:38:19 ANE4959I (Session: 3809, Node: SSTARFLE)  Total
number
 > of objects failed:           0
 > 12/20/2000 13:38:19 ANE4961I (Session: 3809, Node: SSTARFLE)  Total
number
 > of bytes transferred:      116 Bytes
 > 12/20/2000 13:38:19 ANE4963I (Session: 3809, Node: SSTARFLE)  Data
transfer
 > time:                    0.00 sec
 > 12/20/2000 13:38:19 ANE4966I (Session: 3809, Node: SSTARFLE)  Network
data
 > transfer rate:            0.00 KB/sec
 > 12/20/2000 13:38:19 ANE4967I (Session: 3809, Node: SSTARFLE)
Aggregate
 > data transfer rate:          0.01 KB/sec
 > 12/20/2000 13:38:19 ANE4968I (Session: 3809, Node: SSTARFLE)  Objects
 > compressed by:                    0%
 > 12/20/2000 13:38:19 ANE4964I (Session: 3809, Node: SSTARFLE)  Elapsed
 > processing time:            00:00:07
 >
 > Has anyone run into this same problem,  I have MEMORYEFFICIENTBACKUP
NO
 > to convert to longfile names but.
 > It still never does.



--
Alan Davenport
Alan Davenport
Senior Storage Administrator
Selective Insurance
Alan.Davenport AT selective DOT com
973-948-1306

Disclaimer: All corporate mail is for official use only.
<Prev in Thread] Current Thread [Next in Thread>
  • Novell issues during upgrade from 3.1 to 4.1, Alan Davenport <=