Veja o que há na “Zona de Aterrissagem” Exagrid vs. “Zona de Retenção”

Question

Alguém que tenha um Exagrid em seu ambiente me avisa como verificar o que exatamente está residindo na "Zona de Aterrissagem" versus a "Zona de Retenção"? Infelizmente isso não é possível com o painel.

    

Answer 1

Ou o engenheiro estava errado, ou houve uma séria falta de comunicação entre vocês dois. A zona de aterrissagem é (por padrão) metade da capacidade do aparelho. É aí que o backup mais recente é realizado. É deduzido na zona de retenção, portanto, qualquer coisa mais antiga que o backup mais recente deve ser reidratada, portanto, a recuperação levará mais tempo.

Qual problema você está tentando resolver?

Editar - qual é o seu software de backup? Deve ser capaz de dizer a você para qualquer trabalho que foi o backup mais recente. Você geralmente não deveria estar tentando acertar o próprio Exagrid via bash para arquivos de backup, ele deve ser mediado pelo seu software de backup.

    

Answer 2

Eu recebi mais algumas mensagens do Exagrid que explicam o que está acontecendo. Aqui estão eles:

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.