Free guides, interview Q&As, and job responsibility breakdowns — curated by industry veterans to help you crack MNC interviews
Data loss can happen because of accidental deletion, hardware failure, ransomware attacks, or application errors. Azure Backup is a native Azure service that protects data by taking regular, secure copies of Virtual Machines, files, folders, and databases. This section introduces Azure Backup, explains why organizations use it, and looks at its key benefits and common real-world use cases.View Backup Items
Definition
Azure Backup is a fully managed, cloud-based backup service offered by Microsoft Azure that protects data by creating secure, application-consistent backup copies of Azure Virtual Machines, files, folders, and databases.
(Azure Backup Microsoft Azure की एक fully managed backup service है, जो Azure Virtual Machines, files, folders और databases का secure backup copy बनाकर data को protect करती है।)
Explanation
Azure Backup eliminates the need to build and maintain a separate on-premises backup infrastructure. It automatically manages the underlying backup storage and scales as the amount of protected data grows.
The backed-up data is stored in a Recovery Services Vault, which keeps multiple recovery points so that a resource can be restored to an earlier, healthy state whenever required.
Azure Backup का उपयोग करने पर organization को अलग से on-premises backup infrastructure बनाने और manage करने की आवश्यकता नहीं होती। यह service backup storage को automatically manage करती है और data बढ़ने पर खुद-ब-खुद scale हो जाती है।
Backup की गई data को Recovery Services Vault में store किया जाता है, जिसमें कई recovery points रखे जाते हैं ताकि जरूरत पड़ने पर resource को किसी पुरानी, सही स्थिति में restore किया जा सके।
Example
ABC Technologies runs several production Virtual Machines that host its billing application. The IT team enables Azure Backup for these VMs so that a daily recovery point is created automatically. When a configuration error corrupts the application one evening, the team restores the VM from the previous day's recovery point within a few minutes.
Azure Backup is mainly used to protect business-critical data from accidental loss, corruption, and cyber-attacks such as ransomware. Without a proper backup strategy, a single deleted VM, corrupted database, or accidentally overwritten file could result in permanent data loss and serious business impact.
Common reasons organizations use Azure Backup include:
Azure Backup का उपयोग मुख्य रूप से business-critical data को accidental loss, corruption और ransomware जैसे cyber-attacks से बचाने के लिए किया जाता है। सही backup strategy के बिना किसी VM, database या file के गलती से delete या corrupt हो जाने पर data permanently खो सकता है, जिससे business को गंभीर नुकसान हो सकता है।
1. Fully Managed Service
Azure Backup is a fully managed PaaS service, so Microsoft handles the underlying backup infrastructure, storage management, and software updates.
Azure Backup एक fully managed service है, जिसमें backup infrastructure, storage management और updates Microsoft द्वारा handle किए जाते हैं।
2. Application-Consistent Backups
Backups taken by Azure Backup are application-consistent, meaning the VM can be restored to a usable and reliable state without manual data repair.
Azure Backup application-consistent backup लेता है, जिससे VM को restore करने के बाद data reliable और usable रहता है।
3. Centralized Management
Backup for multiple resources across different subscriptions can be centrally managed and monitored using the Backup center in the Azure Portal.
Backup center के through अलग-अलग subscriptions में मौजूद कई resources के backups को एक जगह से centrally manage और monitor किया जा सकता है।
4. Secure and Encrypted Storage
Backup data stored in the Recovery Services Vault is encrypted at rest and in transit, helping protect it from unauthorized access.
Recovery Services Vault में store की गई backup data rest और transit दोनों में encrypted रहती है, जिससे unauthorized access से protection मिलता है।
5. Long-Term Retention
Azure Backup supports long-term retention policies, allowing recovery points to be kept for months or years to meet compliance needs.
Azure Backup long-term retention policies को support करता है, जिससे compliance requirements पूरी करने के लिए recovery points को महीनों या सालों तक रखा जा सकता है।
Azure Backup can be used to protect a wide range of workloads, from individual files to full production environments. Understanding common use cases helps in choosing the right backup approach for each workload.
Azure Backup का उपयोग individual files से लेकर पूरे production environment तक, कई तरह के workloads को protect करने के लिए किया जा सकता है। जैसे Azure VMs, specific files/folders, SQL व SAP HANA databases, Azure File Shares और on-premises servers — इन सभी को Azure Backup के माध्यम से secure तरीके से backup किया जा सकता है।
Before any resource can be backed up in Azure, a storage entity called a Recovery Services Vault must exist. This vault acts as the central container that stores backup data and manages the backup policies applied to protected resources. This section explains what the vault is, why it is needed, its key components, and its overall benefits.
Definition
A Recovery Services Vault is an Azure storage entity that stores backup data and recovery points for protected resources such as Virtual Machines, files, and databases.
(Recovery Services Vault एक Azure storage entity है, जिसमें Virtual Machines, files और databases जैसे protected resources का backup data और recovery points store किए जाते हैं।)
Explanation
Every backup configuration in Azure requires a Recovery Services Vault. The vault also stores the backup policies and keeps a history of all backup and restore jobs performed for the resources it protects.
A single vault can be used to protect multiple resources, and organizations often create separate vaults based on region, environment, or department for easier management.
Azure में किसी भी backup configuration के लिए Recovery Services Vault आवश्यक होता है। Vault में backup policies भी store होती हैं और उससे जुड़े सभी backup व restore jobs का history भी रखा जाता है।
एक ही vault से कई resources को protect किया जा सकता है, और organizations अक्सर region, environment या department के आधार पर अलग-अलग vaults बनाती हैं ताकि management आसान रहे।
A Recovery Services Vault is used because Azure Backup requires a dedicated, secure storage location to hold backup data separately from the source resource being protected. Keeping backup data isolated from the original resource means that even if the source VM or resource is deleted, its backup remains safely available in the vault.
Recovery Services Vault इसलिए उपयोग किया जाता है क्योंकि Azure Backup को backup data रखने के लिए एक dedicated और secure storage location चाहिए होती है, जो original resource से अलग हो। इससे यह फायदा होता है कि source VM या resource delete हो जाने पर भी उसका backup vault में सुरक्षित रहता है।
A Recovery Services Vault is made up of several key components that work together to manage the complete backup lifecycle:
Recovery Services Vault कई components से मिलकर बनता है — Backup Items (protect किए जा रहे actual resources), Backup Policies (schedule और retention rules), Recovery Points (अलग-अलग समय पर बने backup copies) और Backup Jobs (backup/restore operations का record)।
Once a resource is configured for backup, its data is transferred to the Recovery Services Vault according to the assigned backup policy. Each successful backup creates a new recovery point inside the vault, and older recovery points are automatically removed once they exceed the configured retention period.
Resource के लिए backup configure होने के बाद उसकी data assigned backup policy के अनुसार Recovery Services Vault में transfer होती है। हर successful backup से vault में एक नया recovery point बनता है, और retention period पूरा होने पर पुराने recovery points automatically हट जाते हैं।
1. Centralized Storage
The vault provides a single, centralized location to store and manage backup data for multiple resources.
Vault कई resources की backup data को store और manage करने के लिए एक centralized location provide करता है।
2. Isolated and Secure
Backup data is stored separately from the source resource, protecting it even if the original resource is lost or deleted.
Backup data source resource से अलग रखी जाती है, जिससे original resource खो जाने पर भी backup सुरक्षित रहता है।
3. Policy-Based Management
Backup policies attached to the vault make it easy to apply consistent schedules and retention rules across multiple resources.
Vault से जुड़ी backup policies के कारण कई resources पर consistent schedule और retention rules आसानी से apply किए जा सकते हैं।
4. Job History and Monitoring
The vault keeps a complete history of backup and restore jobs, making it easy to monitor status and troubleshoot failures.
Vault backup और restore jobs का पूरा history रखता है, जिससे status monitor करना और failures को troubleshoot करना आसान हो जाता है।
Before configuring Azure Backup for any resource, certain prerequisites must be in place. Understanding these requirements in advance helps avoid configuration errors and ensures the backup process completes successfully.
An active Azure Subscription is the first requirement, since all Azure resources, including the Recovery Services Vault and the VM being protected, must belong to a valid subscription.
Azure Backup configure करने के लिए एक active Azure Subscription होना जरूरी है, क्योंकि Recovery Services Vault और protect की जाने वाली VM दोनों किसी valid subscription के अंतर्गत ही होते हैं।
A Resource Group is needed to logically organize the Recovery Services Vault along with the other resources related to the backup configuration. Using a dedicated or existing resource group makes it easier to manage permissions and track costs.
Recovery Services Vault और उससे जुड़े resources को logically organize करने के लिए एक Resource Group आवश्यक होता है। Dedicated resource group रखने से permissions manage करना और costs track करना आसान हो जाता है।
A Recovery Services Vault must be created in the same region as the resource that needs to be backed up, since Azure Backup does not support backing up a resource to a vault located in a different region.
Backup किए जाने वाले resource की region में ही एक Recovery Services Vault होना चाहिए, क्योंकि Azure Backup किसी resource को अलग region के vault में backup करने की अनुमति नहीं देता।
The Azure Virtual Machine being protected must use a supported operating system and be located in a region where Azure Backup is available. Certain VM configurations, such as unsupported disk types, may need additional planning before backup can be enabled.
Protect की जा रही Azure VM का operating system supported होना चाहिए और वह ऐसे region में होनी चाहिए जहाँ Azure Backup available हो। कुछ VM configurations, जैसे unsupported disk types, को backup enable करने से पहले अतिरिक्त planning की आवश्यकता हो सकती है।
The administrator configuring backup must have the required RBAC (Role-Based Access Control) permissions, such as Backup Contributor, on the Recovery Services Vault and the target resource.
Backup configure करने वाले administrator के पास Recovery Services Vault और target resource पर आवश्यक RBAC permissions (जैसे Backup Contributor) होनी चाहिए।
Along with access permissions, a suitable backup policy with an appropriate schedule and retention period should be selected or created before enabling backup. Reviewing these requirements beforehand helps ensure the backup is configured correctly on the first attempt.
Permissions के साथ-साथ, backup enable करने से पहले उचित schedule और retention period वाली एक backup policy भी select या create करनी चाहिए। इन सभी requirements को पहले से review करने से backup पहली बार में ही सही तरीके से configure हो जाता है।
Understanding the architecture of Azure Backup helps in visualizing how data actually moves from a source resource to secure storage in the Recovery Services Vault. This section covers the overall architecture, the backup process, and how the different components work together.
Definition
Azure Backup Architecture refers to the overall design and flow of components — including the source resource, the backup extension, and the Recovery Services Vault — that work together to protect and store data.
(Azure Backup Architecture का मतलब उन components के overall design और flow से है — जैसे source resource, backup extension और Recovery Services Vault — जो मिलकर data को protect और store करते हैं।)
Explanation
The backup process begins when a backup policy triggers a scheduled backup job for the protected resource. Azure Backup uses a lightweight extension or agent on the VM to coordinate an application-consistent snapshot of the data.
This snapshot data is then securely transferred to the Recovery Services Vault, where it is stored as a new recovery point that can later be used for restoration.
Backup process तब शुरू होता है जब assigned backup policy protect किए जा रहे resource के लिए एक scheduled backup job trigger करती है। Azure Backup VM पर मौजूद एक lightweight extension/agent का उपयोग करके data का application-consistent snapshot तैयार करता है।
इसके बाद यह snapshot data securely Recovery Services Vault में transfer होता है और एक नए recovery point के रूप में store हो जाता है, जिसे बाद में restore करने के लिए उपयोग किया जा सकता है।
An Azure VM is linked to a Recovery Services Vault when backup is enabled for it. This link ensures that every scheduled backup job for the VM sends its recovery points to the specific vault that was chosen during configuration.
Backup enable करते समय Azure VM एक specific Recovery Services Vault से link हो जाती है। इस link के कारण VM के लिए चलने वाले हर scheduled backup job के recovery points उसी vault में जाते हैं जो configuration के समय select किया गया था।
Data flow in Azure Backup follows a consistent pattern: the source resource generates data, the backup extension captures a consistent snapshot, and the resulting recovery point is transferred and stored securely in the vault. This flow repeats automatically based on the backup schedule defined in the backup policy.
Azure Backup में data flow एक consistent pattern follow करता है: source resource पर data होता है, backup extension उसका consistent snapshot capture करता है और resulting recovery point को securely vault में transfer व store किया जाता है। यह पूरा flow backup policy में defined schedule के अनुसार automatically repeat होता रहता है।
The Azure Backup architecture relies on a few key components working together — the protected resource, the backup extension or agent, the backup policy, the Recovery Services Vault, and the resulting recovery points. Each of these components plays a specific role in ensuring that data is backed up reliably and can be restored when needed.
Azure Backup architecture कुछ मुख्य components पर निर्भर करता है — protected resource, backup extension/agent, backup policy, Recovery Services Vault और उससे बनने वाले recovery points। इनमें से हर component data को reliably backup करने और जरूरत पड़ने पर restore करने में अपनी भूमिका निभाता है।
Creating a Recovery Services Vault is usually the first configuration step before any resource can be backed up in Azure. This section walks through creating the vault, configuring its basic settings and storage replication, and verifying that it is ready to be used.
To create a vault, the administrator searches for Recovery Services Vaults in the Azure Portal and selects Create. The required Subscription, Resource Group, Vault Name, and Region must then be provided before proceeding.
Vault create करने के लिए administrator Azure Portal में Recovery Services Vaults search करता है और Create select करता है। इसके बाद required Subscription, Resource Group, Vault Name और Region provide करनी होती है।
The basic settings for a vault include its name, the resource group it belongs to, and the Azure region where it will be created. The vault name should be meaningful and follow the organization's naming convention so it is easy to identify later.
Vault की basic settings में उसका name, resource group और वह Azure region शामिल होते हैं जहाँ vault create किया जाएगा। Vault name meaningful होना चाहिए और organization की naming convention को follow करना चाहिए, ताकि बाद में उसे पहचानना आसान रहे।
Storage replication defines how the backup data inside the vault is replicated for durability. Azure Backup typically supports options such as Locally Redundant Storage (LRS) and Geo-Redundant Storage (GRS), and the appropriate option should be selected based on the required level of resilience.
Storage replication यह decide करती है कि vault के अंदर backup data durability के लिए किस तरह replicate होगा। Azure Backup आमतौर पर Locally Redundant Storage (LRS) और Geo-Redundant Storage (GRS) जैसे options support करता है, और required resilience के अनुसार उचित option select करना चाहिए।
| Locally Redundant Storage (LRS) | Geo-Redundant Storage (GRS) |
| Replicates data within a single Azure region | Replicates data to a secondary, distant Azure region |
| Lower cost storage option | Higher cost, but provides regional disaster protection |
| Suitable when regional disaster protection is not required | Suitable for critical workloads needing cross-region protection |
Before finalizing vault creation, the administrator should review all the entered settings, including the subscription, resource group, name, region, and replication option, to confirm they are correct.
Vault creation finalize करने से पहले administrator को subscription, resource group, name, region और replication option जैसी सभी entered settings को review करना चाहिए ताकि सब कुछ सही हो।
Once the vault is created, its deployment status can be verified from the Azure Portal notifications, and the vault should then appear under Recovery Services Vaults in the selected resource group. This confirms that the vault is ready to be used for configuring backup policies and enabling backup for resources.
Vault create होने के बाद उसका deployment status Azure Portal की notifications में verify किया जा सकता है, और वह selected resource group के अंदर Recovery Services Vaults में दिखने लगता है। इससे यह confirm होता है कि vault backup policies configure करने और resources के लिए backup enable करने के लिए तैयार है।
Azure Virtual Machines are among the most commonly backed-up resources in Azure. This section explains what Azure VM Backup is, why it is used, and how to configure and enable it, along with how to monitor the resulting backup job status.
Definition
Azure VM Backup is a feature of Azure Backup that protects Azure Virtual Machines by creating application-consistent recovery points stored in a Recovery Services Vault.
(Azure VM Backup, Azure Backup का एक feature है, जो Azure Virtual Machines के application-consistent recovery points बनाकर उन्हें Recovery Services Vault में store करके protect करता है।)
VM Backup is used to protect against accidental deletion of a VM, corruption caused by faulty updates or misconfiguration, and data loss from security incidents such as ransomware. It allows a VM to be restored to a previous healthy state without requiring the workload to be rebuilt from scratch.
VM Backup का उपयोग VM के accidental deletion, faulty updates या misconfiguration की वजह से data corrupt होने, और ransomware जैसी security incidents से data loss से बचाने के लिए किया जाता है। इससे VM को previous healthy state में restore किया जा सकता है, बिना workload को शुरू से फिर बनाए।
To configure VM Backup, the administrator selects the target Azure Virtual Machine and chooses Backup from its settings. A Recovery Services Vault and a backup policy must then be selected before the backup configuration is applied to the VM.
VM Backup configure करने के लिए administrator target Azure Virtual Machine select करता है और उसकी settings में से Backup choose करता है। इसके बाद VM पर backup configuration apply करने से पहले एक Recovery Services Vault और backup policy select करनी होती है।
Once the vault and policy are selected, enabling backup schedules the VM for the next backup run based on the policy's configured time. An initial or on-demand backup can also be triggered immediately to create the first recovery point without waiting for the scheduled time.
Vault और policy select होने के बाद backup enable करते ही VM policy में configured time के अनुसार अगले backup run के लिए schedule हो जाती है। इसके अलावा पहला recovery point तुरंत बनाने के लिए scheduled time का wait किए बिना initial या on-demand backup भी trigger किया जा सकता है।
Every backup operation for a VM creates a backup job, which shows details such as the job type, start time, duration, and current status — for example, In Progress, Completed, or Failed. Reviewing the backup job status regularly helps confirm that VMs are being protected as expected.
किसी VM के लिए हर backup operation से एक backup job बनती है, जिसमें job type, start time, duration और current status (जैसे In Progress, Completed या Failed) जैसी details दिखती हैं। Backup job status को regularly review करने से यह confirm होता है कि VMs सही तरीके से protect हो रही हैं।
A Backup Policy controls how often backups are taken and how long the resulting recovery points are retained. This section explains what a backup policy is, its schedule and retention settings, and how to create, configure, and apply one to an Azure VM.
Definition
A Backup Policy is a set of rules in Azure Backup that defines when backups are taken (schedule) and how long the resulting recovery points are kept (retention).
(Backup Policy, Azure Backup में rules का एक set है, जो यह define करता है कि backup कब लिया जाएगा (schedule) और उससे बने recovery points को कितने समय तक रखा जाएगा (retention)।)
The backup schedule defines the frequency and time at which backup jobs run automatically, such as once daily at a specific time. Choosing an appropriate schedule, often during off-peak hours, helps minimize any performance impact on the workload.
Backup schedule यह define करता है कि backup jobs कितनी बार और किस समय automatically चलेंगी, जैसे रोज एक निश्चित समय पर। सही schedule चुनना, अक्सर off-peak hours में, workload पर performance impact को कम करने में मदद करता है।
Backup retention determines how long each recovery point is kept before it is automatically deleted by Azure Backup. Retention settings can typically be configured separately for daily, weekly, monthly, and yearly recovery points.
Backup retention यह decide करता है कि हर recovery point Azure Backup द्वारा automatically delete होने से पहले कितने समय तक रखा जाएगा। Retention settings को आमतौर पर daily, weekly, monthly और yearly recovery points के लिए अलग-अलग configure किया जा सकता है।
The retention policy works together with the backup schedule to control the overall lifecycle of recovery points. For example, a policy might keep daily recovery points for 30 days, weekly points for 12 weeks, and yearly points for 5 years to satisfy long-term compliance requirements.
Retention policy, backup schedule के साथ मिलकर recovery points की overall lifecycle को control करती है। उदाहरण के लिए, कोई policy daily recovery points को 30 दिनों तक, weekly points को 12 हफ्तों तक और yearly points को 5 सालों तक रख सकती है, ताकि long-term compliance requirements पूरी हों।
To create a backup policy, the administrator opens Backup Policies inside the Recovery Services Vault, selects Add, and defines the required schedule and retention settings for the workload type, such as Azure VM. The policy is then saved and made available for assignment to one or more resources.
Backup policy create करने के लिए administrator Recovery Services Vault के अंदर Backup Policies open करता है, Add select करता है और workload type (जैसे Azure VM) के लिए required schedule व retention settings define करता है। इसके बाद policy save होकर एक या अधिक resources को assign करने के लिए उपलब्ध हो जाती है।
A backup policy is applied to an Azure VM either while enabling backup for the first time or by changing the policy on an already protected VM. Once applied, all future backup jobs for that VM follow the schedule and retention rules defined in the assigned policy.
Backup policy किसी Azure VM पर या तो पहली बार backup enable करते समय apply की जाती है, या पहले से protected VM की policy बदलकर लगाई जाती है। Policy apply होने के बाद उस VM के सभी future backup jobs assigned policy में defined schedule और retention rules को follow करते हैं।
Taking backups is only useful if the data can be reliably restored when needed. This section covers what data restore means, the different Azure VM restore options available, and when each option is typically used.
Definition
Data Restore is the process of recovering data from a backup recovery point and bringing it back to a usable state, either as a new resource or by replacing the existing one.
(Data Restore एक process है जिसमें backup recovery point से data recover किया जाता है और उसे usable state में वापस लाया जाता है, या तो नए resource के रूप में या मौजूदा resource को replace करके।)
Azure VM Restore allows an administrator to recover a protected VM from any available recovery point in the Recovery Services Vault. Depending on the situation, the restore can bring back the entire VM, only specific disks, or individual files and folders.
Azure VM Restore administrator को Recovery Services Vault में उपलब्ध किसी भी recovery point से protected VM को recover करने की सुविधा देता है। स्थिति के अनुसार restore पूरी VM, केवल specific disks, या individual files और folders को वापस ला सकता है।
A full VM restore recreates the entire Virtual Machine, including its OS disk, data disks, and configuration, from a selected recovery point. This option is typically used when the VM has become unusable, badly corrupted, or was accidentally deleted.
Full VM restore selected recovery point से पूरी Virtual Machine को, उसके OS disk, data disks और configuration सहित फिर से create करता है। यह option आमतौर पर तब उपयोग किया जाता है जब VM unusable हो जाए, बुरी तरह corrupt हो जाए, या गलती से delete हो जाए।
The Restore Disks option recovers only the disks of the VM from a recovery point without recreating the entire VM. This is useful when only specific disk-level data is affected, and the recovered disks can then be attached to a new or existing VM as required.
Restore Disks option recovery point से केवल VM की disks को recover करता है, पूरी VM को दोबारा create किए बिना। यह तब useful है जब सिर्फ specific disk-level data प्रभावित हुआ हो, और recovered disks को जरूरत के अनुसार नई या मौजूदा VM से attach किया जा सकता है।
The Restore Files and Folders option allows recovery of individual files or folders from a recovery point without restoring the entire VM or its disks. This is the most efficient option when only a small amount of data, such as an accidentally deleted document, needs to be recovered.
Restore Files and Folders option पूरी VM या उसकी disks को restore किए बिना, recovery point से individual files या folders को recover करने की सुविधा देता है। जब सिर्फ थोड़ी सी data, जैसे गलती से delete हुई कोई document, recover करनी हो, तो यह सबसे efficient option होता है।
Choosing the right restore option depends on the scope of the data loss and the urgency of recovery. The following table summarizes when each restore option is typically the best choice:
| Restore Option | Typical Use Case |
| Restore Full VM | VM is deleted, unusable, or badly corrupted |
| Restore Disks Only | Only specific disk data is affected; VM itself is fine |
| Restore Files and Folders | A small number of files/folders need recovery |
सही restore option चुनना data loss की scope और recovery की urgency पर निर्भर करता है — पूरी VM खराब होने पर Full VM restore, केवल disk data प्रभावित होने पर Restore Disks, और सिर्फ कुछ files की जरूरत होने पर Restore Files and Folders उपयोग किया जाता है।
Configuring backup is not enough on its own — backup jobs and their status must be regularly monitored to make sure resources remain properly protected. This section covers how to view backup jobs, check their status, review protected items, monitor the vault, and manage retention over time.
The Backup Jobs section inside the Recovery Services Vault lists every backup and restore operation performed for the resources protected by that vault. Each entry shows the job type, the related resource, its start time, and its current status.
Recovery Services Vault के अंदर Backup Jobs section में उस vault से protected सभी resources के लिए किए गए हर backup और restore operation की list दिखती है। हर entry में job type, related resource, start time और current status दिखाया जाता है।
Checking backup status regularly helps confirm whether recent backup jobs completed successfully, are still in progress, or have failed. A failed job should be investigated promptly, since a missed backup could leave a resource without a recent recovery point.
Backup status को regularly check करने से यह पता चलता है कि हाल के backup jobs successfully complete हुए हैं, अभी in progress हैं, या fail हो गए हैं। किसी failed job की जल्दी जांच करनी चाहिए, क्योंकि missed backup की वजह से resource का कोई recent recovery point उपलब्ध नहीं रह सकता।
The Backup Items view lists all the resources currently protected by the vault, along with details such as the backup policy applied and the latest recovery point available for each item. This view is useful for quickly confirming which resources are protected and which still need to be configured.
Backup Items view में vault से protected सभी resources की list दिखती है, साथ ही उन पर लागू backup policy और हर item के latest available recovery point की details भी दिखती हैं। यह view यह जल्दी confirm करने के लिए useful है कि कौन से resources protected हैं और कौन से अभी configure करने बाकी हैं।
The vault itself can be monitored using Azure Monitor and built-in alerting to receive notifications about backup failures, expiring recovery points, or other important events. Setting up alerts helps administrators respond quickly instead of manually checking the vault every day.
Vault को Azure Monitor और built-in alerting का उपयोग करके monitor किया जा सकता है, जिससे backup failures, expiring recovery points या अन्य important events के लिए notifications मिलती हैं। Alerts setup करने से administrator को हर दिन manually vault check करने की बजाय जल्दी response करने में मदद मिलती है।
Ongoing management includes reviewing and adjusting backup policies, updating retention periods as compliance requirements change, and removing protection for resources that are no longer needed. Regularly managing backup and retention settings ensures that storage costs stay under control while critical data remains adequately protected.
Ongoing management में backup policies को review व adjust करना, compliance requirements बदलने पर retention periods update करना और अब जरूरत ना होने वाले resources के लिए protection remove करना शामिल है। Backup और retention settings को regularly manage करने से storage cost control में रहती है और critical data पर्याप्त रूप से protected रहती है।
The following practical labs provide hands-on experience with Azure Backup and Recovery. These exercises help you understand how to create a Recovery Services Vault, back up an Azure VM, and restore it when required.
Objective
To create a Recovery Services Vault in Azure and configure its basic settings so that it is ready to be used for backing up resources.
Steps
Learning Outcome
After completing this lab, you should be able to create a Recovery Services Vault and configure its basic settings for use with Azure Backup.
Objective
To configure and enable backup for an Azure Virtual Machine using a Recovery Services Vault and a backup policy.
Steps
Learning Outcome
After completing this lab, you should be able to configure and enable backup for an Azure VM and verify that a backup job completes successfully.
Objective
To restore an Azure Virtual Machine, or specific data from it, using an available recovery point in the Recovery Services Vault.
Steps
Learning Outcome
After completing this lab, you should be able to restore an Azure VM or its data from a recovery point and verify that the restored resource works correctly.
Following recommended best practices helps ensure that Azure Backup remains reliable, cost-effective, and ready to support recovery whenever it is needed. This section summarizes the key practices administrators should follow.
Azure Backup को reliable और cost-effective बनाए रखने के लिए इन best practices को follow करना चाहिए: हर workload के लिए उचित backup policy और retention period चुनना, backup status को regularly verify करना, समय-समय पर test restore करना, failed jobs के लिए alerts configure करना, और critical workloads को उचित backup frequency के साथ protect करना।
