Hi,
In my primary job I use a volume without deduplication from windows and the type of backup is forever forward incremental.
When I configure a (Secundary Target) to store on another volume and activate GFS to store the weekly and monthly ones does this mean that the type of backup in (Secundary Target) is a simple incremental?
If the answer is: yes it is a simple incremental. Then I can enable windows deduplication.
If the answer is: it is not an incremental forever like the first one, I will have problems with space consumption.
I was reading the subject Forever Forward Incremental and says that if the forever forward incremental backup chain resides on a deduplicating storage appliance, Veeam Backup & Replication does not reuse empty data blocks of the full backup file. Instead, Veeam Backup & Replication appends data from the first incremental backup file in the chain to the full backup file. As a result, the backup chain may consume more * disk space on the appliance *.
Thanks.
-
- Expert
- Posts: 131
- Liked: 4 times
- Joined: Mar 15, 2020 3:56 pm
- Full Name: Sandro da Silva Alves
- Contact:
-
- Product Manager
- Posts: 14846
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Incremental forward forward on the secundary target
Hello,
But using windows deduplication works in all modes. Whether Windows deduplication is useful, that's another story (dedupe ratio is low without full backups).
I'm not sure what repository you are really using: if windows, then I recommend REFS without Windows deduplication. No need to think about other options.
Best regards,
Hannes
when you activate GFS, then there will be full backups (weekly, monthly, whatever you configure). That's the opposite of forever forward incremental.a simple incremental?
But using windows deduplication works in all modes. Whether Windows deduplication is useful, that's another story (dedupe ratio is low without full backups).
please note that forever forward incremental is not supported for most deduplication appliances (especially HPE StoreOnce and EMC DataDomain). So you have no choice anyways on these boxes.I was reading the subject Forever Forward Incremental and says that if the forever forward incremental backup chain resides on a deduplicating storage appliance,
I'm not sure what repository you are really using: if windows, then I recommend REFS without Windows deduplication. No need to think about other options.
Best regards,
Hannes
-
- Expert
- Posts: 131
- Liked: 4 times
- Joined: Mar 15, 2020 3:56 pm
- Full Name: Sandro da Silva Alves
- Contact:
Re: Incremental forward forward on the secundary target
Hi,
I'm using a Windows volume on ReFS.
I want to use Windows deduplication on this secondary volume where I will store the weekly and monthly backups.
You confirmed to me that when I activate GFS it automatically means simple backup on my secondary.
The documentation mentions a problem with deduplication with backup forever, so I understand that I can use and evaluate whether it will be useful or not.
Whether it will be useful or not we only know in practice!
Thanks.
I'm using a Windows volume on ReFS.
I want to use Windows deduplication on this secondary volume where I will store the weekly and monthly backups.
You confirmed to me that when I activate GFS it automatically means simple backup on my secondary.
The documentation mentions a problem with deduplication with backup forever, so I understand that I can use and evaluate whether it will be useful or not.
Whether it will be useful or not we only know in practice!
Thanks.
-
- Product Manager
- Posts: 14846
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Incremental forward forward on the secundary target
that is possible with the reg key that was discussed in the forum thread you also answered veeam-backup-replication-f2/refs-3-0-an ... 56658.htmlI want to use Windows deduplication on this secondary volume where I will store the weekly and monthly backups.
The documentation is talking about something different. Inline deduplication appliances work different than post-deduplication technology like Windows deduplication.
Who is online
Users browsing this forum: iDeNt_5, jim3cantos, ottl05, RobTurk, sivein, StephanG, tobiaso and 144 guests