Skip to content

Managing Restores

Learn how to restore backups through the Velero Dashboard.

Viewing Restores

  1. Select a cluster from the dropdown
  2. Navigate to Restores in the sidebar
  3. View the list of all restore operations

Restore List

The restore list shows:

  • Name: Restore operation name
  • Backup: Source backup name
  • Status: Completed, InProgress, Failed, etc.
  • Warnings/Errors: Number of issues
  • Created: When restore was initiated

Creating a Restore

  1. Navigate to Backups
  2. Click on the backup you want to restore
  3. Click Create Restore button
  4. Configure restore options:
  5. Name: Unique restore name (optional, auto-generated if empty)
  6. Namespace Mappings: Map source to target namespaces
  7. Exclude Resources: Resources to skip during restore
  8. Restore PVs: Whether to restore persistent volumes
  9. Preserve Node Ports: Keep original node port values
  10. Include Cluster Resources: Restore cluster-scoped resources

  11. Click Create to start the restore

Restore Options

Namespace Mapping

Restore to a different namespace:

source-namespace:target-namespace

Example: production:staging

Excluding Resources

Skip specific resource types:

configmaps,secrets

Partial Restore

Use label selectors to restore only specific resources from a backup.

Viewing Restore Details

Click on a restore name to view:

  • Metadata: Creation time, source backup
  • Status: Current phase and completion
  • Resources: What was restored
  • Warnings: Non-critical issues
  • Errors: Critical failures
  • Logs: Restore operation logs

Viewing Restore Logs

  1. Click on a restore
  2. Click View Logs tab
  3. Review the complete restore log

Useful for debugging failed restores or understanding what was restored.

Restore Status

Status Description
New Restore created, not started
InProgress Restore currently running
Completed Restore finished successfully
PartiallyFailed Some resources failed to restore
Failed Restore encountered critical errors

Common Restore Scenarios

Disaster Recovery

Restore entire namespaces after cluster failure:

  1. Create new cluster
  2. Install Velero with same BSL configuration
  3. Restore from backup

Namespace Migration

Move workloads between namespaces:

  1. Create backup of source namespace
  2. Use namespace mapping to restore to target namespace

Selective Restore

Restore specific resources:

  1. Use label selectors to filter resources
  2. Exclude unwanted resource types

Cross-Cluster Migration

Move workloads to different cluster:

  1. Backup from source cluster
  2. Configure same BSL on target cluster
  3. Restore to target cluster

Best Practices

  • Test Regularly: Perform restore drills to ensure backups are valid
  • Dry Run: Test restore configuration before production restores
  • Namespace Isolation: Use namespace mappings to avoid conflicts
  • Review Logs: Always check restore logs for warnings
  • Incremental: Start with small restores before full disaster recovery

Troubleshooting

Restore Stuck in InProgress

  • Check Velero pod logs
  • Verify target cluster has sufficient resources
  • Check if any resources are blocking completion

Resources Not Restored

  • Check if namespace exists
  • Verify permissions
  • Review exclude/include filters
  • Check backup content

PV Restore Issues

  • Verify volume snapshot locations are configured
  • Check storage class compatibility
  • Ensure PVs exist in backup

Next Steps