4.4rel-notes

Data Domain Confidential - 1 - Data Domain System Release Notes

Data Domain®

Software Release 4.4.4.0-66005Release Notes

April 7, 2008Part Number: 765-0404-0400 Rev. A

Fixed in this Release

9538 Fixed illegal request response.

15322 Gateway restorer timeout increased to 60 seconds when it loses access to its disks.

15323 System now reports correct LUN number and size for LUNs > 255.

15385 Added a "Cleanable" field to GUI and filesys show space command.

15390 Access for CIFS users via ftp/telnet/ssh is granted only to administrative users.

15953 Messages were added to inform users who have added more memory that thefilesystem may take a long time to come up, and giving an estimate of the time it will take.

16212 Fixed race condition in file handle index.

16613 Fixed problem by increasing the number of files in /ddr/var to 2048.

16809 Fixed problem reading Autosupport file.

17000 The idmap configuration from previous releases has now been fixed and no longerneeds to be done. (17270)

17270 Authentication problems for CIFS users accessing the Data Domain system afterupgrading to DDOS 4.4.2/4.4.3 have now been fixed.

17287 A problem necessitating refraining from doing a vtl group rename was fixed forrelease 4.4.3.1. That is, with release 4.4.3.1, it is okay to do a vtl group rename.

17327 The VTL GUI now works whether or not adminaccess http is disabled.

17471 Daylight Saving Time will now change correctly in Canada, Australia, and NewZealand, and in fact everywhere (until the rules change again).

17591 The file /ddr/var/log/snmpd.log is now included in support bundles.

17879 SCSI disk timeout was increased to 60 seconds.


Command Changes in this Release

filesys show history has been replaced by the command filesys showcompression daily.

Power Supply Unit Failure

Important: if a PSU (Power Supply Unit) fails in either the head unit or an expansion shelf,don't remove the failed PSU from the system until you are ready to swap it, as this couldperturb airflow and cause temperature to rise unacceptably. (While the PSU should bereplaced as soon as is practical, operation can continue indefinitely without a significantrise in temperature as long as the PSU is not taken out.) (14776)

New Features in Release 4.4.2.0

The main feature added in this release is DD530 and DD510 Storage Expansion. This isoptional factory-installed licensed storage expansion for the DD530 and DD510.

The following table shows the usable amount of space for each configuration in TeraBytes:

Factory Field UpgradeUsableTB 9 Drives

1 Raid Group15 Drives

1 Raid Group15 Drives

2 Raid GroupsDD510 1.27 2.73 2.11DD530 2.75 5.69 4.51

DD120. Entry level Data Domain System for remote offices.

DD530 and DD510 Storage Expansion. Optional field upgrade licensed storageexpansion for the DD530 and DD510.

VTL GUI. A new VTL (Virtual Tape Library) GUI (Graphical User Interface)provides much greater ease of use when manipulating Virtual Tape Libraries.Functionality is grouped into Libraries, LUN (Logical Unit Number) Groups,Physical Resources, and Pools.

Note: When using the VTL GUI, changes made through the CLI need to beupdated using the Refresh button (the icon for this button is two arrows circlingeach other).


VTL auto-offline. The new VTL auto-offline commands allow you to set virtual tapesto automatically go offline when a tape move operation is generated. Some backupsoftware and diagnostic tools sometimes do not move a tape offline before moving atape out of a drive, which can cause the move operation to hang. (11602) (14782)(14783) The commands are:

vtl option enable auto-offline Always offline a tape when a moveoperation is generated.

vtl option disable auto-offline Do not automatically offline a tapewhen a move operation is generated.

vtl option show auto-offline Display the current auto-offline setting.

Multi-port VTL: Support for a dual port 4Gb FC target mode HBA in the DD510,DD530, DD565, DD580 and DD580g. Optional support for up to two, dual port 4Gb FCHBAs for the DD565, DD580, and DD580g. VTL changer and tape drives access ispossible on any of the FC ports.

VTL port failover. Provides the ability to manually failover from one FC VTL port toanother. Failover can be from one port to another on the same HBA or between portson different HBAs if there are 2 HBAs.

Multi-initiator Host VTL access. An Access Group or LUN Group can be defined,whereby multiple initiators and multiple VTL devices form a group, all the membersof which have access to each other.

2 port Ethernet link aggregation / trunking. Provides the ability to aggregate multipleEthernet interfaces in parallel to increase link speed and to increase redundancy forhigher availability.

Optional second dual ported copper or optical NIC for the DD565, DD580 and DD580g

