Hi,
we are running TSM Server and Client version 7.1. Recently I updated our Fileserver from Windows Server 2003 to Server 2012. I had a look at the Windows Server 2012 deduplication feature and found it worth a try, becacuse the evaluation tool said, we could save about 35 % filespace. Usually our daily incremental backup transfers about 50 - 100 GB of Data to the TSM server. I activated the deduplicaion 2 days ago and the incremental backup transfered between 1 - 2 TB the last two days. :confused:
I can not find any information from IBM about how TSM works with Windows Server 2012 deduplication. But in Microsoft TechNet you can find the following information on deduplication which I think is fitting for TSM:
In non-optimized backup and restore, the backup application does not use the Data Deduplication backup and restore API. Instead, the backup application opens the files and copies them without specifying the reparse point flag.
The optimized files are coped to the backup volume as normal files, not as optimized files. The conversion from optimized files to normal files is performed transparently in memory by Data Deduplication when the backup application copies the files. Restoring from such a backup store is a normal file-copy operation.
http://technet.microsoft.com/de-de/l.../hh831600.aspx
Does anyone know why TSM is transferring such a large amount of data after activating deduplication? Is it cause the background job for deduplication in windows makes changes to the files? Will it decrease after the job has finished the first round?
Thank You!
we are running TSM Server and Client version 7.1. Recently I updated our Fileserver from Windows Server 2003 to Server 2012. I had a look at the Windows Server 2012 deduplication feature and found it worth a try, becacuse the evaluation tool said, we could save about 35 % filespace. Usually our daily incremental backup transfers about 50 - 100 GB of Data to the TSM server. I activated the deduplicaion 2 days ago and the incremental backup transfered between 1 - 2 TB the last two days. :confused:
I can not find any information from IBM about how TSM works with Windows Server 2012 deduplication. But in Microsoft TechNet you can find the following information on deduplication which I think is fitting for TSM:
Quote:
In non-optimized backup and restore, the backup application does not use the Data Deduplication backup and restore API. Instead, the backup application opens the files and copies them without specifying the reparse point flag.
The optimized files are coped to the backup volume as normal files, not as optimized files. The conversion from optimized files to normal files is performed transparently in memory by Data Deduplication when the backup application copies the files. Restoring from such a backup store is a normal file-copy operation.
Does anyone know why TSM is transferring such a large amount of data after activating deduplication? Is it cause the background job for deduplication in windows makes changes to the files? Will it decrease after the job has finished the first round?
Thank You!