Yuzuy is an advanced administration software designed to extend and enhance the capabilities of Qumulo's native Administrator UI. It provides centralized management for multiple Qumulo clusters, simplifying workflows and enabling efficient operations.

Qumulo is the hybrid cloud data platform that offers file data management at any scale, in any location, with your choice of hardware and cloud. Qumulo has been recognized as a leader in the Gartner Magic Quadrant for Distributed File Systems and Object Storage for several consecutive years. This recognition underscores its strong position in the market and its ability to deliver robust and reliable file storage solutions.

Yuzuy enhances Qumulo by offering several key advantages:

• Disaster Recovery Automation: Yuzuy automates failover and failback processes in case of a storage outage or planned downtime, minimizing downtime and ensuring business continuity.
• Multi-Cluster Synchronization: Keeps configuration objects consistent across multiple Qumulo clusters, reducing administrative overhead and ensuring uniformity.
• Simplified Management: Provides a centralized platform for managing multiple Qumulo clusters, streamlining workflows and improving administrative efficiency.
• Intelligent Anti-Malware Integration: Offers a scalable and intelligent anti-malware integration specifically designed for Qumulo, providing robust protection against threats.

Qumulo Continuous Replication is a feature that allows you to automatically replicate data from specific directories to a designated secondary Qumulo cluster. It supports both continuous and snapshot-based replication, ensuring data copies are kept up-to-date once activated and configured.

Yuzuy is integrated into the Qumulo Customer Success Slack channel, allowing for direct communication and collaboration between Qumulo and Yuzuy teams. This ensures efficient case analysis and resolution, providing a streamlined support experience. Support is also accessible by phone and email.

We emphasize direct and efficient support. We recognize the frustration of traditional support methods and strive to streamline the process. By integrating with Qumulo's Slack channel, we offer a collaborative approach where customers can interact directly with both Qumulo and Yuzuy teams, eliminating the need for back-and-forth communication between vendors.

We prioritize customer benefit and strive to ensure issues are resolved effectively, not just processed through a ticketing system.

Yuzuy is particularly beneficial for managed service providers who support multiple clients with diverse systems. The automation capabilities of Yuzuy allow for:

• Consistent Service Quality: Ensures that disaster recovery and synchronization processes are standardized and reliable across all client environments.
• Efficient Scaling: Simplifies the management of multiple Qumulo clusters, allowing service providers to scale their operations efficiently.
• Reduced Operational Costs: Automation reduces the need for manual intervention, freeing up staff time and lowering operational expenses.

Yuzuy unlocks a number of benefits for organizations using Qumulo:

• Enhanced Operational Safety: Yuzuy simplifies disaster recovery operations and encourages routine testing, leading to increased confidence in disaster preparedness.
• Dependability in Critical Situations: The automation and ease of use provided by Yuzuy enhance reliability during emergencies, as complex operations can be tested frequently without disrupting productivity.
• Reduction of Knowledge Gaps: Yuzuy's automation helps bridge knowledge gaps within IT teams, especially for critical operations. The documentation required to operate Yuzuy is very straightforward.
• Unlocking IT Talent without Coding: Yuzuy's process transparency benefits administrators and managers, reducing the need for extensive coding skills.
• Efficient Support for Shared or Managed Service Organizations: Automation in Yuzuy enables managed service providers to effectively support multiple clients with diverse systems, maintaining service quality and scalability.
• Meet compliance requirements: The intelligent anti-malware integration allows you to tick off IT security requirements.

Yuzuy's "Failover and Failback" feature automates workflows in case of storage outages or planned downtime by orchestrating tasks related to Qumulo's Continuous Replication.
It simplifies disaster recovery operations, making them more manageable. It empowers organizations to test their disaster recovery plans regularly, leading to increased operational safety.

Yuzuy utilizes a straightforward subscription-based licensing model. A subscription includes all features, support, and updates for the duration of the subscription. For specific pricing details, it is recommended to contact Yuzuy directly or reach out to a Qumulo partner.

Yuzuy counts the raw capacity in terabytes (TB) across all connected Qumulo clusters.
For example, if you have two clusters, each consisting of six nodes with 92 TB per node, the calculation would be:
6 nodes × 92 TB × 2 clusters = 1,104 TB to license.

No, only the Qumulo clusters managed by Yuzuy require a license.

Yuzuy offers a single subscription type to keep licensing as simple as possible. This ensures that all customers have full access to every Yuzuy feature at any time, without restrictions or additional costs.

No, virtual nodes are not counted by Yuzuy. Nevertheless, they are fully supported.

No, the Bareos plugin is a separate product and not included in the Yuzuy subscription. It is the only exception to our "all-inclusive" approach.

Yes, we include one day (8 hours) of implementation support for every customer at no additional cost.

You can review the onboarding process at yuzuy.com/onboarding.

Yuzuy's Failover and Failback function leverages Qumulo's Continuous Replication, which creates data copies in designated directories on a secondary Qumulo cluster.