OpenStorage (OST) - Symantec NetBackUp OpenStorage Software. An optionallicensable capability that allows a Data Domain system to be a storage server forSymantec’s NetBackup OpenStorage feature. (NetBackup docs are available on theweb at http://entsupport.symantec.com.)

Note: Following a ‘filesys destroy’, the following two commands must beexecuted before the Data Domain system is available as an OST storage unit.$ ost disable$ ost enable

OST client plugin documentation is found on the Data Domain support website under thesoftware downloads link https://support.datadomain.com/downloads.php, at the bottom ofthe page, at the Download link. Be sure to see the readme file in this ost download, whichcontains quick start information. OST server-side documentation is found in the OpenStorage chapter of the Data Domain Operating System User Guide.

http://entsupport.symantec.com/

https://support.datadomain.com/downloads.php


Gateway Multipath. Multiple I/O paths to external storage allow external storage I/Opaths for failover and load balancing across paths. Multipath is supported on allgateway models. See Gateway Support matrix for the arrays with multipathcapability. Up to 2 dual ported 4Gb HBAs are now optionally supported in theDD580g

Starting with release 4.4, when creating a share in CIFS, group names must have the“@” symbol before them.

Log Messages: The log file "message" now has message IDs. A detailed descriptionof log messages can be obtained from the Data Domain Support websitehttps://support.datadomain.com/, by clicking Software Downloads, then the bookicon under Docs for the given release, then Error Message Catalog. (This will go tohttps://support.datadomain.com/doc/4.4/61511/pdf/ErrorMessageCatalog.xml, or apage like it.) See also the section: "Procedure: Understand Log Message" in the LogFile Management chapter of the User Guide.

Command Changes in Release 4.4.2.0

Deleted Commands:enclosure show portsfilesys clean update-statsfilesys show history yyyy/mmreplication show compression obj-spec-listreplication sync start [destination]replication sync status [destination]vtl initiator addvtl initiator del initiator-namevtl lunmask add vtl-name {all\changer\drive drive-name} nameinitiator [lun lun-number]vtl lunmask del vtl-name {all\changer\drive drive-name} nameinitiatorvtl option reset loop-id valuevtl tape eject vtl-name drive drivevtl tape insert vtl-name drive drive barcode barcode [pool pool-name]vtl tape show {all|option-name}

Added Commands:disk Displays disk statistics, status, configuration and use.expand Expand storage capacity on a DD510 or DD530.multipath disable Disable multi-path configuration.multipath enable Enable multi-path configuration.multipath reset stats Clear statistics for all paths of all disks.multipath show history Display the multi-path events history.multipath show stats [enclosure enclosure-id] Display statistics for all paths of all

disks.multipath status [port-id] Display multi-path configurations and run time status.port show {stats|summary} Display disk port information.

filesys Displays file system status and statistics.

https://support.datadomain.com/doc/4.4/61511/pdf/ErrorMessageCatalog.xml


net Set and show RPM network parameters and status.aggregate add vifname mode {roundrobin|xor-L2|xor-L3L4} interfacesinterfaces Add network interfaces to an aggregate interface.

aggregate del vifname interfaces interfaces Remove network interfaces from anaggregate interface.

aggregate reset Reset an aggregate interface by removing all associated physical interfaces. Saggregate show Display all aggregate interfaces.

ost Use a Data Domain system as a storage server for the NetBackup Open Storage feature.destroy Remove all images and LSUs on the Data Domain system.disable Disable storage server capabilities on the Data Domain system.enable Allow storage server capabilities on the Data Domain system.lsu create lsu-name Create a logical storage unit.lsu delete lsu-name Remove all images in a logical storage unit.lsu show [compression] [lsu-name] Display all LSUs, images in an LSU, or images sizes

before and after compression.reset stats Clear all OST statistics.reset user-name name Reset the OST user to the default of no user.set user-name Give a user name for use by OST.show connections Display the maximum number of allowed connections.show histogram Display OST/NFS latencies for performance analysis.show image-duplication active Display the status of active file copy operations.show stats [interval seconds] Display OST statistics since the last OST enable

operation.show user-name Display the current OST user name.status Display the current OST status, enabled or disabled.

user Administer user accounts.change password [user] Change a user password.

vtl Manage the virtual tape library feature.drive add vtl-name [count num-drives][model model] Add drives to a VTL.drive del vtl-name drive drive-number [count num-drives] Delete drives

from a VTL.group add grp-name {initiator init-name|WWPN} Add an initiator to a group.group add grp-name vtl vtl-name {all|changer|drive drive-list} [lunlun] [port {all|none|port-list}] [secondary-port {all|none|port-list}]Add a device to a group.

group create grp-name Create a group.group destroy grp-name Remove a group.group del grp-name {initiator init-name|WWPN} Remove an initiator from a group.group del grp-name vtl vtl-name {all|changer|drive drive-list} Remove a

device from a group.group modify grp-name vtl vtl-name {all|changer|drive drive-list}

[lun lun] [port {all|none|port-list}] [secondary-port {all|none|port-list}] Modify a device in a group.

group rename src-grp-name dest-grp-name Rename a group.group show {all|vtl vtl-name|grp-name} Display configured groups.group use grp-name [vtl vtl-name {all|changer|drive drive-list}]

{primary|secondary} Switch the port for a group or library to the primary or secondary portlist.

option disable {loop-id|auto-eject} Disable an option.option enable {loop-id|auto-eject} Enable an option.option reset auto-eject Reset the auto-eject feature to the default of disabled.option reset loop-id Reset the hard address to the default of 1 (one).


option set auto-eject {enabled|disabled} Enable or disable automatically moving atape from a cartridge access port to the virtual vault..

port disable {all|port-list} Disable one or more Fibre Channel ports.port enable {all|port-list} Enable one or more Fibre Channel ports.port show detailed-stats Display Fibre Channel detailed statistics.port show hardware Display Fibre Channel hardware.port show stats [interval seconds][count count] Display VTL I/O statistics on

Fibre Channel ports.port show summary Display a Fibre Channel summary.reset hba Issue a reset to the HBA.

Changed Commands:filesys show compression [path] [last {n hrs | n days}] [no-sync] The[no-sync] option was added to allow running the command without synchronization.filesys show performance {obj-spec-list|all} [interval second] [countcount] Interval was specified as seconds, and count was added.migration send {obj-spec-list|all} destination-host hostname Theall option was added.net config interface [ipaddr][netmask mask][up|down][mtu {size|default}] [dhcp {yes|no}][duplex {full|half} speed{10|100|1000}][autoneg] The default size option was added.replication show performance {obj-spec-list|all} [interval second][count count] Interval was specified as seconds, and count was added.system show {detailed-version|hardware|modelno|ports|serialno|uptime |version} Portsoption was added.VTL - add it to all the followintg:add vtl-name [model model] [slots num-slots][caps num-caps] Capsadded.export vtl-name {slot|drive|cap} address [count count] Drive|cap}address added.import vtl-name barcode barcode [count count] [pool pool-name][element {drive|cap|slot}] [address addr] The following: [element{drive|cap|slot}] [address addr] ...was added.initiator set alias init-name wwpn wwpn Set alias init wasadded.lunmask show [vtl vtl-name|group group-name] "vtl-name|groupgroup-name" was added.tape move vtl-name source {slot|drive|cap} src-address destination{slot|drive|cap} dest-address This command changed in ways toonumerous to list.tape show {all|pool name|vault|vtl-name} [summary] [count count][barcode barcode] [sort-by {barcode|modtime|capacity|usage|percentfull}[{ascending|descending}]] Added the latter part ofthe command: "[summary] [count count] [barcode barcode] [sort-by{barcode|modtime|capacity|usage|percentfull}[{ascending|descending}]]".


