Avamar Client: SQL Backup Label number

Zusammenfassung: This article explains how label number works for Avamar on SQL Backup.

Dieser Artikel gilt für Dieser Artikel gilt nicht für Dieser Artikel ist nicht an ein bestimmtes Produkt gebunden. In diesem Artikel werden nicht alle Produktversionen aufgeführt.
Andere Ressourcen ansehen

Weisungen

  1. Database backups are created by backing up each individual database as a partial backup. Partial means a backup of each database as part of an entire backup. A partial backup is a piece of a backup that does not stand on its own.
    As displayed below, each labelnum represents a partial backup.

          <file internal="false" labelnum="1372" fullname="SQL\SQLDB/db2/i-2.stream0" acnt="/clients/sql.moja.com" saveas="i-1.stream0" />
          <file internal="false" labelnum="1371" fullname="SQL\SQLDB/db2/f-0.stream0" acnt="/clients/sql.moja.com" />
          <file internal="false" labelnum="1370" fullname="SQL\SQLDB/db4/i-2.stream0" acnt="/clients/sql.moja.com" saveas="i-1.stream0" />
          <file internal="false" labelnum="1369" fullname="SQL\SQLDB/db3/i-2.stream0" acnt="/clients/sql.moja.com" saveas="i-1.stream0" />
          <file internal="false" labelnum="1368" fullname="SQL\SQLDB/db4/f-0.stream0" acnt="/clients/sql.moja.com" />
          <file internal="false" labelnum="1367" fullname="SQL\SQLDB/db3/f-0.stream0" acnt="/clients/sql.moja.com" />

    2. Call a Snapview to tie those backups together into a restorable set.
    Essentially, Snapview ties partial backups together into restorable sets.
    Therefore, the backup above becomes only one number in the Avamar Administrator.

    The Snapview process is how Avamar ties partial backups together into restorable sets. After the backup of each database is complete, a final avtar runs that collects the root hashes of the partial backups and ties them together. This process of tying the backups together is a Snapview.
     
    Streams:
    Avatar considers each stream as a partial backup. Because of this, there is one labelnum for each stream.
    Based on the following example, the configuration has five streams. For larger databases, we can see the five streams, so 5 is the label number because each stream is a partial backup.
     
         <flag type="integer" pidnum="3006" value="5" name="max-parallel" />

          <file internal="false" labelnum="259344" fullname="sql\ins\travelee\f-0.stream0" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259343" fullname="sql\ins\travelee\f-0.stream2" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259342" fullname="sql\ins\travelee\f-0.stream1" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259340" fullname="sql\ins\travelee\f-0.stream3" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259341" fullname="sql\ins\travelee\f-0.stream4" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259367" fullname="sql\ins\adminsys\f-0.stream3" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259368" fullname="sql\ins\adminsys\f-0.stream2" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259369" fullname="sql\ins\adminsys\f-0.stream1" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259365" fullname="sql\ins\adminsys\f-0.stream4" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259366" fullname="sql\ins\adminsys\f-0.stream0" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259362" fullname="sql\ins\Core\f-0.stream3" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259364" fullname="sql\ins\Core\f-0.stream4" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259363" fullname="sql\ins\Core\f-0.stream1" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259360" fullname="sql\ins\Core\f-0.stream0" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259361" fullname="sql\ins\Core\f-0.stream2" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259349" fullname="sql\ins\LCS_SQL\f-0.stream4" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259347" fullname="sql\ins\LCS_SQL\f-0.stream1" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259348" fullname="sql\inst\LCS_SQL\f-0.stream0" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259346" fullname="sql\ins\LCS_SQL\f-0.stream3" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />
          <file internal="false" labelnum="259345" fullname="sql\ins\LCS_SQL\f-0.stream2" acnt="/SQLServers/Production/Cluster/sql.labemc.local" />

Betroffene Produkte

Avamar Client

Produkte

Avamar Client
Artikeleigenschaften
Artikelnummer: 000009839
Artikeltyp: How To
Zuletzt geändert: 25 Sep. 2025
Version:  5
Antworten auf Ihre Fragen erhalten Sie von anderen Dell NutzerInnen
Support Services
Prüfen Sie, ob Ihr Gerät durch Support Services abgedeckt ist.