In a disaster scenario or during planned downtime, Yuzuy automates the following:

1. Failover: Yuzuy performs a series of actions on both the primary and secondary clusters. This includes redirecting client access to the secondary cluster and making the replicated data writable.
2. Failback: When the primary cluster is back online, Yuzuy automates the process of switching back to the primary cluster. It offers options to replicate newly created data back to the primary cluster or discard it, providing flexibility in data management during recovery.

Yuzuy simplifies the failover/failback process by:

• Automating Complex Workflows: Handles all the necessary steps in the correct order, ensuring a smooth and reliable transition.
• Built-in Checks: Performs various checks throughout the process to ensure the integrity and consistency of data.
• Centralized Management: Provides a single interface to trigger and monitor the entire failover and failback operation.

Yuzuy offers two Failover and Failback modes to accommodate different client access protocols and configurations:

1. IP Failover: Used primarily for NFS clients. During failover, the specified IPs are moved from the primary to the secondary cluster, redirecting client access. It can also be used for SMB clients, but clients would have to reconnect as their initial Kerberos tickets would be invalid.
2. DFS Failover: Designed for SMB shares accessed through DFS. During failover, the specified IPs are removed from the primary cluster without being transferred to the secondary. DFS automatically redirects clients to the secondary cluster, allowing them to maintain their connections and Kerberos tickets for uninterrupted access.

Yuzuy supports all replication modes available in Qumulo.

Yes, Yuzuy fully supports cross-replicating Qumulo clusters. All Yuzuy functions, including Failover and Failback, Synchronization, and Anti-Malware, work seamlessly with clusters that replicate in both directions. These functions continue to operate in failover state, whether after a planned switch between clusters or a failover due to a failure.

This is currently not supported. The main reason for this is that it can lead to incomplete test routines and ultimately weaken the resilience of disaster recovery processes. We carefully listen to feature requests in this regard. In case this is something your organization needs, we are open for discussion.

Yuzuy does not offer this by a reason. An imperfect monitoring would raise the risk of false positives and unnecessary failovers. There are great monitoring and ITMS solutions out there. Yuzuy easily integrates with them via REST API.

During the initial setup, Yuzuy requires access to the IP addresses of the Qumulo node you provide in the setup dialog. For Failover and Failback, Yuzuy uses all nodes' persistent IP addresses, which must be accessible from Yuzuy’s IP.

Qumulo limits the number of floating IP addresses per storage node per VLAN to 10. This should be taken into account. This applies especially in failover scenarios where a cluster with many nodes fails over to one with fewer nodes, as typically all floating IPs from the primary cluster must be transferred to the secondary.

In failover relationships with significant differences in the number of nodes between clusters, there's a risk of exceeding the 10 floating IP limit on the secondary cluster, leading to errors. Yuzuy checks for this during configuration and alerts you. Proper planning of floating IP distribution from the start is recommended to avoid DNS changes later. Yuzuy also assists with a planning tool for IP address distribution.

A few seconds.

For planned failovers and failbacks, Yuzuy waits for replication to complete before proceeding. The timeout for this can be configured, and if necessary, Yuzuy can cancel the ongoing replication and force a failover. In the event of a cluster outage, some data in flight may not have been replicated yet.

During a failback, you can choose to replicate new data back to the primary cluster or discard it. Typically, new data is replicated back, with the duration depending on the amount of data and performance. Clients remain connected to the secondary cluster without interruption. Once the primary cluster is up to date and in continuous replication state, the final step of the failback takes only a few seconds.

Yuzuy facilitates Qumulo's built in continuous, snapshot-based replication. RPO is the latest replicated snapshot. 

That is not necessary. Yuzuy leverages the DFS-N concept. It only needs to be touched, when you add or change shares that your clients should be able to access via DFS.

No changes are required on the Yuzuy side. In your Windows domain's DFS configuration, you'll need to add new shares (if they’re not already accessible through a higher-level share) or update the names of any modified shares.

Yes, failover to or from a Qumulo public cloud deployment is generally possible, with the exception of creating or deleting IP addresses in the cloud environment, which is restricted by hyperscalers.

Qumulo's Continuous Replication handles data replication, but configuring the replicated directory on the target cluster is typically a manual task. Yuzuy simplifies this by providing automatic synchronization of configurations associated with a replication relationship.

Configurations that Yuzuy can synchronize include:

• SMB Shares
• NFS Exports
• Quota
• Permissions
• Access Rules
• Share Options

Benefits of Yuzuy's Synchronization:

• Reduced Administrative Effort: Automates configuration synchronization, eliminating manual tasks and reducing the potential for errors.
• Consistency Across Clusters: Ensures that configurations on the source and target clusters are aligned, simplifying management and reducing complexity.
• Failover/Failback Awareness: Configuration changes made during a failover are synchronized back to the primary cluster during failback, maintaining data integrity and consistency.