Fixed in Release 4.4.2.0

6148 Message: "CRITICAL resent container 1252016 container is still bad." reduced to awarning message.

6666 The default router was getting reset.

9366 Improved replication efficiency when using directory replication with VTL.

10114 SNMP traps were fixed so that they return valid responses.

10696 Fixed issue that power-cycling a shelf during load could cause corruption.

12796 If error in lrepl_open_file_2_svc(), we now return err instead of panic.

13005 A user logged in to root/bash using putty/ssh. After changing the sysadminpassword, the root login was available. The root login is now always disabled.

13580 Resolved false reporting of power supply failures in a DD565, DD510, DD530.

13884 Couldn't add LUN, was unable to format disk.

14086 TSM version 5.3 and later uses a different tape marker pattern than earlier TSMversions. The Data Domain system command filesys option set marker-typenow recognizes the new pattern with both the tsm1 and tsm2 options.

14175 Setting the tape marker nw1 now works for Legato 7.3.2 on SUSE using VTL.

14349 Resolved panic on collection replica due to no index space.

14390 If the Data Domain system's CIFS registry entries for smbd-mem-limit and winbindd-mem-limit were set to non-default values, an upgrade to release 4.3.2.0 changed the values.The values are now maintained during an upgrade.

14419 Fixed an upgrade issue when the customer used the default group for his VTLdevices.

