Fork me on GitHub

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
encrypted_backups [2012/04/15 23:08]
henri
encrypted_backups [2012/05/22 23:02]
henri [Mac OS X Specific Information]
Line 1: Line 1:
-===== Encrypted Sparse Images =====+====== Encrypted Sparse Images ​======
 Data can be encrypted on the fly using an encrypted sparse disk image. The advantage of sparse images is that the storage initially required by the image file within the host file system is quite low. The image file then automatically expands in chunks, as files are added to the sparse image file system. This means you can set the disk to have 50GB of free space. Yet, initially the image file may only consume 500MB of space within the host file system. Data can be encrypted on the fly using an encrypted sparse disk image. The advantage of sparse images is that the storage initially required by the image file within the host file system is quite low. The image file then automatically expands in chunks, as files are added to the sparse image file system. This means you can set the disk to have 50GB of free space. Yet, initially the image file may only consume 500MB of space within the host file system.
  
Line 8: Line 8:
 \\  \\ 
  
-===== Mac OS X Specific Information =====+====== Mac OS X Specific Information ​======
  
 \\ \\
Line 26: Line 26:
  
 <​html><​small></​html>  ​ <​html><​small></​html>  ​
-  * **Note :** When creating a backup ​disk image it is advisable to store the image somewhere within the filesystem which will persist after a restart of the system. Typically any items stored within the ''/​tmp/''​ directory will not be there after a reboot of the system. The example above generates the ''​5gig_test.sparsebundle''​ image within the ''/​tmp/''​ directory. This is simply ​an example command, it is recommended that you specify a different path when you create a backup disk image or move it once it out of the the temporary directory ​once it has been generated.+  * **Note :** When creating a disk image for backup or important information storage ​it is advisable to store the image somewhere within the filesystem which will persist after a restart of the system. Typically any items stored within the ''/​tmp/''​ directory will be removed once the system ​has been a rebooted. In some cases files within the ''/​tmp/''​ directory could be removed even between reboots. The example above generates the ''​5gig_test.sparsebundle''​ image within the ''/​tmp/''​ directory. This is an example ​of the command, it is recommended that you specify a different path when you create a backup disk image or at the least move it to a more permanent location within your file system structure ​once it has been generated.
 <​html></​small></​html>​ <​html></​small></​html>​