01-29-2015 01:11 AM
Good morning,
i am running Backup Exec 2014 SP2 on a freshly installed Windows Server 2008R2 Device with internal Deduplication Storage. Client side deduplication is enabled for the deduplication storage.
All Backup jobs are built from scratch with client side deduplication enabled but all jobs are finishing with exceptions:
A backup job using Backup Exec Deduplication Option completes successfully with the following exception:
Client-side deduplication is enabled for this job, but it could not be used.
Please check this link for additional information:
http://entsupport.symantec.com/umi/V-79-18273.
The remote servers are:
1x Windows Server 2012
2x Windows Server 2008R2
4x Windows Server 2003R2
2x Linux Server
I found these links and followed the suggestions but without success:
http://www.symantec.com/business/support/index?page=content&id=HOWTO99117
http://www.symantec.com/business/support/index?page=content&id=TECH185521
http://www.symantec.com/business/support/index?page=content&id=TECH77683&actp=search&viewlocale=en_US&searchid=1422522071254
Solved! Go to Solution.
01-30-2015 12:03 AM
I do have a dedicated volume for my deduplication storage.
However this post shouldn`t be published so soon because i had to wait until i could restart my BE services (running backups) to check if that helps.
In this time i prepared this post for the case that restarting the services didn`t solve the problem but it did indeed.
So the problem is solved with a simple restart of the BE services.
Although, thank you for your help :)
01-29-2015 08:25 AM
The problem is that your deduplication storage is local storage from the backupserver.
In your first link you find the point I copied. You have to use a disk device and not local storage. because the storage will be accessed directly by the backupagent bypassing the server
A deduplication disk storage device or an OpenStorage device must be used for the backup job.
01-30-2015 12:03 AM
I do have a dedicated volume for my deduplication storage.
However this post shouldn`t be published so soon because i had to wait until i could restart my BE services (running backups) to check if that helps.
In this time i prepared this post for the case that restarting the services didn`t solve the problem but it did indeed.
So the problem is solved with a simple restart of the BE services.
Although, thank you for your help :)
01-30-2015 12:17 AM
Please do not do this again. You have just wasted everybody's time read and thinking about your problem.
01-30-2015 01:22 AM
I did not release the thread, i saved it as a draft and waited. How should i know that the post release itself after some time?