-
- Expert
- Posts: 172
- Liked: 20 times
- Joined: Oct 03, 2016 12:41 pm
- Full Name: Robert
- Contact:
3.0 repository questions
Hi,
The new snapshot based retension policy for repositories is good news. Just to clarify - if i create a repository using snapshot based with a retension of 2 years, only 2 years back of data is in the repository, but the hole Exchange mailbox is protected and i will be able to restore any backup data back up until 2 years back?
I guess i can´t convert a existing items based repository to snapshot based?
/Robert
The new snapshot based retension policy for repositories is good news. Just to clarify - if i create a repository using snapshot based with a retension of 2 years, only 2 years back of data is in the repository, but the hole Exchange mailbox is protected and i will be able to restore any backup data back up until 2 years back?
I guess i can´t convert a existing items based repository to snapshot based?
/Robert
-
- Veeam Software
- Posts: 3195
- Liked: 774 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: 3.0 repository questions
Hi Robert,
Yes, that's correct. And once applied, the type of retention cannot be changed in the future.
Here's a good explanation on how different retention types work in v3.
And some details in the documentation as well.
Hope it helps.
Yes, that's correct. And once applied, the type of retention cannot be changed in the future.
Here's a good explanation on how different retention types work in v3.
And some details in the documentation as well.
Hope it helps.
-
- Expert
- Posts: 111
- Liked: 10 times
- Joined: Nov 21, 2017 7:18 am
- Full Name: Peter Helfer
- Contact:
Re: 3.0 repository questions
Is there actually a difference in backup time?
Which method is faster?
Item level or snapshot based?
Which method is faster?
Item level or snapshot based?
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: 3.0 repository questions
Peter,
Theoretically, both methods are equal in time. The only difference should be in the first full. With item level you will take a subset of the data (which is younger than the retention range) and with snapshot you will backup everything.
Theoretically, both methods are equal in time. The only difference should be in the first full. With item level you will take a subset of the data (which is younger than the retention range) and with snapshot you will backup everything.
-
- Expert
- Posts: 111
- Liked: 10 times
- Joined: Nov 21, 2017 7:18 am
- Full Name: Peter Helfer
- Contact:
Re: 3.0 repository questions
Thanks Mike.
Just another Repository question:
Is it recommended to use NTFS or ReFS? What Blocksize in what case?
Does Snapshot feature use ReFS on Server 2016 FastClone as well in VBO Snapshot Backups like in VBR?
Just another Repository question:
Is it recommended to use NTFS or ReFS? What Blocksize in what case?
Does Snapshot feature use ReFS on Server 2016 FastClone as well in VBO Snapshot Backups like in VBR?
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: 3.0 repository questions
Fastclone does not work since we are storing the data in a JetDB and there are no real transforms like in VBR.
Choosing NTFS or ReFS does not matter in this case. Both options are good. I would advise to go for 4k in the case of ReFS because it is not constant sequential data compared to storing VBK files in VBR
Choosing NTFS or ReFS does not matter in this case. Both options are good. I would advise to go for 4k in the case of ReFS because it is not constant sequential data compared to storing VBK files in VBR
-
- Enthusiast
- Posts: 45
- Liked: 6 times
- Joined: Dec 27, 2012 12:25 pm
- Contact:
Re: 3.0 repository questions
The reference links about snapshot retention indicate that retention is based on snapshot date and item date (within the snapshot). Does that mean if you set 1 year retention on a snapshot repository, you will never have email items older than 1 year old in the repository, or am I mis-interpreting this?
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: 3.0 repository questions
Snapshot based retention means that you will have a point in time backup where you will see the mailbox (as an example) exactly as it is at that moment. Item-level means you will see only items where the changed or modified (or created) date are equal or younger than 1 year. Niels explained it in this blog: https://www.veeam.com/blog/new-features ... up-v3.html
If there are still questions, let me know
Mike
If there are still questions, let me know
Mike
-
- Enthusiast
- Posts: 45
- Liked: 6 times
- Joined: Dec 27, 2012 12:25 pm
- Contact:
Re: 3.0 repository questions
Mike,
From Niel's blog about snapshot retention:
From Niel's blog about snapshot retention:
This statement is a bit confusing. Is this supposed to be saying that if your retention is 60 days than any snapshot older than 60 days is removed? Or is it saying that if you have an item within a snapshot that is older than 60 days, that individual item is removed? The former is what I would expect with "snapshot retention", as the later is effectively what item retention does.Retention processing: During clean-up, we will remove all items belonging to snapshots of mailbox/site/folder that are older than the retention period.
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: 3.0 repository questions
This part comes from the snapshot based retention
In that retention, we have point-in-time "images". So every one of these "images" will be removed. Which basically means, that you won't be able to go back to the state of the mailbox/ OneDrive/ whatever anymore. But items that are still in the snapshots who are younger then the retention time (even if the individual age of them is older than 60) won't be removed. As an (hopefully easy) example: If you have contacts in your Outlook who are 3 years old. A snapshot based retention of 60 days. Those contacts are still visible today so as a result, you won't be able to revert to the look of your outlook of 60 days ago, but if you restore from the backup of yesterday, those 3 year old items will still be there.
Hope it makes it clear.
In that retention, we have point-in-time "images". So every one of these "images" will be removed. Which basically means, that you won't be able to go back to the state of the mailbox/ OneDrive/ whatever anymore. But items that are still in the snapshots who are younger then the retention time (even if the individual age of them is older than 60) won't be removed. As an (hopefully easy) example: If you have contacts in your Outlook who are 3 years old. A snapshot based retention of 60 days. Those contacts are still visible today so as a result, you won't be able to revert to the look of your outlook of 60 days ago, but if you restore from the backup of yesterday, those 3 year old items will still be there.
Hope it makes it clear.
-
- Enthusiast
- Posts: 45
- Liked: 6 times
- Joined: Dec 27, 2012 12:25 pm
- Contact:
Re: 3.0 repository questions
Mike,
Thank you for the clarification. I figured the snapshot method didn't consider item age, but rather the age of the snapshot itself.
In your example of a 3 year old Outlook contact with 60 day retention. I would be able to revert the Outlook to it's exact look anywhere from 1 to 59 days ago, correct? In all of those instances. the 3 year old contact will exit in each of those snapshot points.
Thank you for the clarification. I figured the snapshot method didn't consider item age, but rather the age of the snapshot itself.
In your example of a 3 year old Outlook contact with 60 day retention. I would be able to revert the Outlook to it's exact look anywhere from 1 to 59 days ago, correct? In all of those instances. the 3 year old contact will exit in each of those snapshot points.
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: 3.0 repository questions
Correct
-
- Service Provider
- Posts: 45
- Liked: 5 times
- Joined: Nov 08, 2013 2:53 pm
- Full Name: Bert D'hont
- Contact:
Re: 3.0 repository questions
What about needed disk space? Do we need a significant amount of extra disks space for Snapshot based retention in comparison with item based retention?
-
- Veeam Software
- Posts: 3195
- Liked: 774 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: 3.0 repository questions
Hi Bert,
Snapshot-based requires more space, as on the first full backup runs jobs will grab all the available data of the selected type and add changes going further. You can estimate the first full backup size with the Measure-VBOOrganizationFullBackupSize cmdlet.
Snapshot-based requires more space, as on the first full backup runs jobs will grab all the available data of the selected type and add changes going further. You can estimate the first full backup size with the Measure-VBOOrganizationFullBackupSize cmdlet.
Who is online
Users browsing this forum: No registered users and 16 guests