StorEdge has same files in 2 different shares.

This is caused by creating multiple share names that point to the same directory or volume. Shares always point to a directory. Root level shares will always contain all files on the volume, regardless of how many shares are created to this volume. View shares as pointers, with the understanding that many of these pointers may exist to a single location.

User maps are incorrect.

User maps are not automatically created.

The requirements for successful user mapping are to import all NFS users to the StorEdge and define a mapping rule. These requirements must be met before any CIFS/SMB users have connected. If CIFS/SMB users connect before both of these are in place, the user will be mapped to a StorEdge-generated UID.

Once the mapping has been created, it will not be overwritten by subsequent connections with updated credential info.

Windows users are not mapped to the expected NFS group. Mappings are not created for most Windows groups.

Although Windows users can maintain membership in many groups, the StorEdge user and group mapping functionality only recognizes the Primary Group. By default, all Windows Users are assigned the primary group, “Domain Users”. The only exception to this is if they are a member of the “Domain Admins” group at the time the user account is created, in which case this group is assigned as the primary group.

In order for group mapping between CIFS/SMB and NFS to be effective, primary group assignments must be made selectively. It may be necessary to create some groups. Primary group assignment is done is Windows User Manager for Domains, usually from a Domain Controller. See your Windows documentation for details on how to configure this setting. It is important to use only Windows “Global Groups” for this purpose. Windows Local Groups are intended to be used only locally, on the Domain Controllers themselves.

After making modifications to Windows users’ primary groups, groups with no mappings will be mapped to NFS groups according to the mapping policy. The mapping will be automatically created as soon as a CIFS/SMB user connects with a primary group which is not in the StorEdge group.map file. Before this happens, make sure that group information is imported to StorEdge, either manually or via NFS, and the desired mapping policy is in place.

Chapter 2 NAS Head 2-51

Page 96 Page 98
Page 97
Image 97
Sun Microsystems 5310 NAS manual StorEdge has same files in 2 different shares
Page 96 Page 98

5310 NAS specifications

Sun Microsystems, known for its innovative computing solutions, launched the Sun 5310 Network Attached Storage (NAS) system, which marked a significant advancement in the realm of storage solutions in the early 2000s. The 5310 NAS was designed to provide high-performance, reliable, and scalable storage tailored for enterprise environments.

One of the standout features of the Sun 5310 NAS is its file-serving capabilities, which support multiple protocols, notably NFS (Network File System) and CIFS (Common Internet File System). This dual-protocol support allowed organizations to seamlessly integrate the NAS into diverse IT ecosystems, facilitating interoperability between UNIX, Linux, and Windows systems. The enhanced file-sharing capabilities made it an ideal solution for businesses with mixed operating environments.

The Sun 5310 NAS incorporates cutting-edge technologies to ensure high availability and data integrity. The system utilized a RAID (Redundant Array of Independent Disks) technology, providing various RAID levels to protect against data loss while optimizing performance. Additionally, the device featured hot-swappable drives, enabling maintenance and upgrades with minimal downtime, a crucial factor for business continuity.

Equipped with advanced management software, the Sun 5310 NAS offered users an intuitive interface for monitoring storage health and performance. This software included comprehensive reporting functionalities that allowed IT administrators to oversee usage patterns and capacity planning efficiently.

Scalability was another defining characteristic of the Sun 5310 NAS. The system could easily expand with additional storage modules, accommodating the growing needs of an organization without the necessity for complete system overhauls. This flexibility ensured that businesses could adapt their storage solutions to meet evolving data storage needs without incurring significant costs or disruptions.

In terms of performance, the Sun 5310 NAS featured high I/O throughput achieved through its robust hardware architecture and optimized file serving capabilities. This performance baseline was crucial for organizations that relied on heavy data workloads and required rapid access to information.

In summary, the Sun 5310 NAS from Sun Microsystems embodied a forward-thinking approach to network storage, blending reliability, scalability, and multi-protocol support. Its user-friendly management software, combined with the robustness of RAID technology and hot-swappable drives, made it a preferred choice for enterprises looking to streamline their storage infrastructure while safeguarding critical data.
Top Page Image Contents