了解 Azure Service Fabric 中的定期备份配置Understanding periodic backup configuration in Azure Service Fabric

为可靠的有状态服务或 Reliable Actors 配置定期备份包括以下步骤:Configuring periodic backup of your Reliable stateful services or Reliable Actors consists of the following steps:

  1. 创建备份策略:在此步骤中,根据需求创建一个或多个备份策略。Creation of backup policies: In this step, one or more backup policies are created depending on requirements.

  2. 启用备份:在此步骤中,将在步骤 1 中创建的备份策略关联到所需的实体,即“应用程序”、“服务”或“分区”。______Enabling backup: In this step, you associate backup policies created in Step 1 to the required entities, Application, Service, or a Partition.

创建备份策略Create Backup Policy

备份策略包括以下配置:A backup policy consists of the following configurations:

  • 在数据丢失时自动还原:指定在分区发生数据丢失事件时是否使用最新的可用备份自动触发还原。Auto restore on data loss: Specifies whether to trigger restore automatically using the latest available backup in case the partition experiences a data loss event.

  • 最大增量备份数:定义在两个完整备份之间可执行的增量备份的最大数目。Max incremental backups: Defines the maximum number of incremental backups to be taken between two full backups. 最大增量备份数指定上限。Max incremental backups specify the upper limit. 在下列条件之一下,可以在完成指定数目的增量备份前执行完整备份A full backup may be taken before specified number of incremental backups are completed in one of the following conditions

    1. 副本在变为主副本后从未执行过完整备份。The replica has never taken a full backup since it has become primary.

    2. 自上次备份以来的一些日志记录已截断。Some of the log records since the last backup has been truncated.

    3. 副本超出了 MaxAccumulatedBackupLogSizeInMB 限制。Replica passed the MaxAccumulatedBackupLogSizeInMB limit.

  • 备份计划:要执行定期备份的时间或频率。Backup schedule: The time or frequency at which to take periodic backups. 可以将备份安排为按指定的时间间隔或者每日/每周在固定的时间进行。One can schedule backups to be recurring at specified interval or at a fixed time daily/ weekly.

    1. 基于频率的备份计划:如果需要按固定时间间隔执行数据备份,应使用此计划类型。Frequency-based backup schedule: This schedule type should be used if the need is to take data backup at fixed intervals. 两个连续备份之间的所需时间间隔是使用 ISO8601 格式定义的。Desired time interval between two consecutive backups is defined using ISO8601 format. 基于频率的备份计划支持的时间间隔分辨率为分钟。Frequency-based backup schedule supports interval resolution to the minute.

      {
          "ScheduleKind": "FrequencyBased",
          "Interval": "PT10M"
      }
      
    2. 基于时间的备份计划:如果需要在每天或每周的特定时间执行数据备份,应使用此计划类型。Time-based backup schedule: This schedule type should be used if the need is to take data backup at specific times of the day or week. 计划频率类型可以是每日或每周。Schedule frequency type can either be daily or weekly.

      1. ** 每日基于时间的备份计划**:如果需要在每天的特定时间执行数据备份,应使用此计划类型。Daily Time-based backup schedule: This schedule type should be used if the need id to take data backup at specific times of the day. 若要指定此计划类型,请将 ScheduleFrequencyType 设置为 Daily,将 RunTimes 以 ISO8601 格式设置为每天中的所需时间的列表,随时间一起指定的日期将被忽略。To specify this, set ScheduleFrequencyType to Daily; and set RunTimes to list of desired time during the day in ISO8601 format, date specified along with time will be ignored. 例如,0001-01-01T18:00:00 表示每天下午 6:00 ,忽略日期部分 0001-01-01For example, 0001-01-01T18:00:00 represents 6:00 PM everyday, ignoring date part 0001-01-01. 下面的示例展示了在每天上午 9:00 和下午 6:00 点触发每日备份的配置。Below example illustrates the configuration to trigger daily backup at 9:00 AM and 6:00 PM everyday.

        {
            "ScheduleKind": "TimeBased",
            "ScheduleFrequencyType": "Daily",
            "RunTimes": [
              "0001-01-01T09:00:00Z",
              "0001-01-01T18:00:00Z"
            ]
        }
        
      2. ** 每周基于时间的备份计划**:如果需要在每天的特定时间执行数据备份,应使用此计划类型。Weekly Time-based backup schedule: This schedule type should be used if the need id to take data backup at specific times of the day. 若要指定此计划类型,请将 ScheduleFrequencyType 设置为 Weekly,将 RunDays 设置为需要触发备份的星期几的列表,将 RunTimes 以 ISO8601 格式设置为每天中的所需时间的列表,随时间一起指定的日期将被忽略。To specify this, set ScheduleFrequencyType to Weekly; set RunDays to list of days in a week when backup needs to be triggered and set RunTimes to list of desired time during the day in ISO8601 format, date specified along with time will be ignored. 要触发定期备份的星期几的列表。List of days of a week when to trigger the periodic backup. 下面的示例展示了从星期一到星期五在上午 9:00 和下午 6:00 点触发每日备份的配置。Below example illustrates the configuration to trigger daily backup at 9:00 AM and 6:00 PM during Monday to Friday.

        {
            "ScheduleKind": "TimeBased",
            "ScheduleFrequencyType": "Weekly",
            "RunDays": [
               "Monday",
               "Tuesday",
               "Wednesday",
               "Thursday",
               "Friday"
            ],
            "RunTimes": [
              "0001-01-01T09:00:00Z",
              "0001-01-01T18:00:00Z"
            ]
        }
        
  • 备份存储:指定要将备份上传到的位置。Backup storage: Specifies the location to upload backups. 存储可以是 Azure Blob 存储或文件共享。Storage can be either Azure blob store or file share.

    1. Azure Blob 存储:需要将生成的备份存储在 Azure 中时,应选择此存储类型。Azure blob store: This storage type should be selected when the need is to store generated backups in Azure. “独立的” 和“基于 Azure 的” 群集都可以使用此存储类型。Both standalone and Azure-based clusters can use this storage type. 描述此存储类型需要提供连接字符串和要将备份上传到的容器的名称。Description for this storage type requires connection string and name of the container where backups need to be uploaded. 如果具有指定名称的容器不可用,则在上传备份期间会创建该容器。If the container with the specified name is not available, then it gets created during upload of a backup.

      {
          "StorageKind": "AzureBlobStore",
          "FriendlyName": "Azure_storagesample",
          "ConnectionString": "<Put your Azure blob store connection string here>",
          "ContainerName": "BackupContainer"
      }
      
    2. 文件共享:需要将数据备份存储在本地时,应当为“独立的”群集选择此存储类型。 File share: This storage type should be selected for standalone clusters when the need is to store data backup on-premises. 描述此存储类型需要提供要将备份上传到的文件共享路径。Description for this storage type requires file share path where backups need to be uploaded. 可以使用以下选项之一配置对文件共享的访问权限Access to the file share can be configured using one of the following options

      1. 集成 Windows 身份验证,这会将对文件共享的访问权限提供给属于 Service Fabric 群集的所有计算机。Integrated Windows Authentication, where the access to file share is provided to all computers belonging to the Service Fabric cluster. 在这种情况下,请设置以下字段来配置基于“文件共享” 的备份存储。In this case, set following fields to configure file-share based backup storage.

        {
            "StorageKind": "FileShare",
            "FriendlyName": "Sample_FileShare",
            "Path": "\\\\StorageServer\\BackupStore"
        }
        
      2. 使用用户名和密码保护文件共享,这会将对文件共享的访问权限提供给特定用户。Protecting file share using user name and password, where the access to file share is provided to specific users. 在指定文件共享存储时还可以指定辅助用户名和辅助密码来提供回退凭据,以防使用主用户名和主密码进行身份验证失败。File share storage specification also provides capability to specify secondary user name and secondary password to provide fall-back credentials in case authentication fails with primary user name and primary password. 在这种情况下,请设置以下字段来配置基于“文件共享” 的备份存储。In this case, set following fields to configure file-share based backup storage.

        {
            "StorageKind": "FileShare",
            "FriendlyName": "Sample_FileShare",
            "Path": "\\\\StorageServer\\BackupStore",
            "PrimaryUserName": "backupaccount",
            "PrimaryPassword": "<Password for backupaccount>",
            "SecondaryUserName": "backupaccount2",
            "SecondaryPassword": "<Password for backupaccount2>"
        }
        

    备注

    请确保存储可靠性满足或高于备份数据的可靠性要求。Ensure that the storage reliability meets or exceeds reliability requirements of backup data.

  • 保留策略:指定要在配置存储中保留备份的策略。Retention Policy: Specifies the policy to retain backups in the configured storage. 只支持基本保留策略。Only Basic Retention Policy is supported.

    1. 基本保留策略:此保留策略允许通过删除不再需要的备份文件来确保最佳存储利用率。Basic Retention Policy: This retention policy allows to ensure optimal storage utilization by removing backup files which are no more required. 可指定 RetentionDuration 来设置需要在存储中保留备份的时间跨度。RetentionDuration can be specified to set the time span for which backups are required to be retained in the storage. MinimumNumberOfBackups 是一个可选参数,可指定该参数以确保无论 RetentionDuration 如何始终保留指定数量的备份。MinimumNumberOfBackups is an optional parameter that can be specified to make sure that the specified number of backups are always retained irrespective of the RetentionDuration. 以下示例说明了要将备份保留 10 天的配置,并且不允许备份数量低于 20____。Below example illustrates the configuration to retain backups for 10 days and does not allow number of backups to go below 20.

      {
          "RetentionPolicyType": "Basic",
          "RetentionDuration" : "P10D",
          "MinimumNumberOfBackups": 20
      }
      