14450 Improved prevention and error messaging when attempt is made to rename .snapshot.

14507 Gateway now defaults to Serial Number as the sysadmin password.

14579 Resolved out of memory issue that caused DDFS to be killed.

14644 Cron daemon now getting correct time and time zone after software upgrade.

14667 Resolved issue that VTL import was overfilling a library.

14688 Resolved issue that cleaning was taking a long time after upgrade.


14727 Resolved issue that DDFS process could fail when memory was low on the indexmerge buffer.

14751 Resolved issue that sfs_verify was missing segments while verifying/backup/vtc/Default.

14800 Having too many open NFS streams no longer triggers unnecessary alerts.

14835 Resolved issue that VTL/TSM backups could fail stating that volumes are full whenTSM shows 49%.

14976 Replication lag after upgrade.

14993 System booted to kdb because of corrupt NVRAM.

15106 Problem adding LUNs was fixed.

15167 Drives 1.1 and 1.2 failed after replacing with new drives.

15209 Filesys destroy and-zero was timing out when issued on DD580 systems.

15433 System rebooted and created a crashdump--fixed.

15617 False power supply alarm.

15918 Improved upgrade error handling.

Supported BrowsersThe GUI for DD OS 4.4.3.0 runs on the following browsers: Internet Explorer 6+ Firefox 2+

Supported SystemsDD OS 4.4.3.0 runs on the following Data Domain systems: Appliance series: DD580, DD565, DD560, DD460, DD530, DD430, DD510, DD410,

DD120 Gateway series: DD580g, DD560g, DD460g DDX Array series: DD580, DD565, DD560, DD460, DD580g, DD560g, DD460g

controllers


Expansion Shelves

A DD OS upgrade to release 4.4.3.0 from a release earlier than 4.1.3.0 on a Data DomainSystem that has one or two expansion shelves requires a firmware upgrade for the SAS HBAcard in the Data Domain System and for each expansion shelf. The upgrades require ashutdown of the controlling Data Domain System and should be done after upgrading theData Domain System to version 4.4.3.0. Contact your Data Domain field representative toperform the HBA and expansion shelf upgrades.

DD120

Note: The following happens only on the DD120: When one fan is defective, the system mayincorrectly report that all fans and power supplies have failed. The action is to replace thecomplete system.

Upgrade to 4.4.4.0An upgrade to 4.4.4.0 can be done only from systems using DD OS version 4.2.x.x orlater in the 4.x series.

To upgrade from a release earlier than 4.2, first upgrade to 4.0, then upgrade to 4.2, thenupgrade to 4.4. Upgrades can only be done from 4.x to 4.y when x and y are at most twomajor releases apart.

To upgrade from a 4.2 or later system, download the 4.4.4.0 image from the Data Domainsupport web page. After downloading the image, run the system upgrade command.The upgrade process takes a few minutes, depending on the amount of data on the DataDomain System. (If an upgrade fails, call customer support.)

For systems that are already part of a replication pair: With directory replication, upgrade the destination and then upgrade the source.

With collection replication, upgrade the source and then upgrade the destination.

With the exception of bi-directional directory replication, which requires the source anddestination to run the same release, directory replication is backwards compatible withone previous release family (all 4.3.x releases, for 4.4.4.0). After upgrading one side ofa bi-directional replication pair, replication to the other side stops until the other side isupgraded. Replication to the other side of the pair then automatically restarts.

Release 4.4.4.0 collection replication is not compatible with releases earlier than4.4.0.0. In theory, collection replication can be performed between any 4.4.4.x and any


other 4.4.4.x. However, the only tested and supported configurations are those wherethe source and destination are at the same version, i.e. both are 4.4.4.0, for example.

For an upgrade, do NOT disable replication on either system in the pair.

Use the filesys show space command on the source and the destination. If thevalue for the Data line in the Use% column is 2% or more larger on the destination thanon the source, replication or processing of filesys clean results is lagging.Assume that an upgrade on the destination will be slow.

The upgrade process generates a message every 30 seconds while the upgrade is makingprogress. However, the messages are seen only from a serial console. Use a serialconsole to verify that progress is continuous when doing an upgrade that you suspectwill be slow.

