Rubrik with Azure: SLA domains and archive to Blob

This simulated lab plays the Rubrik cluster with PowerShell and the CLI. Load your account name and the current key, which is exactly what an archival location stores:

$st = (Get-Content C:\azure-lab\storage.txt)
$key = az storage account keys list --resource-group rg-saat-data --account-name $st --query "[?keyName=='key1'].value" -o tsv

1Work out what an SLA Domain keeps, and where

Save a small helper that counts restore points for an SLA Domain, then run it for Gold:

$f = @'
function Get-SlaPoints {
    param([int]$EveryHours, [int]$KeepHourlyDays, [int]$KeepDailyDays, [int]$KeepMonthly, [int]$LocalDays)
    $hourly = [int](24 / $EveryHours) * $KeepHourlyDays
    [pscustomobject]@{
        RestorePoints   = $hourly + $KeepDailyDays + $KeepMonthly
        OnCluster       = $hourly + [Math]::Min($KeepDailyDays, $LocalDays)
        ArchivedToAzure = [Math]::Max(0, $KeepDailyDays - $LocalDays) + $KeepMonthly
    }
}
'@
Set-Content -Path C:\azure-lab\Get-SlaPoints.ps1 -Value $f
. C:\azure-lab\Get-SlaPoints.ps1
Get-SlaPoints -EveryHours 4 -KeepHourlyDays 3 -KeepDailyDays 30 -KeepMonthly 12 -LocalDays 7

You should see this:

RestorePoints OnCluster ArchivedToAzure
------------- --------- ---------------
           60        25              35

18 four-hourly points plus 7 daily ones stay on the cluster; 23 daily and 12 monthly points live only in Azure. Most restores hit the 25 local points, so a slower Azure path is acceptable for the other 35.

2Create the archive container

Run this:

az storage container create --account-name $st --account-key $key --name rubrik-archive -o none
az storage container show --account-name $st --account-key $key --name rubrik-archive --query "{name:name, publicAccess:properties.publicAccess}" -o table

You should see this:

Name            PublicAccess
--------------  --------------
rubrik-archive

3Archive two “snapshots” with the key, as the cluster does

Make two small stand-in snapshot files and upload them with the account key, in the Cool tier:

Set-Content -Path C:\azure-lab\snap-day08.bin -Value 'archived snapshot, day 8'
Set-Content -Path C:\azure-lab\snap-month01.bin -Value 'archived snapshot, month 1'
az storage blob upload --account-name $st --account-key $key --container-name rubrik-archive --name gold/web01/snap-day08.bin --file C:\azure-lab\snap-day08.bin --tier Cool -o none
az storage blob upload --account-name $st --account-key $key --container-name rubrik-archive --name gold/web01/snap-month01.bin --file C:\azure-lab\snap-month01.bin --tier Cool -o none
az storage blob list --account-name $st --account-key $key --container-name rubrik-archive --query "[].{name:name, tier:properties.blobTier}" -o table

You should see this:

Name                         Tier
---------------------------  ------
gold/web01/snap-day08.bin    Cool
gold/web01/snap-month01.bin  Cool

The names are stand-ins; Rubrik uses its own internal layout and encrypts everything before upload. What matters here is the Azure behaviour: key-based access, tiers and reads.

4Note the archival location settings

These are the fields you’d fill in RSC for this account:

✅ Checkpoint: Gold keeps 60 restore points, 35 of them only in Azure, and two stand-in snapshots sit in rubrik-archive in the Cool tier.