启用定期备份Enable periodic backup

在定义备份策略来满足数据备份要求后,应当将备份策略与“应用程序”、“服务”或“分区”相关联。______After defining backup policy to fulfill data backup requirements, the backup policy should be appropriately associated either with an application, or service, or a partition.

备份策略的分层传播Hierarchical propagation of backup policy

在 Service Fabric 中,应用程序、服务和分区之间的关系是分层的,如应用程序模型中所述。In Service Fabric, relation between application, service, and partitions is hierarchical as explained in Application model. 备份策略可以与层次结构中的“应用程序”、“服务”或“分区”相关联。____Backup policy can be associated either with an application, service, or a partition in the hierarchy. 备份策略将按层次结构传播到下一级别。Backup policy propagates hierarchically to next level. 假设仅创建了一个备份策略并将其与某个“应用程序” 相关联,则所有属于该应用程序的所有“可靠有状态服务”__ 和 Reliable Actors 的有状态分区__ 都将使用该备份策略进行备份。Assuming there is only one backup policy created and associated with an application, all stateful partitions belonging to all Reliable stateful services and Reliable Actors of the application will be backed-up using the backup policy. 或者,如果该备份策略与某个“可靠有状态服务”__ 相关联,则其所有分区都将使用该备份策略进行备份。Or if the backup policy is associated with a Reliable stateful service, all its partitions will be backed-up using the backup policy.