Note: If you plan to add a SAS HBA (Host Bus Adapter) for the new Expansion Shelffeature,upgrade to 4.4.4.0 before physically installing the SAS HBA. After the softwareupgrade,install the SAS HBA. (10324)

Note: The LUN masking functionality in 4.4 has been replaced with the concept ofGROUPS. The CLI command 'vtl lunmask' has been removed, 'vtl group' added and theusage of 'vtl initiator' changed. For more information please refer to the Data Domainrestorer user guide chapter on VTL.

If you had assigned all devices to initiators prior to upgrading to 4.4 your configuration willbe changed for you and no action will be required.

If ANY device is a member of "Default" (as shown by a 'vtl initiator show') prior to theupgrade those devices will not be accessible after the upgrade. If this occurs, simply createan access group and include those devices in the new access group.

Therefore, when upgrading from 4.3 to 4.4, the (VTL) user has a choice of two ways to go:

The first way (slightly easier):1. Assign all devices from the "Default" lunmask to named (non-Default)

lunmasks/initiators prior to upgrading to 4.4.2. Upgrade.

The other way:1. Make a list of all devices that are in the "Default" lunmask prior to the upgrade.2. Upgrade.3. Create an access group and include all devices that were previously in the "Default"

lunmask in this new access group.

To upgrade software to release 4.4.4.0:

1. [If you are a VTL user, assign all devices from the "Default" lunmask to named (non-Default) lunmasks/initiators prior to upgrading to 4.4.]


2. Make sure that the system is idle. All replication should be completed and nobackups should be running.

3. Point a browser to support.datadomain.com.

4. Log in with the login name and password that you use for access to the Data Domainsupport web page or the Data Domain FTP site.

5. Click on Downloads.

6. Click on Download for version 4.4.4.0-66005. Store the image on the DataDomain System in the directory /ddvar/releases.

Note: When downloading a Data Domain System software upgrade image using InternetExplorer, the browser may add bracket and numeric characters to the upgrade image name.Remove the added characters before running the system upgrade command. (3082)

7. For systems that are already part of a replication pair before the upgrade, do NOTdisable replication on either system in the pair. Upgrade the source (originator) after upgrading the destination (replica). (4939)

8. Stop (log out from) all Data Domain Enterprise Manager sessions on the Data DomainSystem.

9. Stop any active CIFS client connections before starting the upgrade. Use the cifsshow active command to check for CIFS activity. Disconnect any client that isactive. On the client, enter the command net use \\dd\backup /delete.

10. On the Data Domain System enter the following command:

system upgrade 4.4.4.0-66005.rpm

With collection replication, no files are visible on the destination if replication was notfinished before starting the upgrade. After the upgrade, wait until replication completes tosee files on the destination.

Compatibility MatricesFor specific backup software and hardware configurations tested and supported by DataDomain, see the compatibility matrices at the Support web site:

https://support.datadomain.com/compat_matrix.php

For file system data access, see DD500/DD400/DD100 Backup Software Compatibilityusing NFS/CIFS/NDMP.

For VTL data access, see DD500/DD400 Backup Software Compatibility using VTL.


For VTL access with Network Attached Storage (NAS) systems, see DD500/DD400Backup Software compatibility using VTL for Network Attached Storage Systems.

For gateway series Data Domain System model compatibility with 3rd party storage, seethe Gateway Support Matrix.

Documentation Errata for this ReleaseNote: Printed documents may not be current. Release notes contain the most currentinformation.

Added Commands:disk

multipath option set monitor {enabled|disabled} Enable or disablemulti-path monitoring.

multipath option reset monitor Reset multi-path monitoring.multipath option show Show multi-path options.

Deleted Commands:filesys

show history yyyy/mm Display the file system space history report.lunmask show [vtl vtl-name|group group-name] List configured LUN masks.

This command is deprecated. Use 'vtl group show' instead.

Changed Commands:None.

User Guide Network Management Chapter:

The “Data Domain Operating System User Guide” Network Management chapterincludes information about Ethernet failover and net aggregation. The information aboutwhich types of interfaces can work together with failover and aggregation needsclarification.

- Virtual interfaces must be made up of the same type of interfaces, such as all copper orall fiber.

- Virtual interfaces must be made up of the same speed interfaces, all 1 Gb.

- The interfaces on the motherboard can be used with optional NIC interfaces for failover,but not for aggregation.

- A system can have multiple and mixed failover and aggregation virtual interfaces.

The following table lists which type of interface (motherboard, optional NIC, copper,fiber, 1 Gb, or 10 Gb) can be used together for failover and for aggregation:


