For example, if you have a Virtual Machine that uses 100 GB of storage, then the Recovery Folder should also have 100 GB of free space (the ratio is 1:1 for temporary storage).īefore the data is sent to the Recovery Services Vault (covered in more detail in the next section), its metadata and checksum are collected in the Scratch Space so that the next incremental backups can happen seamlessly.Īccording to the documentation (and the installation wizard), this space is normally 5-10% of the size of the backup. Note: In case of SCDPM and MABS (for local backups), there is another location for online recovery called Recovery Folder Settings which also requires enough free space for the recovery to be succeeded. when you use Azure Backup as your long-term backup location in the case of System Center Data Protection Manager (SC DPM) and the Microsoft Azure Backup Server (MABS) or in general when you use the Azure Backup Direct with the MARS Agent). The Scratch Space is used during online backups (i.e. This "cache location" is also referred to as the "scratch space". The only thing it does say is that "Your cache folder should be 5% of the space required for data storage."įigure 1 Microsoft Azure Recovery Services Agent Cache Location The current Microsoft documentation on installing and registering the Agent does not provide any additional details about this cache location. When you install the Microsoft Azure Recovery Services (MARS) Agent (which is required for backing up Files/Folders or System State only), aside from the installation folder, you will need to provide a 'Cache Location'. That may seem odd, especially if you're familiar with the Azure Site Recovery (ASR) service.īut ever since Microsoft combined the Azure Backup (ABU), and the Azure Site Recovery (ASR) services together under the "Azure Recovery Services" label, these two technologies work as 2 pieces in the same puzzle of "recovery/'. If you are not familiar with other Microsoft Business Continuity and Disaster Recovery (BCDR) technologies, you may not realize that MARS actual stands for "Microsoft Azure Recovery Services". Notice the acronym for the Agent is "MARS". This, very clearly, is the Agent where all the data funnel through. we may refer to specific sections of the documentation at times, but we want to go deeper. And it is not our intention to just re-hash what's already been written/provided. Now, of course, Microsoft has their own official documentation. In this section, we will cover each of the components that make up the Azure Backup service. So, let's jump into by starting with a breakdown of the components that make up the Azure Backup service. two separate backup streams, "in case the first one becomes corrupted"). We frequently hear customers say that they "want a full backup every day/week/month", or even "alternating full backups" (i.e. What motivated us to write this whitepaper, is the fact that many of the customers we speak to, still struggle to understand how Azure Backup works, especially in comparison to what they may traditionally be used to do in their on-premises environments. You may think that backup is dull and boring, but there is nothing boring about the amazing rapid changes and improvements that keep coming to a service that, traditionally, is just "set it and forget it".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |