![]() |
![]() |
If you have file names longer than the DOS name space permits, you can specify that Tivoli Storage Manager stores the long names during backup. Long names with spaces must be enclosed in double quotes.
Tivoli Storage Manager Client Version 5.1.0 does not perform a conversion from a long to a short name space. If the Tivoli Storage Manager server name space is NTW:LONG but the local volume does not have long name support, Tivoli Storage Manager Client Version 5.1.0 issues an error message and ceases any backup or archive operation.
If you want to continue backing up using long names, add the long name space support back to the volume in question. You can also use a short name to back up the volume by renaming the file space on the server before attempting a back up.
Tivoli Storage Manager does not support Macintosh name space. If a NetWare volume has only DOS and Mac name spaces, Tivoli Storage Manager uses the DOS name for Macintosh file names. If you use only DOS and Mac names spaces on a NetWare volume, you should add Long name space to that volume. This will ensure that NetWare converts Macintosh file names to the Long name before the file is backed up.
The Macintosh namespace information is not lost when backing up or restoring a Macintosh file. The only issue is how the client will display the name when performing a query, restore, or retrieve operation.
Using the Long name space allows greater flexibility for backing up files whose names are longer than traditional DOS names.
To determine the name spaces that are loaded on a volume, enter volumes at the NetWare console, for example: PROD1:volumes. Information displays which is similar to the following:
+--------------------------------------------------------------------------------+ |Mounted Volumes Name Spaces Flags | | SYS DOS, LONG Cp Sa | | VOL1 DOS, MAC, LONG Cp SA | |PROD1: | +--------------------------------------------------------------------------------+
In this example, server PROD1 has 2 volumes. The SYS volume has DOS and long name spaces. VOL1 has DOS, Mac and long name spaces. The Tivoli Storage Manager client inspects these settings when it begins an operation, such as backup. The client then determines the name space used by the backed up volume. For example:
+--------------------------------------------------------------------------------+ |tsm> q file | |Node Name: VONORE | |Session established with server TSM: Windows NT | | Server Version 5, Release 1, Level 0 | | Server date/time: 02/05/1999 05:59:45 Last access: 02/04/1999 18:34:09 | | | |Num Last incr Date Type File Space Name | |--- ---------------- ---- --------------- | | 1 02/04/1999 18:34:46 NTWFS PROD1\VOL1: | |tsm> | | | +--------------------------------------------------------------------------------+
VOL1 was last backed up with the file space type of NTWFS or DOS name space. When Tivoli Storage Manager starts a full incremental of VOL1, it detects that VOL1 has both Mac and long name spaces, but that the data is backed up using the DOS name space. This causes the file space to be updated to the long name space. Even though both Mac and long are loaded, Tivoli Storage Manager chooses the long name space because the Mac name space is not supported.
After a full incremental backup, the following change displays:
+--------------------------------------------------------------------------------+ |tsm> q file | |Node Name: VONORE | |Session established with server TSM: Windows NT | | Server Version 5, Release 1, Level 0 | | Server date/time: 10/05/2000 05:59:45 Last access: 10/01/2000 20:34:09 | | | |Num Last incr Date Type File Space Name | |--- ---------------- ---- --------------- | | 1 10/01/2000 18:34:46 NTW:LONG PROD1\VOL1: | |tsm> | | | +--------------------------------------------------------------------------------+
The file space type changes from NTWFS to NTW:LONG. The client uses the long name space during the next full incremental backup. The file space is converted to use the long name space. All active and inactive files are changed to the following:
+--------------------------------------------------------------------------------+ |tsm< Q BACKUP VOL1:* -SUB=YES | |Size Backup Date Mgmt Class A/I File | |---- ----------- ---------- --- ---- | | 0 02/05/1999 06:33:28 STANDARD A VOL1:/ | | 0 02/05/1999 06:29:49 STANDARD A VOL1:/DELETED.SAV | | 0 02/05/1999 06:29:49 STANDARD A VOL1:/Frank Ramke | |1,175 02/05/1999 06:29:49 DEFAULT A VOL1:/VOL$LOG.ERR | | 0 02/05/1999 06:29:49 STANDARD A VOL1:/Frank Ramke/Debbie Ramke | | 0 02/05/1999 06:29:49 STANDARD A VOL1:/Frank Ramke/Debbie Ramke/ | | Krista Breeden | | 0 02/05/1999 06:29:49 STANDARD A VOL1:/Frank Ramke/Debbie Ramke/ | | Shane Breeden | | 11 02/05/1999 06:29:49 DEFAULT A VOL1:/Frank Ramke/1 Long File | | 11 02/05/1999 06:29:49 DEFAULT A VOL1:/Frank Ramke/2 Long File | | 11 02/05/1999 06:29:49 DEFAULT A VOL1:/Frank Ramke/Debbie Ramke/1 | | Long File | | 11 02/05/1999 06:29:49 DEFAULT A VOL1:/Frank Ramke/Debbie Ramke/2 | | Long File | | 11 02/03/1999 06:29:49 DEFAULT I VOL1:/FRANK RAMKE/DEBBIE RAMKE/2 | | LONG FILE | |tsm< | +--------------------------------------------------------------------------------+
The last file in the list is an inactive file and is not cased properly because of the way case is preserved by the client. This migration cannot case inactive files correctly.
During a full incremental, objects are updated. This is when renaming occurs. For example,
+--------------------------------------------------------------------------------+ |... | |Updating--> 0 VOL1:/TOMRAMK0/DEBBIERA/SHANEBRE [Sent] | |Updating--> 11 VOL1:/TOMRAMK0/DEBBIERA/1LONGFIL [Sent] | |Updating--> 11 VOL1:/TOMRAMK0/DEBBIERA/2LONGFI0 [Sent] | |Updating--> 11 VOL1:/VONORE/1LONGFIL [Sent] | |Updating--> 11 VOL1:/VONORETE/1LONGFIL [Sent] | |Successful incremental backup of 'VOL1:' | | | +--------------------------------------------------------------------------------+
To convert from a short to a long name space, you must perform a full incremental on your file space. You can perform the conversion using either the Web client or the command line.
To use the Web client, click on the volume name, and select Incremental (complete) from the pull down menu at the top of the screen. To perform a full incremental on your file space from the command line, enter dsmc i sys:.
After converting the file space, the client backs up or archives subsequent files to a long name space.
If the Long Name conversion has started you must let it run to completion. If the conversion from a short name space to a long name space is interrupted and then restarted, you must use a 4.2.1 or higher Tivoli Storage Manager server. You may receive an error message if conversion is attempted with a lower level server.
If you run a selective backup or archive before conversion, Tivoli Storage Manager uses the current name space for the backup; that is, the name space indicated from the query filespace command.
You must change your Include-exclude statements to reflect the long names. Until conversion is complete, consider entering both long and short names. Long names with spaces must be enclosed in double quotes. For example:
exclude vol1:\frankra0/.../* exclude "vol1:\frank ramke/.../*"
If files have been backed up from a volume with long name space loaded, and you attempt to restore them to a volume without long name space, the restore will fail. A message similar to the following displays:
02/12/1999 09:24:30 (TSA400 4.14 287) The name space type does not exist or is invalid.
Use quotes to enclose a long name string that has embedded blanks.
If files are not being converted, the reason could be any of the following:
You can use the NetWare Volume Repair Utility, vrepair.nlm, to remove a name space. For more information, refer to the README file that is shipped on the product installation media.