Interface types Failover Aggregation1 Gb 10 Gb Does not work Does not work1 Gb 1 Gb SUPPORTED SUPPORTEDcopper fiber Not supported Not supportedcopper copper SUPPORTED SUPPORTEDfiber fiber SUPPORTED SUPPORTEDmotherboard optional NIC SUPPORTED Not supportedNIC NIC SUPPORTED SUPPORTED

CIFS <client-list> and <user-names>:

A more correct version of the documentation for CIFS <client-list> and <user-names> is as follows (15785):

<client-list>The <client-list> for the "clients" option in the cifs share:The client list is a comma-separated list of clients that areallowed to access the share. Other than the comma delimiter,there should not be any whitespace (blank, tab) characters.

Some valid client lists are:"host1,host2""host1,10.24.160.116"

Some invalid client lists are:"host1 ""host1 ,host2""host1, 10.24.160.116""host1 10.24.160.116"

<user-names>The <user-names> list for the "users" option in the cifs share:The user names list is a comma-separated list of user names.Other than the comma delimiter, any whitespace (blank, tab)characters are treated as part of the user name, because aWindows user name can have a space character anywhere in thename.

All Domain users can access the share unless you specify one ormore user names. With one or more names specified, only thelisted users can access the share. Built-In CIFS users can alsobe specified. See the Example section below. Add more Built-InCIFS users to the restorer with the user add command. In thelist of user names, group names can occur. Group names must havean at ("@") symbol before them. Group and user names shouldbe separated only by commas, not spaces. There can be spacesinside the name of a group, but there should not be spacesbetween groups. In the example below, there are two groupsfollowed by a user. Note that the 1st group name contains a


space.

Examples:Some valid user names lists are:"user1,user2""user1,@group1"" user-with-one-leading-space,user2""user1,user-with-two-trailing-spaces ""user-with-a middle-space,user2,user3""user1,@CHAOS\Domain Admins"

Access Group

Copies of the User Guide from before release 4.5.1 have under the heading "VTLgroup command" the following text: "Each Data Domain System device (mediachanger or drive) can have a maximum of 1 Access Group".This is no longer accuratefor multi-initiator, where devices may appear in more than one group when usingfeatures such as Shared Storage Option (SSO) etc.

Groups:

A GROUP is a container which consists of initiators and devices.

An initiator can be a member of only one GROUP. A GROUP can contain multiple initiators.

A device can be a member in as many groups as desired. But a device cannot be a member of the sameGROUP more than once.

GROUP names are case-insensitive, can be 256 characters in length and consist of characters from therange “A-Za-z0-9_-”.

The names: Default, TapeServer, all, summary and vtl are reserved and cannot be created, deleted, or haveinitiators or devices assigned to them.

A GROUP can contain 92 initiators.

A maximum of 128 GROUPS is allowed.

A GROUP can be renamed.

Devices:

A Device can be a member of as many GROUPs as needed/wanted, but it occurs only once in a givenGROUP. It is the Device name (or id) that is used to determine membership in a GROUP, not the LUNassigned.

A device may have a different LUN assigned in each GROUP it is a member of.

When adding a device to a group, the FC Ports that the device should be visible on can also be specified.

Port names are two characters, namely: a digit representing the physical slot the HBA resides in and acharacter representing the port on the HBA. “3a” would be port ‘a’ on the HBA in slot 3.

Acceptable port names are: none, all or a list of port names separated by commas (3a,4b for example).


Known IssuesNew issues for this release are listed separately. Known issues that carry over from earlierreleases are grouped by subject.

When managing 4.3.x Data Domain systems from the 4.4.x Group Manager, somethings cannot be seen, including filesys space, number of alerts, etc. (15415)

The disk add enclosure command does not work if one or more of the newdisks is in a state of foreign. Use the disk unfail command to change theforeign disk to spare.

If you manually trespass a LUN via Navisphere, the auto-failback feature puts the LUNback where it was almost immediately. To avoid this in 4.4: when trespassing the LUNon clariion, make sure to change the default owner of the LUN as well. (14353)

Previous releases were configured by default to indicate support of Extended Attributes(EA) to CIFS clients, even though support for writing/reading them was not actuallyprovided. This default behavior has been changed to indicate non-support of EA. Thesystem can be reverted to the previous behavior with the following cifs option (16705):

“cifs option set easupport yes”

Issues Highlighted in Previous Releases

CIFS