Yes, Yuzuy can manage multiple synchronization relationships across several clusters. However, we recommend testing your specific setup using a virtual Proof of Concept (PoC).

Yes, synchronization for a specific cluster pair must be managed by only one Yuzuy instance.

Yuzuy’s Anti-Malware Integration provides event-based malware scanning, leveraging proven detection technology and integrating with existing security architectures. This feature is included with Yuzuy at no extra cost. It allows organizations to maintain a baseline of protection for their file storage without relying solely on client-side scanning.

When changes occur in the file system, such as file creation or modification, Yuzuy detects them and sends this information to Yuzuy agents installed on designated scan servers. These scan servers, equipped with chosen antivirus software, receive the information, trigger a scan, and initiate appropriate follow-up actions.

The AV-integration is a generally open integration, that works with AV-software from various vendors. It does not bring its own AV.

Yuzuy integrates with antivirus solutions that have a command-line interface (CLI). Not all antivirus solutions offer a CLI, and some may have limitations, such as compatibility issues with UNC paths. Yuzuy has successfully tested and integrated with several antivirus solutions, and we encourage potential users to contact us to confirm compatibility with their preferred antivirus software.

Organizations might choose to integrate their existing antivirus solution with Qumulo or add a new antivirus engine. The compatibility of your chosen software with Yuzuy is crucial in determining your approach. Yuzuy offers support in setting up a proof of concept (PoC) using either a non-disruptive virtual configuration or a section of your production system.

The integration consists of two parts: the existing Yuzuy software and the Yuzuy Anti-Virus Protection Client for scan servers.

Yuzuy Anti-Virus Protection Client: This software is installed on physical or virtual servers that handle the malware scanning. Multiple workers can be integrated with a single Yuzuy instance, and they easily connect to Yuzuy for centralized configuration.

The entire configuration happens inside Yuzuy. You can assign specific Qumulo clusters to each scan server, choose the antivirus software installed on each server, and configure its scan parameters directly in Yuzuy.
While the protected paths on the Qumulo clusters are selected from the Yuzuy GUI, Yuzuy automatically manages redundancy by excluding subdirectories from higher-level protection if both are selected.

Scalability: The scan workload is automatically distributed among configured scan servers, and you can scale scan performance by adding more servers.

Logging: Yuzuy’s logging system helps monitor scan activity, identify issues, and ensure comprehensive protection.

Yuzuy’s internal logging records the response codes for every file scan command sent to the antivirus agent, ensuring that no files are missed.

Yes, deployment using tools like SCCM is supported.

Yes, Yuzuy supports changes to cluster configurations. After modifying nodes or IP addresses, review the Yuzuy configuration to ensure continued operation. In Yuzuy 1.2.2, a status message in the GUI will alert you to such changes. Future versions will include a more advanced notification system.

System Requirements: 

• Qumulo Cluster Version: Both source and target Qumulo clusters must run the same version of Qumulo Core (2.12.0 or above or 4.0.0 or above).
• Hypervisor: A hypervisor compatible with OVA images (e.g., vSphere/ESXi 6.5 and later). For compatibility with other hypervisors, please contact Yuzuy.
• CPU, RAM & Storage: 4 CPU cores, 8 GB RAM and 100 GB storage are a good starting point. An active anti-malware integration will need a more, depending on the file change rate.
• Admin Privileges: Admin privileges are required for all Qumulo clusters being managed by Yuzuy. A role with the necessary privileges can also be used.

No, internet access is not needed, either during the initial setup or for ongoing use.

Yes, Yuzuy offers API access, allowing for integration with external systems and automation of tasks such as triggering failover or failback operations.

That's currently not Supported. Although this is something we have in the backlog and might be available in the future, there should always be a local user in the software, that can be used, when the identity provider is unavailable.

MFA is not yet available but will be offered in the future.

Yes, these functions can be used independently. Although they are designed to work seamlessly together and consider each other’s state, they do not depend on one another to operate.

This is generally possible but should be thought through carefully.

Yuzuy is delivered as an OVA image that you run in your data center or cloud. After importing and starting the virtual machine, the install wizard guides you through the initialization process. Software updates are performed manually using the integrated update function.

Yuzuy offers in-place upgrades that are self explanatory and non-disruptive.

Yuzuy’s cloud readiness is in progress. Currently, the Yuzuy appliance is not fully cloud-ready but can be deployed on VMware within cloud environments.

While Yuzuy doesn't have built-in replication between instances, customers can run multiple instances for redundancy. Commonly, the hypervisor's replication feature is used to ensure the high availability of the Yuzuy software itself. The Synchronization between two certain clusters must only run on one Yuzuy instance.

my.yuzuy.com is a user-friendly online platform that serves as a central hub for:

• Existing Customers: Streamlines Yuzuy experience management.
• Consultants and Engineers: Provides access to demo or PoC licenses.

Key features of the portal include:

• Software Updates: Easy access to the latest Yuzuy software versions.
• Centralized Resources: Provides a single location for product documentation and licenses.