Restoring a compressed or encrypted backup
Published 06 February 2015
SQL HyperBac is very easy to use; you don't need to make substantial changes to your existing restore jobs to restore compressed or encrypted backup files. Provided the backup file extensions are registered with SQL HyperBac, decompression or decryption processing is applied automatically.
By default, SQL HyperBac automatically recognizes backup files on any path with the following extensions, and applies the processing shown:
Extension (applies to all paths) | Processing applied by SQL HyperBac |
*.hbc | Compression (standard) |
*.hbe | Encryption (AES-256) |
*.hbc2 | Compression (fast) Note that fast compression uses less CPU resource, but also results in larger compressed files than SQL HyperBac's standard or ZIP-compatible compression. If your system is I/O-bound (for example, while writing to disk) "fast" compression may actually take longer than the other compression options. |
*.zip or *.rar | Compression (ZIP-compatible) ZIP-compatible compression creates backup files that you can decompress using many popular 3rd-party tools (for example, WinZip or WinRAR). Note that any tool you use for decompression must support ZIP64. |
For restore jobs, SQL HyperBac will automatically decompress or decrypt the backup data as appropriate.
You can add, modify, and delete extensions and associated processing options using HyperBac Configuration Manager. For example, you might choose to create a new ".bak" extension to use SQL HyperBac with your existing backup jobs. See Working with file paths, extensions, and processing options for further information.