If a CIFS share is deleted and recreated using the same name for the share but adifferent path, existing CIFS client connections continue to point to the original path.On the Data Domain System, enter the cifs disable and cifs enable commands to resetthe connections. (14026) (12719)

With directory replication from a Data Domain System that stores CIFS and NFSdata, use separate replication contexts for each type of data. Do not use onereplication context to replicate a mix of both types of data. Also, before usingdirectory replication for CIFS data and NFS data mixes, contact Data DomainTechnical Support before configuring the replication contexts.

If a CIFS client cannot map to a Data Domain System in an environment withmultiple domain controllers, the joining of the Data Domain System to an activedirectory domain probably failed. Domain controllers out of sync cause the problem.Look in the Data Domain System log files for messages similar to Preauthenticationfailed or Client not found in Kerberos database.

The workaround is to join the Data Domain System to a domain using a single IPaddress in the CIFS command on the Data Domain System. For example: (9253)

# cifs set authentication active-directoryyour.company.com 192.168.10.12


When using Windows domain or active directory mode authentication on a Data DomainSystem, adding 50,000 or more user accounts can lead to memory allocation errorssimilar to: (8382)

tdb/tdbutil.c:tdb_log(725)tdb(/var/run/samba/winbindd_cache.tdb): tdb_mmap failed for size8511488 (Cannot allocate memory)

Enter the following command on any Data Domain System that will have 50,000 ormore user accounts. The command doubles the memory available for user accounts.

cifs option set "dd winbindd mem limit" 157286400

Windows 2000 SP4 or Windows 2003 SP1 domain controllers with the latest Microsoftsecurity patches may not be able to map drives on a Data Domain System that usesdomain authentication. To positively identify the situation, use the log list commandon the Data Domain System to find the log file with a name using the IP address of theWindows client. In the file, look for messages similar to: (10068)

[2005/12/05 10:55:54.323869, 1] auth/auth.c:check_ntlm_password(271) check_ntlm_password: winbind authentication foruser [Administrator] FAILED with error NT_STATUS_NO_SUCH_USER

Also use the log list command to find the winbindd log. Look for messagessimilar to:

[2005/12/05 10:43:07.382802, 1]nsswitch/winbindd_rpc.c:sequence_number (905)sequence_number: Unable to get samr handle:NT_STATUS_INSUFFICIENT_ RESOURCES

The workaround is to set the following CIFS option on the Data Domain System toallow anonymous lookups:

sysadmin# cifs option set clientschannel no

If the domain controller is using Windows 2003 SP1 with the latest security patches,also set the Network access: Allow anonymous SID/Name translation security policyon the Windows system to enabled.

Trusted domain support is currently disabled to improve performance. To enable trusteddomain support, enter the following command on the Data Domain System:

sysadmin# cifs option set allowtrusteddomains yes

Change A CIFS Backup Server Setting.

Internal activities on a Data Domain System can take longer than a default CIFStimeout, leading to an error message from the media server. The message is similarto: Network name no longer existed. On all CIFS backup servers using a DataDomain System, change the SESSTIMEOUT value from the default of 45 (seconds)to 3600. (2478)


If you want detailed background information, see the following web page:http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q102/0/67.asp&NoWebContent=1

Open REGEDT32 and navigate toHKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\LANMANWORKSTATION\PARAMETERS

If the SESSTIMEOUT key does not exist, click in the right panel and select Newand DWORD value. Create a new key, SESSTIMEOUT. Note: The registry is casesensitive. Use all caps for the new key name.

Double click on the new (or existing) key. In the Base box, click the Decimal button, and set the key value to 3600. With CIFS configured for Active Directory mode, be sure that the realm is fully

qualified. For example: domain_name.yourcompany.com *. The domain namealone does not allow connectivity. Use the cifs show config command tocheck the realm entry. Use the cifs set authentication command to resetthe realm.

Replication

After setting the replication throttle with a small value (such as 50 KB), the systemshow detailed-stats command (alias: iostat) with a small interval (such as 5 seconds)on the replication source may show much larger or much smaller (even zero) bytes-out values than the throttle value. After a large amount of data is sent, the system mayhave to wait for buffers to clear when writing data to the destination. Over time, theactual bytes-out performance follows the throttle value. (12710)

After a replication recover operation to a collection replication source, run the filesysrestart command on the source. (12709)

With directory replication, initialization or recovery from a Data Domain System thatis close to full may cause the receiving Data Domain System to run out of space.Replication stops, and log messages inform you that the system is out of space.