替代备份策略Overriding backup policy

某些情况下,应用程序的大多数服务的数据备份要求使用相同的备份计划,但某些服务除外,这些服务要求数据备份使用频率更高的计划或者要求将备份存放到不同的存储帐户或文件共享。There may be a scenario where data backup with same backup schedule is required for all services of the application except for specific services where the need is to have data backup using higher frequency schedule or taking backup to a different storage account or fileshare. 为应对这样的情况,备份还原服务提供了相关机制来用于在服务和分区作用域内替代传播的策略。To address such scenarios, backup restore service provides facility to override propagated policy at service and partition scope. 当备份策略与“服务”__ 或“分区”__ 相关联时,它将替代所传播的任何备份策略。When the backup policy is associated at service or partition, it overrides propagated backup policy, if any.

示例Example

此示例将设置用于两个应用程序:MyApp_AMyApp_BThis example uses setup with two applications, MyApp_A and MyApp_B. 应用程序 MyApp_A 包含两个可靠有状态服务 SvcA1 & SvcA3 和一个 Reliable Actors 服务 ActorA2Application MyApp_A contains two Reliable Stateful services, SvcA1 & SvcA3, and one Reliable Actor service, ActorA2. SvcA1 包含三个分区,而 ActorA2SvcA3 各包含两个分区。SvcA1 contains three partitions while ActorA2 and SvcA3 contain two partitions each. 应用程序 MyApp_B 包含三个可靠有状态服务 SvcB1SvcB2SvcB3Application MyApp_B contains three Reliable Stateful services, SvcB1, SvcB2, and SvcB3. SvcB1SvcB2 各包含两个分区,而 SvcB3 包含三个分区。SvcB1 and SvcB2 contains two partitions each while SvcB3 contains three partitions.

