The biggest update made to Zmanda since its kick-off is the support for Distributed Clusters. This gives users the convenience to link Amanda Enterprise Backup Servers across the globe to one central console. The new update made also offers unprecedented convenience while managing backups of 1000s of machines across continents. At the same time, we also make sure we deliver the same reliable robustness users have come to expect from Zmanda during disaster scenarios. Zmanda’s Backup Engine also outperforms other backup solutions through its native code architectures and offers near-real-time RPO for workloads running on VMWare instances.

This combination of Zmanda's Backup Engine allowing for near-real-time backup clubbed with the convenience of managing backup sets seamlessly across the globe, Zmanda 4.0 delivers the best backup and recovery experience yet.

There are various reasons why Zmanda uses a Star architecture.

Star is the fastest known implementation of a tar archiver.

It includes the first free implementation of POSIX.1-2001 extended tar headers. The POSIX.1-2001 extended tar headers define a new standard way for going beyond the limitations of the historic tar format. They allow (among other things) all UNIX time stamps to be archived withsub-second resolution, files of arbitrary size, filenames without length limitation, and file names that use UNICODE UTF-8 encoding.

Star is built on top of libfind and thus allows you to execute "find" like expressions in create, extract and list mode. This allows to do a lot of interesting things that could not be done if star and find would be called separately.

Star automatically detects swapped archives and transparently reads them the right way, regardless of the endian-ness of the architecture of the system that created the archive and the architecture of the system reading the archive. 

There is no definitive answer to this question. The optimal number of clusters is somehow subjective and depends on the method used for measuring similarities and the parameters used for partitioning.
A simple and popular solution consists of inspecting the dendrogram produced using hierarchical clustering to see if it suggests a particular number of clusters. 

Zmanda (cluster mode enabled) has a configuration endpoint which "knows" all the primary and node endpoints in the cluster. Your application connects to the configuration endpoint. Whenever your application writes to or reads from the cluster's configuration endpoint, Zmanda, behind the scenes, determines which shard the key belongs to and which endpoint in that shard to use. It is all quite transparent to your application.

• It is the World’s leading provider of enterprise open source backup and recovery products. We have a legacy of protecting enterprise data.  

• Zmanda also offers seamless enterprise backups for Hybrid cloud environment. Zmanda ensures that all critical workloads such as servers, databases, application, and VMs across hybrid cloud resources are protected against security breaches and accidental errors.

• Zmanda has cleared Homeland certification for Government use. Coverity, which creates automated source-code analysis tools, announced its first list of open source projects that have been certified as free of security defects and we are humbled to be on the list certified for government use.