Common Problems & Solutions
Last updated
Last updated
2023 © Zmanda, A BETSOL Company
Explanation: Zmanda Pro is configured so that all significant operations are handled by the client’s device. If the device is limited in terms of CPU power, memory, network infrastructure, or internet connection speed, this can impede the backup process.
Solutions:
Diagnose Hardware and Network Issues: Assess and rectify any problems with the device or network that might be slowing down the backup.
Evaluate System Load: Verify that no other intensive processes are running simultaneously that might affect the backup operation.
Problem: Network shares are accessible, but backups fail.
Solutions:
Path Verification: Make sure network paths are specified using a UNC path rather than a local drive letter that may not be universally recognized.
Permission Configuration: Check that the backup client has the necessary permissions to access the share. Consider setting up a specific user account for the backup client.
Client Installation Strategy: Install the backup client directly on the device storing the original data for more effective access.
Explanation: The restoration process involves an index that identifies which data chunks are needed. Even though this index is typically small, it can become significantly large in extensive data stores.
Solutions:
Avoid Spooling to Backup Targets: Do not spool data to drives that are also being backed up.
Utilize Permanent Storage Solutions: Avoid using ephemeral storage devices like removable USB drives for critical backups.
Switch Backup Methods: If persistent issues arise, consider adopting the Zmanda Pro Disk Image backup method designed to handle such complexities: Disk Image Walkthrough | Zmanda Documentation
Introduction to VSS: Volume Shadow Copy Service (VSS) is an essential Microsoft technology designed to create consistent, point-in-time backups of disk volumes. It utilizes VSS Writers, which are software components that monitor the snapshot process to ensure files are in a stable state for backup. This system is crucial for backing up application-specific data efficiently.
VSS Limitations and Issues:
Network Limitations: VSS cannot operate over network paths. It requires the backup client to be installed on the device containing the original data.
Interference from Other Software: Other active backup software can disrupt VSS operations. Disabling conflicting software might resolve these issues.
Diagnostic Error Codes: Error codes such as 0xXXXXXXXX can indicate the reasons behind VSS failures. Investigating these codes is critical for resolving VSS issues.
Detailed VSS Diagnostic Steps
Checking VSS Writers:
Open a command prompt with administrative rights.
Execute the command vssadmin list writers to review the status of each VSS Writer, noting any that report errors.
Advanced VSS Diagnostics with VSSTrace: For deeper insights into VSS operations:
Download and extract VSSTrace.
Open an elevated command prompt, navigate to the VSSTrace directory.
Execute .\vsstrace.exe -l 255 +f 0xffff > trace001.log.
Run the backup operation.
Upon failure, stop the trace and review trace001.log for detailed diagnostics.
Persistent 'Running' Jobs: If a job remains in the 'running' state:
Allow Natural Completion: Initially, let the job complete on its own.
Forced Software Update: If persistence continues, force a software update via Connected Devices -> Actions to terminate the job.
Reindex Storage Vault: Post-update, enable advanced options, and reindex the vault to reset job statuses and organize data.
Scenario: Logs indicate discrepancies between indexed and actual stored data chunks.
Solution:
Logs indicating a mismatch between index files and actual data stored can be addressed by:
Navigating to Admin -> Advanced Options.
Selecting the affected user, accessing the Devices tab, and choosing Reindex under Storage Vault options.
Applying retention rules and verifying corrections in the job history.
Error logs such as "<packindex/xxxxxxxx> says <snapshot/yyyyyyyy> depends on missing pack <data/zzzzzzzz>":
Problem: Logs show that certain snapshots depend on missing data packs, rendering them non-restorable.
Solution:
Locate and document the affected data bucket using the Storage Vaults tab under the user’s profile.
Access the storage location, identify, and delete the specified 'packindex' files causing the issue.
Reapply retention rules and verify through logs that the missing data chunks have been indexed or that the corrupted snapshot has been purged.
"Cannot Proceed - Locked by Device"
Issue Identification: Occasionally, a storage vault may be locked by a device, preventing any new write operations.
Unlocking Procedure:
Identify the locking device via user profiles and device IDs.
Ensure no active jobs are using the vault.
Access admin settings to unlock the vault and finalize any pending backup operations.
Solutions:
Ensure Full Extraction: Before installation, make sure the installer files are fully extracted.
Adjust Anti-virus Settings: Set antivirus software to ignore the installation files, which can prevent interruption of the installation process.
Solutions:
Reinstallation of Client Software: A fresh installation can reset configurations and resolve underlying issues.
Software Updates: Regularly update the client software through the admin panel to ensure all devices run the latest version, potentially resolving compatibility or performance issues.