假设这些应用程序的数据备份要求如下所述Assume that these applications' data backup requirements are as follows

  1. MyApp_AMyApp_A

    1. 为属于应用程序的所有“可靠有状态服务” 和 Reliable Actors 的所有分区创建数据的每日备份。Create daily backup of data for all partitions of all Reliable Stateful services and Reliable Actors belonging to the application. 将备份数据上传到位置 BackupStore1Upload backup data to location BackupStore1.

    2. 其中一个服务 SvcA3 要求每小时进行数据备份。One of the services, SvcA3, requires data backup every hour.

    3. 分区 SvcA1_P2 中的数据大小高于预期值,应当将其备份数据存储到另一个存储位置 BackupStore2Data size in partition SvcA1_P2 is more than expected and its backup data should be stored to different storage location BackupStore2.

  2. MyApp_BMyApp_B

    1. 在每星期日的早上 8:00 为 SvcB1 服务的所有分区创建数据备份。Create backup of data every Sunday at 8:00 AM for all partitions of SvcB1 service. 将备份数据上传到位置 BackupStore1Upload backup data to location BackupStore1.

    2. 在每天的早上 8:00 为分区 SvcB2_P1 创建数据备份。Create backup of data every day at 8:00 AM for partition SvcB2_P1. 将备份数据上传到位置 BackupStore1Upload backup data to location BackupStore1.

