ADSM-L

Unicode-Enabled file spaces

2003-06-18 14:27:10
Subject: Unicode-Enabled file spaces
From: Shannon Bach <SBach AT MGE DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 18 Jun 2003 13:27:41 -0500
Ran into a problem this morning when a NT 4 client that recently upgraded
from 4.1.3 to 5.1.6 needed to have his filespaces unicode-enabled.  Since
the upgrade, the Mac servers that use this NT dbserver client have not been
able to read from the images volume.   I updated the node to AUTOFSRENAME
YES, and the client put AUTOFSRENAME YES in his dsm.opt.  I started his
incremental schedule early and now everything looks like it is working
fine.  The testfile1_c$ was renamed to testfile1_c$_OLD and the new unicode
filespace=yes is now created.  It hasn't reached the other volume yet.  My
question is;

When this backup-up gets done and I have 2 sets of each filespace does the
client keep the AUTOFSRENAME YES in the dsm.opt?  And do I update the node
back to AUTOFSRENAME NO or just leave it.  I cannot find this part of it in
the Administrator's Guide or the Windows Backup-Archive Clients
Installation and Users Guide.

As always, thanks very much for any response.
Shannon Bach
Madison Gas & Electric Co.
Operations Analyst - Data Center Services
e-mail sbach AT mge DOT com

<Prev in Thread] Current Thread [Next in Thread>
  • Unicode-Enabled file spaces, Shannon Bach <=