Run a filesys clean operation on the Data Domain System that has run out ofspace. With replication initialization, run the command on the replication destination.With replication recovery, run the command on the replication source (the systemthat has run out of space). (11089)

When configuring directory replication, be sure that the space available for thedestination directory is at least as large as the expected maximum size of the sourcedirectory. (9501)

When performing a replication recover operation to a collection replicationsource that used the VTL feature, the procedure must include a vtl disablecommand on the source before you enter the filesys destroy command. (9505)


When changing an IP address for a Replicator source or destination Data DomainSystem: The Replicator throttling feature that controls the flow of data during replicationshould not restrict data flow. Use the following command on the source to set the throttlerate to unlimited: (5276)

replication throttle set current unlimited

After the IP address change is complete, use the following command to returnthrottling to the scheduled rate:

replication throttle reset current

Expansion Shelves

If more than two disks are missing or failed from the primary disk group (dg0 asdisplayed with the disk show raid-info command), the Data Domain Systemcannot boot. The situation can occur unexpectedly when primary disk group disks areon an expansion shelf and the shelf is disconnected from or not available to the DataDomain System. Make sure that the expansion shelf is connected and available andreboot the Data Domain System. (11382)

Configuration

The net enable ethx command also tries to enable any Ethernet interfaces thatare marked as enabled but that are disconnected or otherwise physically not available.The command output then includes a message Configuring network …timed out andenters messages in the system log. The messages are for your information only andthe target interface is enabled (if it is connected). (10144)

Each backup file written to or read from a Data Domain System is seen as a stream.For optimal performance, Data Domain recommends the following limits on streamsbetween Data Domain Systems and your backup servers:

Platforms Total Max WriteOnly

Max Readonly

Mixed

DD580DD580gDD565 – 12GB

20 20 20 Up to16 writes andup to16 reads

DD565 – 8GBDD560DD560g

20 20 16 Up to 12 writes andUp to 8 reads

DD4xxDD460gDD510DD530DD120

16 16 4 Up to 12 writes andup to 4 reads


A directory at any level (including /backup) on a Data Domain System can have nomore than 31998 subdirectories. Messages similar to the following appear when the limitis reached:

Nov 14 01:56:16 rstr01 ddfs: ERROR sfr: failed to mkdirdaily/load1. Too many links.

You can configure different network interfaces on a Data Domain System to differentsubnets. However, multiple interfaces must not be linked to the same LAN or VLAN inthe network.

If you use a terminal emulator to setup and configure a Data Domain System through theData Domain System serial port, do not run the terminal emulator on a server that usesWindows 2003 Service Pack 1. The combination does not configure the serial portcorrectly on the Data Domain System.

If the Data Domain System serial port is configured incorrectly, connect to the DataDomain System using a terminal emulator from a server that does not use Windows2003 Service Pack 1, set Hardware Flow Control to OFF, and on theData Domain System, enter CTRL-C.

Miscellaneous

Some lines of output from the system show detailed-stats command (alias: iostat)may show no NFS activity when data transfer is active. The statistics are updatedevery two seconds. Other system activity can slow the collection of data for theupdate to just over two seconds, giving 0 (zero) activity for the period. (11892)

The disk show performance command displays various disk performancemeasurements. All values are cumulative from the last power cycle or disk resetperformance command. Performance numbers tend to be very low over time asthe system is idle when not reading or writing data. (9518)

If the filesys destroy command is interrupted before completion, the DataDomain System file system may not be able to recover, depending on the state of theoperation. The system cannot be rebooted when the file system is not available. CallData Domain Technical Support for assistance. (3786)

The system NVRAM cards may generate alerts messages similar to the following:

NVRAM potentially failing: Battery 1 at low charge andnot charging.NVRAM potentially failing: Battery 2 at low charge andnot charging.

The batteries are probably not failing, but are disabled. Use the system statuscommand to check. Look at the NVRAM section:


battery 1 0% charged, enabledbattery 2 0% charged, enabled

If the battery lines are similar to the messages above, with both batteries listed as 0%charged:

- Run the system poweroff command.- Remove and then replace the power cables.- Restart the system.- Enter the system status command again.

The batteries should appear as fully-charged. If not, the NVRAM card needs to bereplaced.

Data Domain, Inc.2421 Mission College Blvd.Santa Clara, CA 95054-1214

USAPhone: 408-980-4800 Direct

877-207-3282 Toll-freeFax: [email protected]://support.datadomain.comCopyright © 2008 Data Domain, Incorporated

4.4rel-notes

Documents