为解决这些数据备份要求,将创建备份策略 BP_1 到 BP_5 并启用备份,如下所述。To address these data backup requirements, backup policies BP_1 to BP_5 are created and backup is enabled as follows.

  1. MyApp_AMyApp_A

    1. 创建备份策略 BP_1,使其采用基于频率的备份计划且将频率设置为 24 小时。Create backup policy, BP_1, with frequency-based backup schedule where frequency is set to 24 Hrs. 将备份存储配置为使用存储位置 BackupStore1and backup storage configured to use storage location BackupStore1. 使用启用应用程序备份 API 为应用程序 MyApp_A 启用此策略.Enable this policy for Application MyApp_A using Enable Application Backup API. 此操作为属于应用程序 MyApp_A 的“可靠有状态服务”__ 和 Reliable Actors 的所有分区启用使用备份策略 BP_1 的数据备份。This action enables data backup using backup policy BP_1 for all partitions of Reliable Stateful services and Reliable Actors belonging to application MyApp_A.

    2. 创建备份策略 BP_2,使其采用基于频率的备份计划且将频率设置为 1 小时。Create backup policy, BP_2, with frequency-based backup schedule where frequency is set to 1 Hrs. 将备份存储配置为使用存储位置 BackupStore1and backup storage configured to use storage location BackupStore1. 使用启用服务备份 API 为服务 SvcA3 启用此策略。Enable this policy for service SvcA3 using Enable Service Backup API. 此操作将使用显式启用的备份策略 BP_2 为服务 SvcA3 的所有分区替代传播的策略 BP_1,从而导致使用备份策略 BP_2 为这些分区执行数据备份。This action overrides propagated policy BP_1 by explicitly enabled backup policy BP_2 for all partitions of service SvcA3 leading to data backup using backup policy BP_2 for these partitions.

    3. 创建备份策略 BP_3,使其采用基于频率的备份计划且将频率设置为 24 小时。Create backup policy, BP_3, with frequency-based backup schedule where frequency is set to 24 Hrs. 将备份存储配置为使用存储位置 BackupStore2and backup storage configured to use storage location BackupStore2. 使用启用分区备份 API 为分区 SvcA1_P2 启用此策略。Enable this policy for partition SvcA1_P2 using Enable Partition Backup API. 此操作将使用显式启用的备份策略 BP_3 为分区 SvcA1_P2 替代传播的策略 BP_1This action overrides propagated policy BP_1 by explicitly enabled backup policy BP_3 for partition SvcA1_P2.

  2. MyApp_BMyApp_B

    1. 创建备份策略 BP_4,使其采用基于时间的备份计划,将计划频率类型设置为每周,将运行日设置为星期日,将运行时间设置为早上 8:00。Create backup policy, BP_4, with time-based backup schedule where schedule frequency type is set to weekly, run days is set to Sunday, and run times is set to 8:00 AM. 将备份存储配置为使用存储位置 BackupStore1Backup storage configured to use storage location BackupStore1. 使用启用服务备份 API 为服务 SvcB1 启用此策略。Enable this policy for service SvcB1 using Enable Service Backup API. 此操作为服务 SvcB1 的所有分区启用使用备份策略 BP_4 的数据备份。This action enables data backup using backup policy BP_4 for all partitions of service SvcB1.

    2. 创建备份策略 BP_5,使其采用基于时间的备份计划,将计划频率类型设置为每日,将运行时间设置为早上 8:00。Create backup policy, BP_5, with time-based backup schedule where schedule frequency type is set to daily and run times is set to 8:00 AM. 将备份存储配置为使用存储位置 BackupStore1Backup storage configured to use storage location BackupStore1. 使用启用分区备份 API 为分区 SvcB2_P1 启用此策略。Enable this policy for partition SvcB2_P1 using Enable Partition Backup API. 此操作为分区 SvcB2_P1 启用使用备份策略 BP_5 的数据备份。This action enables data backup using backup policy BP_5 for partition SvcB2_P1.

下图描绘了显式启用的备份策略和传播的备份策略。Following diagram depicts explicitly enabled backup policies and propagated backup policies.

Service Fabric 应用程序层次结构

禁用备份Disable backup

不需要对数据进行备份时,可以禁用备份策略。Backup policies can be disabled when there is no need to backup data. 在“应用程序” 上启用的备份策略只能在同一“应用程序” 上使用禁用应用程序备份 API 进行禁用,在“服务” 上启用的备份策略可以在同一“服务” 上使用禁用服务备份 API 进行禁用,在“分区” 上启用的备份策略可以在同一“分区” 上使用禁用分区备份 API 进行禁用。Backup policy enabled at an application can only be disabled at the same application using Disable Application Backup API, Backup policy enabled at a service can be disabled at the same service using Disable Service Backup API, and Backup policy enabled at a partition can be disabled at the same partition using Disable Partition Backup API.

  • 为“应用程序” 禁用备份策略将停止因为传播到可靠有状态分区或 Reliable Actors 分区的备份策略而发生的所有定期数据备份。Disabling backup policy for an application stops all periodic data backups happening as a result of propagation of the backup policy to Reliable Stateful service partitions or Reliable Actor partitions.

  • 为“服务”__ 禁用备份策略将停止因为传播到“服务”的分区的此备份策略而发生的所有定期数据备份。__Disabling backup policy for a service stops all periodic data backups happening as a result of propagation of this backup policy to the partitions of the service.

  • 为“分区” 禁用备份策略将停止因为分区处的备份策略而发生的所有定期数据备份。Disabling backup policy for a partition stops all periodic data backup happening due to the backup policy at the partition.

  • 禁用实体(应用程序/服务/分区)的备份时,可将 CleanBackup 设置为 true 以删除配置存储中的所有备份。While disabling backup for an entity(application/service/partition), CleanBackup can be set to true to delete all the backups in configured storage.

    {
        "CleanBackup": true 
    }
    

