I understand that if I dedupe a filesystem, the deduped data gets written to savvol. If I then delete the deduped filesystem without re-hydrating it, will the deduped data that exists in savvol get deleted as well?
actually, the deduplication engine does not USE the SavVol. It uses a hidden area within the filesystem to copy the candidates and deduplicate/compress them.
What the manual states is :
IF you have checkpoints for this specific filesystem, the deduplication process will copy the changed blocks to the SavVol as it was a user write.
From "Using Celerra Data Deduplication" on "Planning application integration" secction :
Point-in-time views of the file system The deduplication process releases space in the production file system immediately. However, it may cause blocks to be copied to the SnapSure save volume (SavVol) in the process. Deduplicating data associated with a file involves copying the data within the file system so it can be compressed as well as single instanced. Since SnapSure checkpoints copy changed blocks to the SavVol on first write, the blocks that are deduplicated may need to be copied to the SavVol in order to preserve a previous checkpoint point-in-time view of the file system. These blocks are freed when the corresponding checkpoint gets deleted or refreshed and are then available for re-use by other checkpoints. How many blocks will need to be copied to the SavVol during the deduplication process is a function of how full the file system is, the rate of change in it, and so on, and therefore is difficult to predict. By default the system is configured to abort deduplication operations on a file system before it causes the SavVol to extend. This avoids the SavVol expanding due to deduplication activity. If the deduplication process is aborted in this way, an alert is generated that explains what happened. The Celerra administrator can choose to extend the SavVol or simply let the deduplication process execute again on its next scheduled run.
So, to answer your question, if you want to delete a deduped filesystem with checkpoints, you need to delete it's checkpoints first, so you won't have a SavVol for this filesystem when you are deleting it.
Celerra deduplication is transparent for any file-based backup - like the NDMP backup used by Avamar or Data Domain - so it will work the same way as without
PAX-based (tar, dump) NDMP backups, which must reduplicate the files during the backup process, will be slowed when backing up deduplicated files. This will be particularly noticeable for small files.
As result, files are not deduped writen to backup medium (tape).
VBB: Celerra deduplication-enabled file systems can be backed up using Celerra Volume Based Backup (VBB) and restored in full by using the FDR method. However, a single file restore or a file-by-file restore of deduplicated files from VBB backups is not supported and will be rejected by the Celerra.
As result, FS is deduped writen to backup medium (tape).
PAX-based (tar, dump) NDMP backups, which must reduplicate the files during the backup process, will be slowed when backing up deduplicated files. This will be particularly noticeable for small files.
As result, files are not deduped writen to backup medium (tape).
so every time i run NDMP backup, the whole file system gets re-duplicated and dedupe process has to start from scratch ?
gbarretoxx1
2 Intern
•
366 Posts
556
0
Posted July 22nd, 2009 05:00
actually, the deduplication engine does not USE the SavVol.
It uses a hidden area within the filesystem to copy the candidates and deduplicate/compress them.
What the manual states is :
IF you have checkpoints for this specific filesystem, the deduplication process will copy the changed blocks to the SavVol as it was a user write.
From "Using Celerra Data Deduplication" on "Planning application integration" secction :
Point-in-time views of the file system
The deduplication process releases space in the production file system immediately. However, it may cause blocks to be copied to the SnapSure save volume (SavVol) in the process. Deduplicating data associated with a file involves copying the data within the file system so it can be compressed as well as single instanced. Since SnapSure checkpoints copy changed blocks to the SavVol on first write, the blocks that are deduplicated may need to be copied to the SavVol in order to preserve a previous checkpoint point-in-time view of the file system.
These blocks are freed when the corresponding checkpoint gets deleted or refreshed and are then available for re-use by other checkpoints. How many blocks will need to be copied to the SavVol during the deduplication process is a function of how full the file system is, the rate of change in it, and so on, and therefore is difficult to predict. By default the system is configured to abort deduplication operations on a file system before it causes the SavVol to extend. This avoids the SavVol expanding due to deduplication activity. If the deduplication process is aborted in this way, an alert is generated that explains what happened. The Celerra administrator can choose to extend the SavVol or simply let the deduplication process execute again on its next scheduled run.
So, to answer your question, if you want to delete a deduped filesystem with checkpoints, you need to delete it's checkpoints first, so you won't have a SavVol for this filesystem when you are deleting it.
Gustavo Barreto.