Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revision Both sides next revision | ||
|
hard-links [2012/05/18 03:06] henri |
hard-links [2012/05/18 03:07] henri |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| The image below shows that each of the backup snapshots within this backup set consume a minimum of 300GB storage. | The image below shows that each of the backup snapshots within this backup set consume a minimum of 300GB storage. | ||
| \\ | \\ | ||
| - | {{:backup_set.jpg?200|}} | + | {{:backup_set.jpg|}} |
| \\ \\ | \\ \\ | ||
| However, if we run the 'du' (disk usage) command on the entire backup set (as shown in this next image) we are able to determine that the physical storage requirements for the entire backup set (all backup snap shots, prior to file system de-duplication or compression) is close to 900GB. It is clear from the screen capture above that each snapshot requires a minimum of 300GB of storage space. Therefore with over 30 snapshots in this backup set, the hard linking between snapshots has saved more than 9,000 GB of storage space. | However, if we run the 'du' (disk usage) command on the entire backup set (as shown in this next image) we are able to determine that the physical storage requirements for the entire backup set (all backup snap shots, prior to file system de-duplication or compression) is close to 900GB. It is clear from the screen capture above that each snapshot requires a minimum of 300GB of storage space. Therefore with over 30 snapshots in this backup set, the hard linking between snapshots has saved more than 9,000 GB of storage space. | ||