9.Enter the desired size of the Mirror Buffer.

The mirror buffer stores file system write transactions while they are being transferred to the mirror server. The size of the mirror buffer depends on a variety of factors, but must be at least 100 MB. You may want to create a mirror buffer that is approximately 10% of the size of the file volume you are replicating. The size you choose should depend on how much information is being written to the file volume rather than the size of the file volume. The file volume free space on the active server will be reduced by the allocation size of the mirror buffer. Our general recommendation is 10% of the volume to be replicating.

10.Select option "7", "Save Changes" to proceed.

11.To verify status, return to the Mirrors submenu, and view details by selecting the "Mirror" option, usually "A" or "B."

This display shows status complete and details of current operations.

2.37StorEdge File Replicator Issues

Since File Replicator operates at the disk block level, the mirror system is an exact replica of the master system. However, since replicating operations are not strictly real time, the mirror system may lag the master by a time delta dependent on the speed and quality of the network. While this network lag may prevent the mirror system from being an exact copy of the master at any given point, the integrity of the mirror system is guaranteed at all times. Only complete file system transactions are replicating. In the course of creating a duplicate volume, a mirror goes through three main phases: creation, replication, or sync, and sequencing. File Replicator is a fault- tolerant technology. In all of the three main phases, the mirror handles errors with the intent of self-recovery as much as possible. When errors are encountered that are too severe for the mirror to handle on its own, it enters an ERROR state. In this state, user intervention is required to remedy the error and restart the mirror.

A list of all mirror states and their definitions can be found in the "Error Codes" section at the end of this document. The mirror states are very useful for troubleshooting.

Configuration

File Replicator requires that the NIC card to be used for File Replicator is designate as a mirror role, and that the network connection for this card be private. Also check that a host entry exists in both systems to provide a path to mirror and master.

2-152Sun StorEdge 5310 NAS Troubleshooting Guide • December 2004

Page 197 Page 199
Page 198
Image 198
Sun Microsystems 5310 NAS manual StorEdge File Replicator Issues, Enter the desired size of the Mirror Buffer
Page 197 Page 199

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