Library Table of Contents  Previous Next Comments

Possible upgrade issues

Pre-Data ONTAP 5.3 compatibility issues

Forcing Unicode conversion  Top

Unicode support was introduced in Data ONTAP 5.3. When existing directories and the files that they contain are accessed from Windows clients, their names are converted to Unicode. Unicode conversion can take a significant amount of time, and while conversion is in progress, error messages might be returned when users attempt to delete files.

To force Unicode conversion, complete the following steps.

Step

Action

1

At a Windows workstation, use Network Neighborhood to locate the filer.

2

Open a share.

3

Right-click each top-level folder, then select Properties from the menu.

4

Wait for the folder size calculation to finish.

Result

The directory and file names for everything contained in the folder are converted to Unicode.

5

Repeat Step 2 through Step 4 for each additional share on the filer.

Only SCSI-2 compliant tape media changers supported  Top

Starting with Data ONTAP 5.3, the filer only supports tape media changers that are SCSI-2 compliant. If you plan to upgrade from a pre-5.3 release, make sure that any tape media changers attached to your filer are SCSI-2 compliant. A noncompliant media changer prevents the filer from booting.

Pre-5.3 snapshot access lost from CIFS  Top

Upgrading from a pre-5.3 release to Data ONTAP 5.3 or later results in a loss of CIFS access to any snapshots that you previously made.

Default SPANS device name changed  Top

Data ONTAP 5.3 included an updated version of Simple Protocol for ATM Network Signaling (SPANS). SPANS now uses the default device name fa0; previous releases used the default device name a0. If your filer is running a pre-5.3 version, before you follow the upgrade procedure, edit the filer /etc/rc file to reflect the ATM interface name change. Otherwise, the ATM interface does not come up after the software upgrade.

Library Table of Contents  Previous Next Comments