Hi,
I am trying to get my head around a submitted problem where we witness a with a very bad dedup ratio (2:1) with Backup Copy Job.
Here is a little background.
Model is a 4700. Veeam is 9.5U4b
Backup works great! ratio is good goes easily to over 4.
No GFS is used, Jobs follow the best practices (except a few with over 14 retention points – *sight*, no supported either –
No StoreOnce licence is available, CIFS is used as a repository
The repository serves a Veeam Cloud Connect – I know this is NOT supported scenario (*re-sight*)
Repository is set to decompress
We know compress files, video, music aren’t good candidates … but for over 100 TB. It is hard to believe it is the reason.
Your inputs are welcome to see it clearer.
Oli
-
- Service Provider
- Posts: 129
- Liked: 27 times
- Joined: Apr 01, 2016 5:36 pm
- Full Name: Olivier
- Contact:
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: HPE StoreOnce - Backup Copy Job & bad dedup ratio.
Hi, Olivier. Honestly, this question is best directed to HPE support, as we cannot comment on why some 3rd party storage does not dedupe well. I expect HPE support should be able to analyze their internal device metrics and provide you the explanation of why they cannot dedupe the incoming content. Thanks!
-
- Service Provider
- Posts: 129
- Liked: 27 times
- Joined: Apr 01, 2016 5:36 pm
- Full Name: Olivier
- Contact:
Re: HPE StoreOnce - Backup Copy Job & bad dedup ratio.
Hey Gostev,
It is part of the plan, but there are so many clever people here. I had to ask their share of experience
Thanks for your time.
Have a good week-end,
Oli
It is part of the plan, but there are so many clever people here. I had to ask their share of experience
Thanks for your time.
Have a good week-end,
Oli
Who is online
Users browsing this forum: Bing [Bot], Semrush [Bot] and 76 guests