Storage configuration
Local path: When you choose the local path option in Zmanda Pro, it means your data will be stored right on your computer's hard drive.
How to set it up: You need to specify the location on your computer where you want your data to be stored.
Things to know:
Zmanda doesn’t restrict the number of times you can access your stored data simultaneously, so you can access it whenever you need.
If you’re using Windows, be aware that some versions have a limit on how long your file paths can be. However, if your storage path is on a network drive, keep in mind any restrictions on both the mapped drive and its source drive.
Virtual storage locations
On top of physical storage locations (like local disks, SFTP servers, or Amazon S3), Zmanda Pro offers virtual storage locations that might combine aspects of both for extra features.
Using cloud storage with Zmanda Pro
Supported cloud storage providers: Zmanda Pro supports any storage provider compatible with S3.
Configuring cloud storage: You can set it up on the Zmanda Pro Server or directly on the Zmanda Pro Backup client. Configuring it on the server is recommended for better performance.
Direct-to-cloud method:
Backup data goes straight from the client to the cloud storage provider.
Cloud storage credentials are visible in the Zmanda Pro Backup client (although somewhat hidden).
You can use this method with Storage Templates (define cloud provider details once) and custom Storage Vaults (unique credentials per user).
Available storage locations
Local Path: Stores data on your local filesystem.
Zmanda Pro Server Storage Role Bucket:
This option appears under a different name in the Zmanda Pro Backup client.
The Zmanda Pro Server includes a "Storage Role" microservice that allows creating buckets with secret keys for storing and retrieving data.
You cannot use another Storage Role Bucket as a storage location.
SFTP:
Stores data on an SFTP server (like OpenSSH). SFTP stands for Secure File Transfer Protocol, a secure way to transfer files over a network.
What You'll Need:
SFTP Server Details:
Address: The hostname or IP address of your SFTP server. You can optionally specify the port number after a colon (":"). The default port is 22.
Username: The username for your SFTP account.
Remote Path (Optional): A specific folder on the SFTP server where you want to store your backups. If left blank, backups will be saved in your SFTP user's home directory.
Authentication Details:
Authentication Type: Choose how you want to connect to the SFTP server. Options include:
Native: Uses your system's existing OpenSSH configuration for login.
Password: Enter the password for your SFTP account.
Private Key: Provide your SFTP account's unencrypted private key in OpenSSH format.
Verification: Select how to verify the SFTP server's identity for security reasons. Options include:
Native: Uses your system's OpenSSH configuration for verification.
Allow Any Host Key (Not Recommended): Skips verification (insecure, not recommended).
Custom Path to Known Hosts File: Specify a local file that stores trusted SFTP server keys.
Creating the SFTP Backup Configuration
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "SFTP" as the destination type.
Enter the required SFTP server details mentioned earlier (Address, Username, Remote Path).
Select the desired authentication type (Native, Password, or Private Key) and provide the necessary credentials.
Choose the verification method for the SFTP server (Native, Allow Any Host Key, or Custom Path).
Save the configuration.
FTP:
Stores data on an FTP server (like FileZilla Server or ProFTPd). It's important to note that FTP has security weaknesses and is considered a less secure option. If possible, using SFTP (Secure File Transfer Protocol) or a local network share (SMB or NFS) is recommended for better performance and security.
What You'll Need:
FTP Server Details:
Address: The hostname or IP address of your FTP server. You can optionally specify the port number after a colon (":"). The default port is 21.
Username: The username for your FTP account.
Password: The password for your FTP account.
Optional Settings:
Use Default Directory: Choose whether to store backups in your FTP user's home directory (default) or a custom location.
Custom Directory (if applicable): Specify a specific folder on the FTP server to store backups (only needed if not using the default directory).
Connections: Set the number of simultaneous backup connections to the FTP server (default is 5).
Accept Invalid SSL (Not Recommended): This option is for advanced users only and should generally be avoided for security reasons. It allows connecting to FTP servers with untrusted security certificates (not recommended).
Creating the FTP Backup Configuration
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "FTP" as the destination type.
Enter the required FTP server details (Address, Username, Password).
Decide where to store backups:
Select "Use Default Directory" to use your FTP user's home directory (default).
If you prefer a specific location, choose "Custom Directory" and provide the folder path on the server.
Adjust the number of connections if needed (default is 5).
Leave "Accept Invalid SSL" unchecked for security reasons (unless instructed otherwise).
Save the configuration.
Amazon S3:
Backing Up to Regular Amazon S3
Requirements:
An Amazon S3 account with appropriate permissions.
The globally unique name of the bucket you want to store backups in.
Configuration Steps:
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "Amazon S3" as the destination type.
Enter your Amazon S3 access key and secret key.
Specify the name of the S3 bucket where you want to store backups.
(Optional) Add a subdirectory within the bucket to organize your backups separately (useful if sharing the bucket with other applications).
Save the configuration.
Backing Up to Amazon S3 China (Special Case)
Use this section only if you have an Amazon S3 account specifically for the China region.
Requirements:
An Amazon S3 account for the China region with appropriate permissions.
The globally unique name of the bucket you want to store backups in (can be the same name used in a different region for China S3).
The specific endpoint for accessing Amazon S3 China (e.g., region).
Configuration Steps:
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "Amazon S3 China" as the destination type.
Enter the endpoint for your China S3 region.
Enter your Amazon S3 China access key and secret key.
Specify the name of the S3 bucket where you want to store backups.
(Optional) Add a subdirectory within the bucket to organize your backups separately.
Save the configuration.
Google Cloud Storage:
Configuration Steps:
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "Google Cloud Storage" as the destination type.
Obtain your Google Cloud Platform (GCP) credentials:
Go to the Google Cloud Platform web interface.
Locate the "Interoperability" section and retrieve your access key and secret key.
Enter your GCP access key and secret key in the Zmanda Pro configuration.
Specify the name of the GCS bucket where you want to store backups.
(Optional) Add a subdirectory within the bucket to organize your backups separately (useful if sharing the bucket with other applications).
Save the configuration.
S3-compatible:
What is S3-Compatible Storage?
Amazon S3 is a popular cloud storage service and its object storage protocol has become widely adopted by other providers. This means you can use Zmanda Pro to back up your data to a variety of cloud storage solutions besides Amazon S3 itself.
Benefits of S3-Compatible Storage:
Flexibility: Choose from a variety of cloud storage providers to fit your needs and budget.
Scalability: Easily store large amounts of data and grow as your needs increase.
Durability: Most S3-compatible storage offers high data durability, ensuring your backups are safe and retrievable.
Security: Look for S3-compatible storage providers that offer robust security features to protect your sensitive data.
Configuration Steps:
Choose an S3-compatible storage provider: Refer to the "Cloud Storage Providers" document for a list of compatible options.
Gather your credentials: Obtain the access key, secret key, and any other necessary details from your chosen S3-compatible storage provider.
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "S3-compatible" as the destination type.
Enter the hostname of your S3-compatible storage server.
(Optional) If your provider uses a custom region, specify it here.
Enter your access key and secret key for the S3-compatible storage account.
Specify the bucket where you want to store your backups.
(Optional) Add a subdirectory within the bucket to organize your backups separately.
Select whether to use HTTPS for encrypted transmission (recommended).
Save the configuration.
Wasabi:
While Zmanda Pro allows connecting to Wasabi using the generic "S3-compatible" storage type, a dedicated Wasabi option is available for potentially better compatibility. Here's how to configure both methods:
Using the Dedicated Wasabi Option:
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "Wasabi Cloud Storage" as the destination type.
Obtain your Wasabi Cloud Storage access key and secret key. You can find these under the hamburger menu button (top left) and then clicking on "Access Keys."
Enter your Wasabi access key and secret key in the Zmanda Pro configuration.
Specify the name of the bucket where you want to store your backups.
(Optional) Add a subdirectory within the bucket to organize your backups separately.
Save the configuration.
Using the S3-Compatible Option:
Follow steps 1-3 from the dedicated Wasabi option instructions above.
Choose "S3-compatible" as the destination type.
Enter the hostname of your Wasabi Cloud Storage server (refer to Wasabi documentation for details).
(Optional) If Wasabi uses a custom region, specify it here.
Enter your Wasabi access key and secret key.
Follow steps 6-8 from the dedicated Wasabi option instructions above.
Wasabi and Immutability/Anti-Ransomware
While Zmanda Pro itself cannot prevent unauthorized access using your Wasabi credentials, Wasabi offers features to enhance backup security:
Object Locking: Zmanda Pro supports Wasabi's object locking functionality.
Bucket Versioning: Zmanda Pro works with Wasabi's bucket versioning feature. Here's what to consider:
Benefits:
Even if a file is deleted (intentionally or maliciously), it can be recovered from previous versions.
Considerations:
Wasabi charges for storing deleted versions.
Recovering deleted files requires additional steps (e.g., removing tombstone versions).
To manage storage costs, Wasabi recommends periodically deleting old versions (lifecycle policies).
Zmanda Pro's retention policy applies on top of Wasabi's versioning.
Permissions and Security
Storage Template Feature: If you use Zmanda Pro's Storage Template feature to create access keys, they will have limited permissions, allowing only "tombstoning" files (marking them for deletion) instead of permanently removing them.
Root Wasabi Key: The root Wasabi key has full permissions, so avoid using it for backups unless strictly necessary.
Custom IAM Policy: If using a custom IAM policy, ensure it restricts deleting entire version stacks.
Backblaze B2 Cloud Storage:
Backblaze B2 uses Application Keys for access control. You can configure Zmanda Pro to use either the Master Application Key or a per-bucket Application Key.
Using the Master Application Key:
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "Backblaze B2" as the destination type.
Enter your Backblaze B2 Account ID.
Enter your Master Application Key.
Specify the name of the bucket where you want to store your backups.
(Optional) Add a subdirectory within the bucket to organize your backups separately.
Select whether to hide deleted files instead of permanently removing them (more on this later).
Save the configuration.
Using a Per-Bucket Application Key:
Follow steps 1-3 from the Master Application Key instructions above.
Enter the Application Key ID for the specific bucket you want to use.
Enter the Application Key for the chosen bucket.
Complete steps 6-9 from the Master Application Key instructions above.
Alternative Connectivity:
Zmanda Pro also allows connecting to Backblaze B2 via the "S3-compatible" storage type if you use an S3-to-B2 gateway server like Minio.
Hiding Deleted Files
Backblaze B2 allows hiding files instead of deleting them. This feature can be beneficial for:
Ransomware Protection: Even if compromised, a key without the "deleteFiles" permission cannot remove hidden files.
Version Control: Hidden files can be recovered later if needed.
Important Considerations:
Lifecycle Rules: To prevent unlimited storage usage, set up Backblaze B2 lifecycle rules to automatically remove hidden files after a specific period.
Key Permissions: When using "hide files," ensure your key doesn't have the "deleteFiles" permission. Storage Templates automatically generate such keys.
Backblaze Fireball
Backblaze Fireball is a physical storage device. Here's how to configure Zmanda Pro for a Fireball backup:
Connect the Fireball to your network and enable SFTP.
In Zmanda Pro client, go to "Account" tab and select "Add Storage Vault."
Choose "Custom" and create a name for the vault.
In the "Storage" tab, select "SFTP" as the option.
Enter the Fireball's address, path, username, and password.
Back up your data to the Fireball.
Follow Backblaze's instructions to ship the Fireball to their data center.
Update the storage vault details to point to the corresponding Backblaze B2 bucket for future backups.
Azure Blob Storage:
Connecting to Azure Blob Storage:
Navigate to the section for configuring backup destinations.
Choose "Azure Blob Storage" as the destination type.
Enter the Realm Address (usually core.windows.net). Use a scheme-qualified URI (e.g., https://) to enable TLS encryption.
Enter your Azure Blob Storage account name.
Enter your account key.
Specify the container where you want to store your backups.
(Optional) Add a subdirectory within the container to organize your backups separately.
Save the configuration.
Using Third-Party Storage:
Zmanda Pro can connect to compatible third-party storage services using the Azure Blob Storage API. In the "Realm Address" field, enter the custom URL provided by your third-party storage provider.
Alternative Connectivity:
You can also access Azure Blob Storage using the "S3-compatible" storage type if you use an S3-to-Azure gateway server like Minio.
Filebase:
Using the Dedicated Filebase Option (Recommended):
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "Filebase Cloud Storage" as the destination type.
Obtain your Filebase Cloud Storage access credentials: Access Key and Secret Key. You can find these by clicking on "Access Keys" on the left-hand side of the Filebase web interface.
Enter your Filebase Access Key and Secret Key in the Zmanda Pro configuration.
Specify the name of the bucket where you want to store your backups.
(Optional) Add a subdirectory within the bucket to organize your backups separately.
Click "Test Connection" to verify successful communication with Filebase.
Save the configuration.
Idrive e2:
There are three ways to connect Zmanda Pro to IDrive e2:
Using the Dedicated IDrive e2 Option (Recommended):
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "IDrive e2 Cloud Storage" as the destination type.
Obtain your IDrive e2 access credentials: Access Key ID and Secret Access Key. You can find these by navigating to "Access Keys" on the left-hand side of the IDrive e2 web interface and clicking "Create Access Key."
Enter your IDrive e2 Access Key ID and Secret Access Key in the Zmanda Pro configuration.
Specify the name of the bucket where you want to store your backups.
(Optional) Add a subdirectory within the bucket to organize your backups separately.
Click "Test Connection" to verify successful communication with IDrive e2.
Save the configuration.
Using IDrive e2 as a Storage Template:
Zmanda Pro allows you to configure IDrive e2 as a storage template. This creates separate credentials and a private bucket for each storage vault using this template within your IDrive e2 account. Here's what you need:
Access Key ID: An access key with at least write access across all buckets in your IDrive e2 account.
Secret Access Key: The secret access key associated with the access key ID.
Using IDrive e2 with Constellation Remote Server (Optional):
Note: This is an advanced configuration and might not be necessary for typical backups.
The IDrive e2 credentials entered for Constellation, a Zmanda Pro component, are used to clean up unused buckets and access keys associated with your storage vaults. To avoid accidental deletion of buckets used by Zmanda Pro itself, it's recommended to have separate IDrive e2 accounts:
One account for your user buckets (where backups reside).
Another account for the Constellation storage role (used for cleanup).
Impossible Cloud:
Since Impossible Cloud is fully S3-compatible, configuration within Zmanda Pro is straightforward:
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "S3-compatible" as the destination type.
Obtain your access credentials from the Impossible Cloud console:
Navigate to the 'Keys' section within Impossible Cloud.
Refer to the Impossible Cloud documentation for detailed guidance on managing access keys.
Enter your Access Key and Secret Key in the Zmanda Pro configuration.
Specify the name of the bucket where you want to store your backups.
(Optional) Add a folder within the bucket to organize your backups separately.
Click "Test Connection" to verify successful communication with Impossible Cloud.
Save the configuration.
Storj DCS:
Storj DCS provides a unique approach to cloud storage: a decentralized network of independent storage nodes.
Zmanda Pro offers two ways to connect to Storj DCS:
Using the Native Storj API (Recommended):
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "Storj DCS" as the destination type.
Obtain your Storj DCS credentials:
Satellite: Choose a Storj DCS satellite node. The satellite region is usually shown in the login prompt of the Storj website.
API Key: Generate an API key by navigating to "Access" on the left-hand side menu of the Storj DCS web interface and clicking "Create Keys for CLI" on the right.
Password: Set a password for the bucket you'll use.
Bucket: Specify the bucket name where you want to store your backups.
Enter your Storj DCS credentials in the Zmanda Pro configuration.
(Optional) Add a prefix within the bucket to organize your backups. This allows multiple users to store data in the same bucket with distinct prefixes.
Click "Test Connection" to verify successful communication with Storj DCS.
Save the configuration.
Using Storj DCS as a Storage Template:
Zmanda Pro allows you to configure Storj DCS as a storage template. This creates separate storage vaults with system-generated prefixes within a single bucket for each vault using this template. Here's what you need:
Satellite: Choose a Storj DCS satellite node.
API Key: An API key with access permissions to create buckets.
Bucket Name: The base name for the buckets that will be created (Zmanda Pro will append a unique prefix to each).
Password: A password used for all bucket prefixes created from this template.
Using S3-Compatible Storage (Alternative):
While Zmanda Pro offers the option to use Storj DCS via the S3-compatible storage type, the native Storj DCS API method (option 1) is recommended for potentially better compatibility and performance.
Storadera:
There are two ways to connect Zmanda Pro to Storadera:
Using the Dedicated Storadera Option (Recommended):
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "Storadera Cloud Storage" as the destination type.
Obtain your Storadera access credentials:
Navigate to the "Keys" section on the top menu of the Storadera web interface.
Click "Create" to generate a new access key and secret key pair.
Enter your Storadera Access Key ID and Secret Access Key in the Zmanda Pro configuration.
Specify the name of the bucket where you want to store your backups.
(Optional) Add a subdirectory within the bucket to organize your backups separately.
Click "Test Connection" to verify successful communication with Storadera.
Save the configuration.
Using the S3-Compatible Option:
While Zmanda Pro offers the "S3-compatible" storage type, using the dedicated Storadera option is recommended for potentially better compatibility and performance. However, if you prefer the S3-compatible approach, follow these steps:
Follow steps 1-3 from the dedicated Storadera option instructions above.
Choose "S3-compatible" as the destination type.
Enter the hostname of your Storadera Cloud Storage server (refer to Storadera documentation for details).
(Optional) If Storadera uses a custom region, specify it here.
Enter your Storadera Access Key ID and Secret Access Key obtained in step 4 of the dedicated Storadera option.
Follow steps 6-9 from the dedicated Storadera option instructions above.
Digital Ocean Spaces:
Using the Dedicated DigitalOcean Spaces Option (Recommended):
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "DigitalOcean Spaces" as the destination type.
Obtain your DigitalOcean Spaces credentials:
Navigate to the "API" section on the left menu of the DigitalOcean web interface.
Click on "Generate New Key" within the "Space Access Keys" section.
Enter your DigitalOcean Spaces Access Key and Secret Key in the Zmanda Pro configuration.
Specify the name of the bucket where you want to store your backups.
(Optional) Add a subdirectory within the bucket to organize your backups separately.
Click "Test Connection" to verify successful communication with DigitalOcean Spaces.
Save the configuration.
Catalyst Cloud Object Storage:
Catalyst Cloud Object Storage Regions:
New Zealand Hamilton Region
New Zealand Porirua Region
New Zealand Wellington Region
Configuring Catalyst Cloud Object Storage Backup with Zmanda Pro
Using the Dedicated Catalyst Cloud Option (Recommended):
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "Catalyst Cloud Object Storage" as the destination type.
Obtain your Catalyst Cloud credentials:
Navigate to the "API Access" section on the left menu of the Catalyst Cloud web interface.
Click on "Create EC2 Credentials" to generate a new access key and secret key pair.
Enter your Catalyst Cloud Access Key (EC2 Access Key) and Secret Key (EC2 Secret Key) in the Zmanda Pro configuration.
Specify the name of the bucket where you want to store your backups.
(Optional) Add a subdirectory within the bucket to organize your backups separately.
Select the desired region from the available options (New Zealand Hamilton, Porirua, or Wellington).
Click "Test Connection" to verify successful communication with Catalyst Cloud. 1 0. Save the configuration.
OpenStack Swift:
OpenStack offers three Identity API versions for authentication:
v1 (Basic): This is the earliest and simplest method, available from all OpenStack providers.
v2 (Tenants): Introduced isolation between users with the concept of "Tenants."
v3 (Domains and Projects): The latest version adds another layer of isolation with "Domains" and renames "Tenants" to "Projects."
Zmanda Pro automatically detects the API version based on the provided "Auth Endpoint" URL. It's recommended to use the highest supported version (v3) for enhanced security.
Configuration:
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "OpenStack Swift" as the destination type.
Obtain your OpenStack Swift credentials:
Auth Endpoint URL: The URL for the OpenStack authentication server, including protocol (http:// or https://). This URL typically ends in "v1.0," "v2.0," or a similar version indicator.
Username: Your OpenStack account username.
API Key: The API key associated with your user account.
Enter the required credentials in the Zmanda Pro configuration.
Container: Specify the container name where you want to store your backups. Zmanda Pro will create it if it doesn't exist.
(Optional) Subdirectory: Add a subdirectory within the container to organize your backups.
Optional Fields (v2/v3):
Domain Name: (v3 only) Specify your domain name if it differs from the user domain.
Region: (v2/v3) Specify the region to use (e.g., "LON" or "ORD"). Zmanda Pro might automatically select a region if not provided.
Tenant Name/ID: (v2/v3) Enter the name or ID of the tenant/project where your backups will reside.
Tenant Domain: (v3 only) Specify the tenant/project's domain name if it differs from the user domain.
Trust ID: (v3 only) Provide the trust ID if using trust-based authentication.
(Optional) Container Policy: Set a policy for the container creation (if it doesn't exist) to define access permissions.
Click "Test Connection" to verify successful communication with OpenStack Swift.
Save the configuration.
WebDAV:
Log in to the Zmanda Pro tenant admin console.
Navigate to the section for configuring backup destinations.
Choose "WebDAV" as the destination type.
Obtain your WebDAV server credentials:
Hostname: The URL of your WebDAV server, including protocol (http:// or https://) and any custom port number (if applicable).
Username: The username for logging in to your WebDAV server.
Password: The password associated with your WebDAV server username.
Enter the credentials in the Zmanda Pro configuration.
(Optional) Path: Specify a subdirectory path within the WebDAV server where you want to store your backups. This helps organize your backups on the server.
Click "Test Connection" to verify successful communication with the WebDAV server.
Save the configuration.
Security Considerations:
WebDAV authentication typically uses basic username and password credentials. Consider implementing additional security measures on your WebDAV server, such as SSL/TLS encryption for secure data transfer.
Refer to your WebDAV server's documentation for recommended security practices.
Spanned:
File Placement Strategies- Zmanda Pro offers two file placement strategies to determine where new data gets stored within the Spanned pool:
Default (Automatic):
Zmanda Pro intelligently distributes new data across all locations for balanced storage and performance.
It considers factors like free space, keeping drives busy, and minimizing overhead.
Initially, with ample free space everywhere, data is spread evenly across all locations for optimal performance.
As a location fills up, Zmanda Pro prioritizes writing to locations with the most free space to maximize remaining storage.
Cloud storage is generally preferred when spanning between local disks and cloud providers due to difficulty determining cloud storage availability.
You can add new spanned drives anytime to increase capacity.
Overhead: Low (minimal overhead when checking location space)
Static Locations:
This strategy places files in specific locations based on their filename hash, like a unique fingerprint.
Zmanda Pro can instantly locate any file by its name, potentially improving access speed.
Limitations:
Only applicable for entirely new Spanned locations.
Adding or reordering existing storage targets is not recommended.
All targets should have roughly similar free space for optimal performance.
Overhead: None (ideal for performance if restrictions are met)
Using Spanned Storage with Zmanda Pro Server:
You can configure your Zmanda Pro Server to virtually offer data hosted on remote servers (e.g., Amazon S3) using Spanned storage.
Cloud Failover with Spanned Storage:
For optimal performance, set up a Spanned location with local storage initially. When local space is exhausted, Zmanda Pro can automatically expand to cloud storage (requires Default placement strategy).
Important Considerations:
Each underlying storage location (e.g., individual drives) retains its own connection limits. Spanned locations don't have additional limits.
Spanned locations don't actively rebalance data between locations. However, some passive rebalancing occurs during data retention processes and when writing new data.
With the Default strategy, you can manually rebalance storage locations by moving files between them while your Zmanda Pro Server is running.
Rebalancing is not possible with the Static Locations strategy.
Expanding Storage with Spanned Locations:
To increase storage capacity, simply add a new spanned target (storage location).
Example: Adding a New Hard Drive
Imagine your Zmanda Pro Server has almost-full storage on drive "D:". You've attached a new hard drive named "E:". Here's how to expand storage using Spanned locations:
Go to Zmanda Pro Server Settings > Storage Role > Locations.
Under "Choose where data will be stored," you'll see the current storage type and location (e.g., Local Path, D:).
Change the storage type from "Local Path" to "Spanned."
Add two Span Targets:
The existing location (Local Path, D:).
The new hard drive location (Local Path, E:).
Keep the File Placement Strategy as "Default" (if data already exists on drive D:).
Click "Save" and restart the Zmanda Pro Server.
Important Note: Converting from Spanned to a different storage type is complex. If needed, contact Zmanda Pro Support for assistance.
Last updated