Skip to main content
Home

Search form

Menu

Search form

  • SkyVault 2.0 overview
  • Video tutorials
  • Using SkyVault 2.0
  • Managing Share features
  • Managing users and groups
  • Working with SkyVault licenses
  • Components of a SkyVault solution
  • Recommendations for split architecture
    • When to split
    • How to split
      • Scenario: Clustering for redundancy
      • Scenario: Clustering for high throughput
  • Setting up repository server cluster
  • CIFS clustering through load balancer
  • Tracking clustering issues
  • Setting up multi-tenancy
  • Creating and managing workflows
  • Setting up Enterprise to Cloud Sync
  • Managing transformations
  • Setting up content stores
  • Setting up and managing content replication
  • Importing and transferring files
  • Migrating
  • Monitoring SkyVault
  • Backing up and restoring
  • Auditing SkyVault
  • Copyright
  • You are here

    SkyVault 2.0 » Administering » Setting up clustering » Setting up Share cluster » Recommendations for split architecture

    How to split

    When you have decided to upgrade from a single node environment to a distributed or clustered environment, you must find the most appropriate way to cluster SkyVault's architecture.
    • Scenario: Clustering for redundancy This is a scenario-based topic describing the clustering architecture for redundancy and high availability of SkyVault services.
    • Scenario: Clustering for high throughput This is a scenario-based topic describing the clustering architecture for maximizing throughput of SkyVault services.
    Parent topic: Recommendations for split architecture

    © 2017 TBS-LLC. All Rights Reserved.    Follow @twitter