暂停和恢复备份Suspend & resume backup

某些情况下可能需要临时暂停定期数据备份。Certain situation may demand temporary suspension of periodic backup of data. 在这种情况下,可以根据需要在“应用程序”、“服务”或“分区”上使用“暂停备份”API。______In such situation, depending on the requirement, suspend backup API may be used at an Application, Service, or Partition. 定期备份暂停将在应用程序层次结构的子树中从应用暂停的点开始向下传递。Periodic backup suspension is transitive over subtree of the application's hierarchy from the point it is applied.

  • 当在某个“应用程序” 上使用暂停应用程序备份 API 应用暂停时,此应用程序下的所有服务和分区都将暂停定期数据备份。When suspension is applied at an Application using Suspend Application Backup API, then all the services and partitions under this application are suspended for periodic backup of data.

  • 当在某个“服务” 上使用暂停服务备份 API 应用暂停时,此服务下的所有分区都将暂停定期数据备份。When suspension is applied at a Service using Suspend Service Backup API, then all the partitions under this service are suspended for periodic backup of data.

  • 当在某个“分区” 上使用暂停分区备份 API 应用暂停时,此分区将暂停定期数据备份。When suspension is applied at a Partition using Suspend Partition Backup API, then it suspends partitions under this service are suspended for periodic backup of data.

不再需要暂停时,可以使用各自的恢复备份 API 来恢复定期数据备份。Once the need for suspension is over, then the periodic data backup can be restored using respective resume backup API. 必须在暂停定期备份时所在的同一“应用程序”、“服务”或“分区”上进行恢复。______Periodic backup must be resumed at same application, service, or partition where it was suspended.

暂停备份与禁用备份之间的差异Difference between Suspend and Disable backups

当特定的应用程序、服务或分区不再需要备份时,应当禁用备份。Disable backup should be used when backups are no longer required for a particular application, service or partition. 用户可以在将“清理备份”参数设置为 true 的情况下调用“禁用备份”请求,这意味着所有现有备份也将被删除。One can invoke disable backup request along with clean backups parameter to be true which would mean all existing backups are deleted as well. 但是,暂停将用于以下场景:当用户希望暂时关闭备份时,例如,当本地磁盘已满或者上传备份由于已知的网络问题等而失败时。However, suspend is to be used in scenarios where one wants to turn off backups temporarily like when local disk becomes full or uploading backup is failing due to known network issue etc.

只能在先前显式启用备份的级别调用禁用,但是可以在当前直接或通过继承/层次结构启用备份的任何级别应用暂停。While disable can be invoked only at a level which was earlier enabled for backup explicitly however suspension can be applied at any level which is currently enabled for backup either directly or via inheritance/ hierarchy. 例如,如果在某个应用程序级别启用了备份,则用户只能在该应用程序级别调用禁用,但是可以在该应用程序上以及该应用程序下的任何服务或分区上调用暂停。For example, if backup is enabled at an application level, one can invoke disable only at the application level however suspend can be invoked at application, any service or partition under that application.

在数据丢失时自动还原Auto restore on data loss

服务分区可能会由于意外故障而导致数据丢失。The service partition may lose data due to unexpected failures. 例如,分区的三个副本中两个副本(包括主副本)的磁盘数据已损坏或被擦除。For example, the disk for two out of three replicas for a partition (including the primary replica) gets corrupted or wiped.

