See what's in the Exagrid “Landing Zone” vs. “Retention Zone”Question regarding an NAS server and remote usersBacula Volume Retention and Automatic RecyclingAsus WL-520GC + external HDD via EthernetClarify volume retention for me?Creating a scalable back-up cluster with one interface and retentionHow to query the dedupe ratios for Exagrid shares?ZyXEL NSA310S - most recent ownCloud version possible to runWhere is my VHD being used in Azure VM?Changing Azure Backup Retention policy not reducing Azure storage used?Can you apply a retention policy to users within a group on O365?
Do I have a twin with permutated remainders?
Why do I get two different answers for this counting problem?
Alternative to sending password over mail?
What is going on with Captain Marvel's blood colour?
How to draw the figure with four pentagons?
Has there ever been an airliner design involving reducing generator load by installing solar panels?
Is it unprofessional to ask if a job posting on GlassDoor is real?
Doing something right before you need it - expression for this?
In a spin, are both wings stalled?
How can I tell someone that I want to be his or her friend?
How can saying a song's name be a copyright violation?
What is the intuition behind short exact sequences of groups; in particular, what is the intuition behind group extensions?
Forgetting the musical notes while performing in concert
Where does SFDX store details about scratch orgs?
Why does Kotter return in Welcome Back Kotter?
How much of data wrangling is a data scientist's job?
Can a virus destroy the BIOS of a modern computer?
What is a clear way to write a bar that has an extra beat?
Infinite Abelian subgroup of infinite non Abelian group example
Theorems that impeded progress
Did Shadowfax go to Valinor?
Is it possible to create light that imparts a greater proportion of its energy as momentum rather than heat?
AES: Why is it a good practice to use only the first 16bytes of a hash for encryption?
SSH "lag" in LAN on some machines, mixed distros
See what's in the Exagrid “Landing Zone” vs. “Retention Zone”
Question regarding an NAS server and remote usersBacula Volume Retention and Automatic RecyclingAsus WL-520GC + external HDD via EthernetClarify volume retention for me?Creating a scalable back-up cluster with one interface and retentionHow to query the dedupe ratios for Exagrid shares?ZyXEL NSA310S - most recent ownCloud version possible to runWhere is my VHD being used in Azure VM?Changing Azure Backup Retention policy not reducing Azure storage used?Can you apply a retention policy to users within a group on O365?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
Can anyone that has an Exagrid in their environment let me know how to check what exactly is residing on the "Landing Zone" vs. the "Retention Zone"? Unfortunately this is not possible with the dashboard.
backup storage network-attached-storage exagrid
asked Oct 20 '16 at 20:08
Paul MasekPaul Masek
3172515
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
Can anyone that has an Exagrid in their environment let me know how to check what exactly is residing on the "Landing Zone" vs. the "Retention Zone"? Unfortunately this is not possible with the dashboard.
backup storage network-attached-storage exagrid
asked Oct 20 '16 at 20:08
Paul MasekPaul Masek
3172515
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
Can anyone that has an Exagrid in their environment let me know how to check what exactly is residing on the "Landing Zone" vs. the "Retention Zone"? Unfortunately this is not possible with the dashboard.
backup storage network-attached-storage exagrid
asked Oct 20 '16 at 20:08
Paul MasekPaul Masek
3172515
Can anyone that has an Exagrid in their environment let me know how to check what exactly is residing on the "Landing Zone" vs. the "Retention Zone"? Unfortunately this is not possible with the dashboard.
backup storage network-attached-storage exagrid
backup storage network-attached-storage exagrid
asked Oct 20 '16 at 20:08
Paul MasekPaul Masek
3172515
asked Oct 20 '16 at 20:08
Paul MasekPaul Masek
3172515
edited Oct 24 '16 at 13:13
Paul Masek
asked Oct 20 '16 at 20:08
Paul MasekPaul Masek
3172515
asked Oct 20 '16 at 20:08
Paul MasekPaul Masek
3172515
asked Oct 20 '16 at 20:08
Paul MasekPaul Masek
3172515
3172515
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Either the engineer was wrong, or there was a serious miscommunication between you two. The landing zone is (by default) half of the appliance capacity. That's where the most recent backup is held. It's deduped into the retention zone, so anything older than the most recent backup has to be rehydrated, thus retrieval will take longer.
What problem are you trying to solve?
Edit - what's your backup software? It should be able to tell you for any given job what the most recent backup was. You're not generally supposed to be trying to hit the Exagrid itself via bash for backup files, it should be mediated by your backup software.
answered Oct 20 '16 at 21:10
mfinnimfinni
33.1k34380
The problem I'm trying to solve is that I want my most recent backup chain (incrementals plus corresponding full) to reside in the "Landing Zone", which is advertised as undeduplicated right on their website. In order to verify that this is happening I wanted to view it in the filesystem, as well as view where the Retention Zone files are. I only used bash to view the files, not to manually script out the backup process. We use Veeam.
– Paul Masek
Oct 21 '16 at 13:41
1
OK, so you want it to work the way it's supposed to work. If you don't believe them, then test it yourself. Do a restore of something big from the most recent backup. So a restore of the same thing from before that. Compare the execution times of the restores. Hopefully you're not bottlenecked somewhere besides the Exagrid on your data path. Veeam can help show that.
– mfinni
Oct 23 '16 at 23:32
add a comment |
I received a couple more messages back from Exagrid that explain what is going on. Here they are:
Backups land on the landing space. From there they are processed (compressed and deduped) into the retention space. They remain in the landing space for as long as we can keep them (ie., the space isn’t needed to land more backups.) So, they will actually reside on disk in two different places. One is fully hydrated in the landing space and one is all chopped up in blocks in the retention space. The retention space version is only what is necessary to rehydrate at a later time if need be. The landing space version can and will be flushed from disk if it is the oldest data and more space is needed to ingest more backups, perform restores or provide copies of the data.
The actual technical details are all part of our patented algorithms.
In a nutshell, the backup lands on the landing space. The specific type of backup (determined by the application used) is detected. The processing breaks the backups into chunks. Based on whether or not there is previous data and how well that previous data is matched, the chunks will be retained or tossed out. The matching requires that the backup data is uncompressed and unencrypted. This is standard across all the backup applications. There are some exceptions where this requirement is relaxed. Those are detailed in the online documents (Help->Online Library.)
The retained chunks are all located in the retention space. The retention space data is kept for as long you specify according to the retention policies set in to the backup applications.
The original backups are all retained in the landing space. Again, the landing space is nothing more than a big caching mechanism. All data here is kept for as long as possible. It will eventually be filled to capacity but is marked 100% available because all data is subject to be flushed from the landing space as space to ingest more backups is needed.
answered Oct 21 '16 at 14:02
Paul MasekPaul Masek
3172515
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f810331%2fsee-whats-in-the-exagrid-landing-zone-vs-retention-zone%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Either the engineer was wrong, or there was a serious miscommunication between you two. The landing zone is (by default) half of the appliance capacity. That's where the most recent backup is held. It's deduped into the retention zone, so anything older than the most recent backup has to be rehydrated, thus retrieval will take longer.
What problem are you trying to solve?
Edit - what's your backup software? It should be able to tell you for any given job what the most recent backup was. You're not generally supposed to be trying to hit the Exagrid itself via bash for backup files, it should be mediated by your backup software.
answered Oct 20 '16 at 21:10
mfinnimfinni
33.1k34380
The problem I'm trying to solve is that I want my most recent backup chain (incrementals plus corresponding full) to reside in the "Landing Zone", which is advertised as undeduplicated right on their website. In order to verify that this is happening I wanted to view it in the filesystem, as well as view where the Retention Zone files are. I only used bash to view the files, not to manually script out the backup process. We use Veeam.
– Paul Masek
Oct 21 '16 at 13:41
1
OK, so you want it to work the way it's supposed to work. If you don't believe them, then test it yourself. Do a restore of something big from the most recent backup. So a restore of the same thing from before that. Compare the execution times of the restores. Hopefully you're not bottlenecked somewhere besides the Exagrid on your data path. Veeam can help show that.
– mfinni
Oct 23 '16 at 23:32
add a comment |
Either the engineer was wrong, or there was a serious miscommunication between you two. The landing zone is (by default) half of the appliance capacity. That's where the most recent backup is held. It's deduped into the retention zone, so anything older than the most recent backup has to be rehydrated, thus retrieval will take longer.
What problem are you trying to solve?
Edit - what's your backup software? It should be able to tell you for any given job what the most recent backup was. You're not generally supposed to be trying to hit the Exagrid itself via bash for backup files, it should be mediated by your backup software.
answered Oct 20 '16 at 21:10
mfinnimfinni
33.1k34380
The problem I'm trying to solve is that I want my most recent backup chain (incrementals plus corresponding full) to reside in the "Landing Zone", which is advertised as undeduplicated right on their website. In order to verify that this is happening I wanted to view it in the filesystem, as well as view where the Retention Zone files are. I only used bash to view the files, not to manually script out the backup process. We use Veeam.
– Paul Masek
Oct 21 '16 at 13:41
1
OK, so you want it to work the way it's supposed to work. If you don't believe them, then test it yourself. Do a restore of something big from the most recent backup. So a restore of the same thing from before that. Compare the execution times of the restores. Hopefully you're not bottlenecked somewhere besides the Exagrid on your data path. Veeam can help show that.
– mfinni
Oct 23 '16 at 23:32
add a comment |
Either the engineer was wrong, or there was a serious miscommunication between you two. The landing zone is (by default) half of the appliance capacity. That's where the most recent backup is held. It's deduped into the retention zone, so anything older than the most recent backup has to be rehydrated, thus retrieval will take longer.
What problem are you trying to solve?
Edit - what's your backup software? It should be able to tell you for any given job what the most recent backup was. You're not generally supposed to be trying to hit the Exagrid itself via bash for backup files, it should be mediated by your backup software.
answered Oct 20 '16 at 21:10
mfinnimfinni
33.1k34380
Either the engineer was wrong, or there was a serious miscommunication between you two. The landing zone is (by default) half of the appliance capacity. That's where the most recent backup is held. It's deduped into the retention zone, so anything older than the most recent backup has to be rehydrated, thus retrieval will take longer.
What problem are you trying to solve?
Edit - what's your backup software? It should be able to tell you for any given job what the most recent backup was. You're not generally supposed to be trying to hit the Exagrid itself via bash for backup files, it should be mediated by your backup software.
answered Oct 20 '16 at 21:10
mfinnimfinni
33.1k34380
answered Oct 20 '16 at 21:10
mfinnimfinni
33.1k34380
answered Oct 20 '16 at 21:10
mfinnimfinni
33.1k34380
answered Oct 20 '16 at 21:10
mfinnimfinni
33.1k34380
33.1k34380
The problem I'm trying to solve is that I want my most recent backup chain (incrementals plus corresponding full) to reside in the "Landing Zone", which is advertised as undeduplicated right on their website. In order to verify that this is happening I wanted to view it in the filesystem, as well as view where the Retention Zone files are. I only used bash to view the files, not to manually script out the backup process. We use Veeam.
– Paul Masek
Oct 21 '16 at 13:41
1
OK, so you want it to work the way it's supposed to work. If you don't believe them, then test it yourself. Do a restore of something big from the most recent backup. So a restore of the same thing from before that. Compare the execution times of the restores. Hopefully you're not bottlenecked somewhere besides the Exagrid on your data path. Veeam can help show that.
– mfinni
Oct 23 '16 at 23:32
add a comment |
The problem I'm trying to solve is that I want my most recent backup chain (incrementals plus corresponding full) to reside in the "Landing Zone", which is advertised as undeduplicated right on their website. In order to verify that this is happening I wanted to view it in the filesystem, as well as view where the Retention Zone files are. I only used bash to view the files, not to manually script out the backup process. We use Veeam.
– Paul Masek
Oct 21 '16 at 13:41
1
OK, so you want it to work the way it's supposed to work. If you don't believe them, then test it yourself. Do a restore of something big from the most recent backup. So a restore of the same thing from before that. Compare the execution times of the restores. Hopefully you're not bottlenecked somewhere besides the Exagrid on your data path. Veeam can help show that.
– mfinni
Oct 23 '16 at 23:32
The problem I'm trying to solve is that I want my most recent backup chain (incrementals plus corresponding full) to reside in the "Landing Zone", which is advertised as undeduplicated right on their website. In order to verify that this is happening I wanted to view it in the filesystem, as well as view where the Retention Zone files are. I only used bash to view the files, not to manually script out the backup process. We use Veeam.
– Paul Masek
Oct 21 '16 at 13:41
The problem I'm trying to solve is that I want my most recent backup chain (incrementals plus corresponding full) to reside in the "Landing Zone", which is advertised as undeduplicated right on their website. In order to verify that this is happening I wanted to view it in the filesystem, as well as view where the Retention Zone files are. I only used bash to view the files, not to manually script out the backup process. We use Veeam.
– Paul Masek
Oct 21 '16 at 13:41
1
1
OK, so you want it to work the way it's supposed to work. If you don't believe them, then test it yourself. Do a restore of something big from the most recent backup. So a restore of the same thing from before that. Compare the execution times of the restores. Hopefully you're not bottlenecked somewhere besides the Exagrid on your data path. Veeam can help show that.
– mfinni
Oct 23 '16 at 23:32
OK, so you want it to work the way it's supposed to work. If you don't believe them, then test it yourself. Do a restore of something big from the most recent backup. So a restore of the same thing from before that. Compare the execution times of the restores. Hopefully you're not bottlenecked somewhere besides the Exagrid on your data path. Veeam can help show that.
– mfinni
Oct 23 '16 at 23:32
add a comment |
I received a couple more messages back from Exagrid that explain what is going on. Here they are:
Backups land on the landing space. From there they are processed (compressed and deduped) into the retention space. They remain in the landing space for as long as we can keep them (ie., the space isn’t needed to land more backups.) So, they will actually reside on disk in two different places. One is fully hydrated in the landing space and one is all chopped up in blocks in the retention space. The retention space version is only what is necessary to rehydrate at a later time if need be. The landing space version can and will be flushed from disk if it is the oldest data and more space is needed to ingest more backups, perform restores or provide copies of the data.
The actual technical details are all part of our patented algorithms.
In a nutshell, the backup lands on the landing space. The specific type of backup (determined by the application used) is detected. The processing breaks the backups into chunks. Based on whether or not there is previous data and how well that previous data is matched, the chunks will be retained or tossed out. The matching requires that the backup data is uncompressed and unencrypted. This is standard across all the backup applications. There are some exceptions where this requirement is relaxed. Those are detailed in the online documents (Help->Online Library.)
The retained chunks are all located in the retention space. The retention space data is kept for as long you specify according to the retention policies set in to the backup applications.
The original backups are all retained in the landing space. Again, the landing space is nothing more than a big caching mechanism. All data here is kept for as long as possible. It will eventually be filled to capacity but is marked 100% available because all data is subject to be flushed from the landing space as space to ingest more backups is needed.
answered Oct 21 '16 at 14:02
Paul MasekPaul Masek
3172515
add a comment |
I received a couple more messages back from Exagrid that explain what is going on. Here they are:
Backups land on the landing space. From there they are processed (compressed and deduped) into the retention space. They remain in the landing space for as long as we can keep them (ie., the space isn’t needed to land more backups.) So, they will actually reside on disk in two different places. One is fully hydrated in the landing space and one is all chopped up in blocks in the retention space. The retention space version is only what is necessary to rehydrate at a later time if need be. The landing space version can and will be flushed from disk if it is the oldest data and more space is needed to ingest more backups, perform restores or provide copies of the data.
The actual technical details are all part of our patented algorithms.
In a nutshell, the backup lands on the landing space. The specific type of backup (determined by the application used) is detected. The processing breaks the backups into chunks. Based on whether or not there is previous data and how well that previous data is matched, the chunks will be retained or tossed out. The matching requires that the backup data is uncompressed and unencrypted. This is standard across all the backup applications. There are some exceptions where this requirement is relaxed. Those are detailed in the online documents (Help->Online Library.)
The retained chunks are all located in the retention space. The retention space data is kept for as long you specify according to the retention policies set in to the backup applications.
The original backups are all retained in the landing space. Again, the landing space is nothing more than a big caching mechanism. All data here is kept for as long as possible. It will eventually be filled to capacity but is marked 100% available because all data is subject to be flushed from the landing space as space to ingest more backups is needed.
answered Oct 21 '16 at 14:02
Paul MasekPaul Masek
3172515
add a comment |
I received a couple more messages back from Exagrid that explain what is going on. Here they are:
Backups land on the landing space. From there they are processed (compressed and deduped) into the retention space. They remain in the landing space for as long as we can keep them (ie., the space isn’t needed to land more backups.) So, they will actually reside on disk in two different places. One is fully hydrated in the landing space and one is all chopped up in blocks in the retention space. The retention space version is only what is necessary to rehydrate at a later time if need be. The landing space version can and will be flushed from disk if it is the oldest data and more space is needed to ingest more backups, perform restores or provide copies of the data.
The actual technical details are all part of our patented algorithms.
In a nutshell, the backup lands on the landing space. The specific type of backup (determined by the application used) is detected. The processing breaks the backups into chunks. Based on whether or not there is previous data and how well that previous data is matched, the chunks will be retained or tossed out. The matching requires that the backup data is uncompressed and unencrypted. This is standard across all the backup applications. There are some exceptions where this requirement is relaxed. Those are detailed in the online documents (Help->Online Library.)
The retained chunks are all located in the retention space. The retention space data is kept for as long you specify according to the retention policies set in to the backup applications.
The original backups are all retained in the landing space. Again, the landing space is nothing more than a big caching mechanism. All data here is kept for as long as possible. It will eventually be filled to capacity but is marked 100% available because all data is subject to be flushed from the landing space as space to ingest more backups is needed.
answered Oct 21 '16 at 14:02
Paul MasekPaul Masek
3172515
I received a couple more messages back from Exagrid that explain what is going on. Here they are:
Backups land on the landing space. From there they are processed (compressed and deduped) into the retention space. They remain in the landing space for as long as we can keep them (ie., the space isn’t needed to land more backups.) So, they will actually reside on disk in two different places. One is fully hydrated in the landing space and one is all chopped up in blocks in the retention space. The retention space version is only what is necessary to rehydrate at a later time if need be. The landing space version can and will be flushed from disk if it is the oldest data and more space is needed to ingest more backups, perform restores or provide copies of the data.
The actual technical details are all part of our patented algorithms.
In a nutshell, the backup lands on the landing space. The specific type of backup (determined by the application used) is detected. The processing breaks the backups into chunks. Based on whether or not there is previous data and how well that previous data is matched, the chunks will be retained or tossed out. The matching requires that the backup data is uncompressed and unencrypted. This is standard across all the backup applications. There are some exceptions where this requirement is relaxed. Those are detailed in the online documents (Help->Online Library.)
The retained chunks are all located in the retention space. The retention space data is kept for as long you specify according to the retention policies set in to the backup applications.
The original backups are all retained in the landing space. Again, the landing space is nothing more than a big caching mechanism. All data here is kept for as long as possible. It will eventually be filled to capacity but is marked 100% available because all data is subject to be flushed from the landing space as space to ingest more backups is needed.
answered Oct 21 '16 at 14:02
Paul MasekPaul Masek
3172515
answered Oct 21 '16 at 14:02
Paul MasekPaul Masek
3172515
answered Oct 21 '16 at 14:02
Paul MasekPaul Masek
3172515
answered Oct 21 '16 at 14:02
Paul MasekPaul Masek
3172515
3172515
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f810331%2fsee-whats-in-the-exagrid-landing-zone-vs-retention-zone%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
