12-11-2014 04:18 AM
Hi All,
We have had two appliances with 2.5.0.3 and it was working well. Now to fix some issues like slow hydration and dehydration we were asked by Symantec to upgrade to 2.6.0.2 after which we had nighmares where almost all backups started failing with 13 and 24 and 6. It was later found that there is an issue with new features enabled..
Now to resolve that we were asked to upgrade to 2.6.0.3. Since then we have noticed that the MSDP pool is consuming disk space more that it is supposed to do ... Mostly SQL backups are going to this appliance.. In the activity monitor we see good dedupe rate anywhere from 85 to 90... while on the CLISH reports->deduplication it shows merely 76%
Moreover the dehydration with this code is very slow. We tested with same data set on two appliances ... another one with 7.5.0.6 and it have double performance while vaulting ..... !!
Mster server is at same version and is on a windows 2008 r2 cluster ...
any thoughts or simillar experiences....
12-11-2014 08:35 AM
Do you have a support case regarding the performance difference between the two versions? Please make sure your case is reflecting that performance change or open a new case dedicated to that issue so it gets examined separately.
Your dedupe at a job level is not going to be the same at an appliance level, which is what you are looking at with that report. What was that report showing before the upgrade?
02-02-2015 07:38 AM
This is still going on with backline....
02-26-2015 02:32 AM
No concrete solution given by Symantec on this. Eventually we were able to balance the backup to another appliance and now the case is closed.