BLM Archiver Invoicing (Billing for BLM data)
Summary
The DS-System is the central billing point for backed up data. Invoices are generated by the DS-System for both online data (DS-System) and archived data (BLM). This article provides some more details on the billing for BLM data.
- "Details"
- "BLM Archiver configured WITHOUT back-referencing"
- "BLM Archiver configured WITH back-referencing"
- "Charges occurring for common files"
Details
Billing for BLM data appears as a separate line on each DS-Client's monthly Invoice, which is generated by DS-System (a BLM billing scale must be assigned to the DS-Client). Three Invoice Calculation Methods are available for the BLM data:
Flat fee is by definition, constant, regardless how much data is stored on the BLM Archiver. Protected size is always based on the information supplied from each DS-Client (original backup sizes). The only method that may require further description is the one based on Stored Size. This is because the actual stored size may vary for a BLM Archiver (depending on various configurations).
The main considerations that could affect the Stored Size are the following:
- Number of Library Files (common file elimination)
- Whether BLM is set to perform back-referencing (across different archive packages for the same backup set). This is configured on the BLM Archiver from BLM GUI > Setup > Configuration: General Configuration.
Stored size information is gathered per DS-Client:
- DS-Operator > Right-click a DS-Client > Edit DS-Client > Advanced Tab: Storage History Setting (1 Day | 1 Hour | 30 minutes | 15 minutes | 10 minutes | 5 minutes)
These statistics are viewable from: DS-Operator > Reports > Charts > Storage Trend.
The Storage Trend screen allows you to view the Stored and Protected sizes of data on both DS-System and BLM (See "Viewing the Storage Trend".). These statistics are gathered by DS-System, based on the per DS-Client Storage History Setting. The last entry of the month (usually 23:59:59 on the last day of the month) is used in the Invoices (or the Average or Peak listed, depending on the Billing Settings). If the DS-Client has been deactivated, the last Storage History entry for that DS-Client will be used to generate the 'Final' Invoice.
BLM Archiver configured WITHOUT back-referencing
The following is a very basic example of BLM Archiver storage for a file (File-A). The backup set is configured as follows:
- File-A is part of a regular file system backup set.
- The backup set is configured for a maximum of three (3) generations online.
- File-A changes before each backup session.
The following are performed, in order:
1. Backup 1 creates File-A.1 on DS-System (a Master)
2. BLM Request 1 creates BLM Package 1, then adds File-A.1 (a Master)
3. Backup 2 creates File-A.2 on DS-System (a Delta)
4. BLM Request 2 adds File-A.2 (a Delta) to BLM Package 1
5. Backup 3 creates File-A.3 on DS-System (a Delta)
6. BLM Request 3 closes BLM Package 1, opens BLM Package 2, then adds File-A.3 (a Master) to BLM Package 2
In this scenario, BLM Archiver stores 2 BLM Archiver packages. The first one includes a Master and a Delta generation for File-A. The second package contains another Master generation for File-A (because back-referencing is not enabled).
Protected Size Charges (without back-referencing)
Each generation of a file is charged based on the size of that file/generation on the source machine (before DS-Client processing for delta, compression, and encryption). This charge applies for each package where that file resides.
In this example, the BLM Archiver charge for File-A for a full month (for both packages) will be equal to the size of each generation on the source machine before the actual backup.
- the first generation protected size (File-A.1) is 100 MB
- the second generation protected size (File-A.2) is 101 MB
- the third generation protected size (File-A.3) is 102 MB
2. The BLM Charge for File-A would be for 303 MB, even though the BLM will store less data.
Stored Size Charges (without back-referencing)
In this example, the BLM Archiver charge for File-A for a full month (for both packages) will be equal to the stored size of each generation on the BLM machine after the BLM Archiving session has finished.
- the first generation stored size (File-A.1) is 50 MB
- the second generation stored size is (File-A.2) 25 MB
- the third generation stored size is (File-A.3) 51 MB
2. The BLM Charge for File-A would be for 126MB.
- NOTE: The stored size is going to vary (in part), based on how frequently the BLM Package is closed. Packages are only closed if a BLM Request includes the specification to "Close active package", or if the package is consolidated. If more generations can be stored as Delta generations, the stored size will be reduced. The stored size may also vary based on the BLM request type that triggers the data to move from DS-System to BLM Archiver.
BLM Archiver configured WITH back-referencing
Using the same file from the previous example, the following are performed, in order:
1. Backup 1 creates File-A.1 on DS-System (a Master)
2. BLM Request 1 creates BLM Package 1, then adds File-A.1 (a Master)
3. Backup 2 creates File-A.2 on DS-System (a Delta)
4. BLM Request 2 adds File-A.2 (a Delta) to BLM Package 1.
5. Backup 3 creates File-A.3 on DS-System (a Delta)
6. BLM Request 3 closes BLM Package 1, opens BLM Package 2, then adds File-A.3 (a Delta) to BLM Package 2 with back-referencing.
In this scenario, BLM Archiver stores 2 BLM Archiver packages. The first one includes a Master and a Delta generation for File-A. The second package contains a Delta generation for File-A that references the previous delta generation from the first package (because back-referencing is enabled).
Protected Size Charges (with back-referencing)
Each generation of a file is charged based on the size of that file/generation on the source machine (before DS-Client processing for delta, compression, and encryption). This charge applies for each package where that file resides.
In this example, the BLM Archiver charge for File-A for a full month (for both packages) will be equal to the size of each generation on the source machine before the actual backup.
- the first generation protected size (File-A.1) is 100 MB
- the second generation protected size (File-A.2) is 101 MB
- the third generation protected size (File-A.3) is 102 MB
2. The BLM Charge for File-A would be for 303 MB, even though the BLM will store less data.
- Note: This is essentially the same as Protected Size charges without back referencing, since stored size is not taken into account.
Stored Size Charges (with back-referencing)
In this example, the BLM Archiver charge for File-A for a full month (for both packages) will be equal to the stored size of each generation on the BLM machine after the BLM Archiving session has finished. Stored size is the size of the file/generation on the BLM Storage (after processing for delta, compression, encryption, etc.).
- the first generation stored size (File-A.1) is 50 MB
- the second generation stored size is (File-A.2) 25 MB
- the third generation stored size is (File-A.3) 20 MB
2. The BLM Charge for File-A would be for 95MB.
Charges occurring for common files
BLM Configured without back-referencing
Each BLM package only contains data from one backup set. For each BLM package, a new full instance of the library must be stored. The rest of the same common files in that package will be stored as links to the library file.
- Billing based on protected size: Each common file that is stored (either as a link or as a full instance library file) will be considered for billing at the same size as the file had on the source before backup.
- Billing based on stored size: Common files are billed for the storage taken up by the full instance library file (usually one copy, compressed and encrypted) and all the library link files (usually many very small link files of less than 1KB). Without back-referencing, at least one full instance library file will be saved per BLM package.
BLM Configured with back-referencing
Each BLM package only contains data from one backup set. After the first full instance of the library is stored in a BLM package, subsequent packages point back to that first full instance when using back-referencing.
- Billing based on protected size: Each common file that is stored (either as a link or as a full instance library file) will be considered for billing at the same size as the file had on the source before backup.
- Billing based on stored size: Common files are billed for the storage taken up by the full instance library file (usually one copy, compressed and encrypted) and all the library link files (usually many very small link files of less than 1KB). Because of back-referencing, the total stored size may be reduced even further with less full instance library files stored in the archive packages for that backup set.
See Also
The information provided in this document is provided "AS IS", without warranty of any kind. ASIGRA Inc. (ASIGRA) disclaims all warranties, either express or implied. In no event shall ASIGRA or its business partners be liable for any damages whatsoever, including direct, indirect, incidental, consequential, loss of business profits or special damages, even if ASIGRA or its business partners have been advised of the possibility of such damages. © Asigra Inc. All Rights Reserved. Confidential.
![]() ![]() |