NT V3 PTF 5 warning

Hello,

In light of the recent discussion on the list,  we in ADSM development realize
that  there's some level of anxiety over the Universal
Naming Convention support introduced in the Win32 v3.1.0.5 client.  Let me
explain the motivation for introducing this support.  In
preparation for the changes introduced by the forthcoming NT 5.0 release, we
believe a phased introduction of support for UNC is a
needed step.This support gives users the ability to backup/restore un-mapped
drives and to back up drives without a volume label.
One effect of this support was the necessity to change ADSMs filespace naming
convention.  We have provided documention of the
change in the readme files, but perhaps that information is easily overlooked.
I've included a section here from the
IP21371.readme.1st and baclient.txt.  We apologize for any confusion, but hope
that you will find the enhanced function useful in your
environment.

From the IP21371.readme.1st:

***************************************************************************
1. Before You Install Your ADSM Client                                    *
***************************************************************************
  Warnings
  ========

    *************  Existing filespace names will be migrated from volume
    * IMPORTANT *  label names to Universal Naming Convention (UNC) names.
    *************  While the migration is transparent, it will affect the
    way filespace names are specified, especially from the command line
    Backup-Archive client. It is IMPORTANT that you review the specifics of
    this change in the BACLIENT.TXT file before installing and/or using this
    level of the client for the first time.

From the baclient.txt:

SUPPORT FOR UNIVERSAL NAMING CONVENTION (UNC)
---------------------------------------------
1) You can specify Universal Naming Convention (UNC) names for backup/r1) You 
can specify Universal Naming Convention (UNC) names for backup/restore
   operations.

2) You can backup and restore share information on remote UNC names (shares
   are always considered to be remote even if they alias a local resource).
   Share information includes, among other things, directory aliases and
   share level security. This information is already backed up because it is
   stored in the registry. However, backing data on a per UNC (share) basis
   allows a more granular interface. This enhancement is currently supported
   for the Windows NT client.

3) Include/Exclude and domain list option processing will also be UNC
   enabled.

Note: the GUI client will continue to require that remote shares be mapped to
      a drive letter for backup/archive.

A UNC name is a network resource name for a share point on a machine
consisting of a string in a form of:

  \\<machine>\<share point name>

Every local drive letter is accessible by specifying a local UNC Name in the
form of:

  \\<machine>\<x$> where x is the particular local drive letter.


FILESPACE NAME MIGRATION
------------------------
The filespace naming scheme:
The filespace naming scheme:

   - The filespace name for local, fixed logical partitions (drives) will be
     the default UNC name as described above.

   - The filespace name for all remote share points (regardless of whether
     mapped to a drive letter) will be the UNC sharename.

   - The filespace name for all local, removable media partitions will
     continue to be the volume label.

Rules for migrating existing filespaces:

1) If the current volume label matches the filespace name on the server and
   the drive letter is the same as the one stored on the server, and the new
   filespace doesn't exist, any existing filespaces created with the volume
   label will be renamed to the new naming convention the first time they are
   accessed for backup/archive.

   Message 1053 will be logged in the error log:

   ANS1053I Existing filespace name <old_name> has been renamed
            to <new_name>

2) If the current volume label matches the filespace name on the server but
   the drive letters do not match, any existing filespaces created with the
   volume label are ignored.

   Message 1055 will be logged in the error log:

   ANS1055I Trying to rename existing filespace <old_name> to new filespace
            <new_name>,
            but drive letters do not match, old=<old_drive>, new=<new_drive>.
            Ignore the old filespace and backup to the new filespace.

3) If the current volume label matches the filespace name on the server but
   the new filespace exists, any existing filespaces created with the volume
   label are ignored.

   Message 1057 will be logged in the error log:

   ANS1057I Trying to rename existing filespace <old_name> to new filespace
            <new_name>,
            but both filespaces exist.  Ignore the old filespace and backup to
            the new filespace.


WARNINGS
--------
1) When using the 3.1.0.3 or prior levels of the client to restore data1) When 
using the 3.1.0.3 or prior levels of the client to restore data that
   were backed up using 3.1.0.5 client, you must explicitly specify the
   filespace name, which is the UNC name.

   Example:  dsmc i c:\*                     (filespace name is \\buzzcut\c$)
             dsmc res {"\\buzzcut\c$"}\* -subdir=y

2) When using the 3.1.0.5 client to restore data that were backed up using
   3.1.0.3 or prior levels of the clients, you must explicitly specify the
   filespace name, which is the volume label to restore the data. You don't
   need to explicitly specify the filespace name if it has been migrated to
   the new filespace naming convention as described in the "FILESPACE NAME
   MIGRATION" section (above).

   Example:  dsmc i c:\*              (filespace name is volume label C-DISK)
             dsmc res {"C-DISK"}\* -subdir=y
             dsmc res {"C-DISK"}\* -subdir=y

Regards,

Joanne Nguyen
ADSM Client Development