Showing posts with label Data Compression. Show all posts
Showing posts with label Data Compression. Show all posts

Tuesday, February 10, 2015

Hardware Compression vs. Software Compression

Software compression is more well-known among people when compared with hardware compression. The reason is that the majority of people do not have need to apply hardware compression in their daily life. In contrast, software compression does meet their requirements in many aspects. Generally speaking, software compression is cheaper and more easily accessible solution compared with hardware compression. On the other hand, hardware compression demands specialized equipment which is designed to deal with specific workload. Even though hardware compression costs users more, it does have its own advantages over software compression. First of all, the specialized hardware enables hardware compression to be faster than software compression to a great degree. Software compression just requires a general purpose processor in order to perform its job. Secondly, hardware compression will not cause any extra burden to the host processor because its calculations take place within its own hardware. Software compression cannot make it. Under most circumstances, software compression is likely to degrade the performance of the host during heavy use and other operations. If you are compressing a large amount of data while using your computer at the same time, then this may pose a great threat.

There is no doubt that software compression has advantages as well. First, it costs less. Second, software compression offers users a lot of options to choose from. Users are allowed to control the process of how the data is archived, compressed and formatted. In comparison, users are given very few, or no options at all with hardware compression. Users have no say in the process of how the data is compressed before being stored into the media. Everything has been pre-programmed into the hardware by the manufacturer.

In conclusion, software compression is better if you are going to store compressed data for a long time. Hardware compression is usually device specific, which may cause great problems when your device fails without anything can replace it.

Monday, February 9, 2015

Hardware Compression

Generally speaking, the hardware compression is performed on the data path level. As a matter of fact, the hardware compression is only available for the data path which directs data to tape libraries. Under this circumstance, the uncompressed data will be sent from the client computer to the media through the data path. Therefore, the data will be compressed by the tape drive hardware before being written to the media.

There is no doubt that hardware compression is faster than software compression most of the time. The reason is that hardware compression is operated by dedicated circuitry. As a result, the hardware compression is ideal for direct-connect configurations in particular where the subclient and MediaAgent are hosted by the same physical computer. In such configurations, the drives are able to compress the data at the same rate as it is sent by the subclient as there are no network bottlenecks throttling the data transmission to the media drives. On the other hand, the hardware compression can boost the virtual capacity of the tape but also the performance of the data protection thanks to the tape storing more data per unit with higher operation speed. 

However, the problem is that hardware compression is not supported by disk library. It is only applicable for tape libraries.


If the data secured by data protection operations must compete with other data for network bandwidth, then hardware compression may be not that useful. When the network is congested, the tape drives will be starved for data for the data cannot be supplied quickly enough. Under such circumstance, the drives can compress as well, but the drives are likely to stop and restart the media in order to wait for more available data. Therefore, the compression performance may not be very ideal, which may lead to some potential problems.

Sunday, February 8, 2015

Software Compression


Client Compression

The client compression is specified on the subclient level for most agents. Generally speaking, it is available for all storage media. If people adopt this way, then the data on the client computer will be compressed using the compression software. Next, the compressed data will be sent to the MediaAgent that directs it to the storage media in turn. When the client and MediaAgent reside on separate computers and the client has no choice but to send the data through a network, then client compression will be of great use and convenience for it can reduce the network load to a large extent.

Replication Compression

Replicated data can be compressed between the source and the destination computer. If the compression is enabled, then the data will be compressed on the source computer, replicated across the network to the destination computer and uncompressed on the destination computer, which can reduce the workload of the network to a rather large degree. As a matter fact, replication compression is specified on the Replication Set level and applies to all of its Replication Pairs. Therefore, people have the capability to enable or disable client compression between the source and destination machines for a given Replication.

MediaAgent Compression

The MediaAgent compression is specified on the subclient level for most clients. If the data path does not have hardware compression enabled, then people have the capability to enable or disable MediaAgent compression for a given subclient or instance as appropriate. 

Actually, MediaAgent compression is available for all storage media. The data will eb compressed on the MediaAgent using compression software in the MediaAgent. Afterwards, the compressed data will be sent from the MediaAgent to the storage media. When the MediaAgent software resides on a computer more powerful than the client computer, then the MediaAgent Compression can be of great use and convenience.

Saturday, February 7, 2015

Data Compression

Data compression options are provided for data which is secured by data protection operations. Generally speaking, compression is a very useful way to reduce the quantity of data sent to storage, which will double the effective capacity of the media in return (depending on the nature of the data). Moreover, the system will automatically decompress the data and restore it to the original state when the data is later restored or recovered.

The following data compression options are provided: software compression and hardware compression. Software compression offers users to compress data in the Client and MediaAgent while hardware compression for libraries with tape media at the individual data path. In addition, as compressed data often increases in size if it is again subjected to compression, the system will apply one type of compression for a given data protection operation. Therefore, users are able to redefine the compression type at any time without damaging the ability to restore/recover the data.

If the hardware compression is available and applied, then it will have some kind of priority over the other compression selections. Whenever hardware compression has been enabled for a data path, all data conducted through the data path will be compressed in the way of hardware compression automatically. Otherwise, the data will be dealt with in accordance with the software compression selection of each subclient which backs up to the data path. Under such circumstances, people are able to choose from the following options: Client compression, MediaAgent compression, or no compression.


Last but not least, bear in mind that hardware compression is not applicable for disk libraries. As a result, the software compression selection for subclient is adopted by people for data paths which are associated with disk libraries. It is advisable to have a good understanding of such knowledge before compressing data.