当 Service Fabric 检测到分区丢失了数据时,它会对分区调用 OnDataLossAsync 接口方法并期望分区采取所需的操作来避免数据丢失。When Service Fabric detects that the partition is in data loss, it invokes OnDataLossAsync interface method on the partition and expects partition to take the required action to come out of data loss. 在这种情况下,如果在分区上生效的备份策略将 AutoRestoreOnDataLoss 标志设置为 true,则将自动触发还原并使用此分区的最新可用备份。In this situation, if the effective backup policy at the partition has AutoRestoreOnDataLoss flag set to true then the restore gets triggered automatically using latest available backup for this partition.

获取备份配置Get backup configuration

有单独的 API 可用来在“应用程序”、“服务”和“分区”作用域内获取备份配置信息。______Separate APIs are made available to get backup configuration information at an application, service, and partition scope. 这些 API 分别是获取应用程序备份配置信息获取服务备份配置信息获取分区备份配置信息Get Application Backup Configuration Info, Get Service Backup Configuration Info, and Get Partition Backup Configuration Info are these APIs respectively. 这些 API 主要返回适用的备份策略、备份策略应用于的作用域以及备份暂停详细信息。Mainly, these APIs return the applicable backup policy, scope at which the backup policy is applied and backup suspension details. 下面是有关这些 API 的返回结果的简要说明。Following is brief description about returned results of these APIs.

  • 应用程序备份配置信息:提供在应用程序上应用的备份策略的详细信息,以及在属于该应用程序的服务和分区上被替代的所有策略。Application backup configuration info: provides the details of backup policy applied at application and all the over-ridden policies at services and partitions belonging to the application. 它还包括应用程序及其服务和分区的暂停信息。It also includes the suspension information for the application and it services, and partitions.

  • 服务备份配置信息:提供在服务上生效的备份策略的详细信息,此策略应用于的作用域,以及其分区上被替代的所有策略。Service backup configuration info: provides the details of effective backup policy at service and the scope at which this policy was applied and all the over-ridden policies at its partitions. 它还包括服务及其分区的暂停信息。It also includes the suspension information for the service and its partitions.

  • 分区备份配置信息:提供在分区上生效的备份策略的详细信息,以及此策略应用于的作用域。Partition backup configuration info: provides the details of effective backup policy at partition and the scope at which this policy was applied. 它还包括分区的暂停信息。It also includes the suspension information for the partitions.

列出可用备份List available backups

可以使用“获取备份列表”API 列出可用备份。Available backups can be listed using Get Backup List API. 此 API 调用的结果包括与备份存储上可用的所有备份相关的备份信息项,备份存储是在适用的备份策略中配置的。Result of API call includes backup info items related to all the backups available at the backup storage, which is configured in the applicable backup policy. 提供了此 API 的不同变体,用以列出属于应用程序、服务或分区的可用备份。Different variants of this API are provided to list available backups belonging to an application, service, or partition. 这些 API 支持获取所有适用的分区的“最新”__ 可用备份,也支持根据“开始日期”和“结束日期”来筛选备份。____These APIs support getting the latest available backup of all applicable partitions, or filtering of backups based on start date and end date.

这些 API 还支持对结果进行分页,当 MaxResults 参数设置为非零正整数时,API 将返回最多 MaxResults 个备份信息项。These APIs also support pagination of the results, when MaxResults parameter is set to non-zero positive integer then the API returns maximum MaxResults backup info items. 如果可用的备份信息项多于 MaxResults 值,则会返回一个继续标记。In case, there are more backup info items available than the MaxResults value, then a continuation token is returned. 可以使用有效的继续标记参数来获取下一组结果。Valid continuation token parameter can be used to get next set of results. 将有效的继续标记值传递给下一次 API 调用时,该 API 将返回下一组结果。When valid continuation token value is passed to next call of the API, the API returns next set of results. 当返回了所有可用结果时,响应中将不包含继续标记。No continuation token is included in the response when all available results are returned.

下面是有关受支持变体的简要信息。Following is the brief information about supported variants.

后续步骤Next steps