Highlighted

BE16 Cloud storage - delete expired volumes to save on AWS S3-IA storage costs

As you can see in screen shot below that for AWS S3 Cloud Storage there are "expired" and "active" backups listed. My question is "when it is flagged EXPIRED does Veritas backup delete that file from AWS S3 storage or they are still there?" and if they are still there what is the process to clean up expired files from S3 aws infrequent storage so we do not incur any further unecessary file storage charges from AWS.

veritas-expired.JPG

1 Solution

Accepted Solutions
Accepted Solution!

Re: BE16 Cloud storage - delete expired volumes to save on AWS S3-IA storage costs

Hi @PankajB 

Actually, BE would clear the storage on AWS when Data Lifecycle Management (DLM) deletes the backup images. In the case in the screenshot you provided, it appears that the images are past their expiration date, but BE probably decided not to delete them from storage. This is usually because they are/there are subsequent backup sets, such as incremental backup sets, that depend on these earlier backup sets to able to get a complete restore chain. As long as expired sets have active/non-expired sets that depend on them, the expired sets won’t be removed by BE. This is so that you would be able to do a restore which would need the entire chain.

Another reason where sets may be left around is if that is the latest backup set chain for a given resource. The latest chain is retained by default, even if all its constituent backup sets have expired, so that the resource is restorable. This is a configurable setting.

This article explains how DLM works in BE.

View solution in original post

1 Reply
Accepted Solution!

Re: BE16 Cloud storage - delete expired volumes to save on AWS S3-IA storage costs

Hi @PankajB 

Actually, BE would clear the storage on AWS when Data Lifecycle Management (DLM) deletes the backup images. In the case in the screenshot you provided, it appears that the images are past their expiration date, but BE probably decided not to delete them from storage. This is usually because they are/there are subsequent backup sets, such as incremental backup sets, that depend on these earlier backup sets to able to get a complete restore chain. As long as expired sets have active/non-expired sets that depend on them, the expired sets won’t be removed by BE. This is so that you would be able to do a restore which would need the entire chain.

Another reason where sets may be left around is if that is the latest backup set chain for a given resource. The latest chain is retained by default, even if all its constituent backup sets have expired, so that the resource is restorable. This is a configurable setting.

This article explains how DLM works in BE.

View solution in original post