Delete all backups of a client

[Joseph_TKLee]

Good afternoon,

I have backed up A server but realized I don't need it.

Is there any command/way to delete all backups of A server?

Thanks,

Joseph

[Marianne]

You can expire backups from the Catalog section of the GUI.

You can use the Verify utility to provide search criteria such as Client name and date range.

You can then select images in search results, right-click, Expire.

See Admin Guide I for details.

[RamNagalla]

yes.. best way would be selecing from the GUI-> catalog secion .. and search the images and right click and expire..

you also can use , commands like bpimagelist ---> to find the images and bpexpdate to expire the images.. 

[Joseph_TKLee]

Thanks guys,

I just worked out using the script below and looks okay.

echo "########################################"
echo "The following backupids will be removed"
echo "########################################"
echo "--------------------------------- $1 ---------------------------------------------"
bpimagelist -hoursago 240 -U -client $1
echo "----------------------------------------------------------------------------------"
for Backup_id in `bpimagelist -hoursago 240 -client $1  | awk '{print $6}'  | grep $1`
do
        bpimage -deletecopy 1 -backupid $Backup_id && echo "$Backup_id deleted";
done
 

I just deleted 6TB backup images but the disk pool doesn't have free up 6TB.

Do you know why??

[RamNagalla]

what is the type of disk ?, 

basic disk?

OST?

pure disk?

[Joseph_TKLee]

Hi Nagalla,

PureDisk

Thanks,

[RamNagalla · Accepted solution]

hi ,

as per my understanding only we get the space imeediatly after deletion of the images if that is a basic disk.

Any advance disk needs some time to clean up the data in the disk..

below tech note explies how PureDiks reclimes the space... after image expiration on Netbackup, you may need to think on manual clean up of pure disk if you need space immedialty

http://www.symantec.com/business/support/index?page=content&id=TECH124914

How NetBackup and PureDisk reclaim space

Reclamation of the redundant storage is driven by the user's configured retention settings in the backup policy. NetBackup's deduplication technologies automatically reclaim storage from the container files by following a specific sequence of transactions. (Once a container file is used, it is managed by the deduplication store and will not be released to the file system.) This sequence is slightly different for the following 3 use cases:

Use case 1: Data protected with a NetBackup client and stored on a Media Server Deduplication Pool (MSDP).

1. Based on the configured retention, NetBackup expires the images in the NetBackup image catalog (image cleanup job) and then creates corresponding expiration transactions in the deduplication transaction queue.
2. Transactions in the queue are processed by the deduplication daemons every 12 hours, 20 minutes past the hour, and the corresponding data pointers are dereferenced from storage.
3. A garbage collection runs weekly to clean up any orphaned data, which can occur in certain edge cases.

Use case 2: Data protected with a NetBackup client and stored on an external PureDisk Storage Pool.

1. Based on the configured retention, NetBackup expires the images in the NetBackup image catalog (image cleanup job). NetBackup also notifies the PureDisk MetaBase (catalog) of the images to be deleted.
2. On a weekly basis the PDDO Data Removal Policy removes the corresponding NetBackup image data from the PureDisk MetaBase engine (catalog) and creates corresponding expiration transactions in the PureDisk deduplication transaction queue. The schedule of the PDDO Data Removal Policy can be changed in the PureDisk WebUI to daily if needed.
3. Transactions in the queue are processed by the Queue Processing Policy, and the corresponding data pointers are dereferenced from storage. The schedule of the Queue Processing is 2 times a day by default; it can be changed from the PureDisk WebUI.
4. On a monthly basis a CR garbage collection policy runs automatically to clean up any orphaned data, which can occur in certain edge cases. If you have very short retention policies (retention of less than 5 days), then it is useful to schedule CR Garbage Collection more frequently (once or twice a week).

Use case 3: Data protected with a PureDisk client and stored on a PureDisk Storage Pool.

1. The data removal policies, which run at a user's scheduled time, automatically dereference the affected files in the MetaBase Engine (catalog) and add the necessary expiration transactions in the Content Router (CR) queue for removal.
2. Transactions in the queue are processed by the Queue Processing Policy, and the corresponding data pointers are dereferenced from storage. The schedule of the Queue Processing is 2 times a day by default; it can be changed from the PureDisk WebUI.
3. On a monthly basis a CR garbage collection policy runs automatically to clean up any orphaned data, which can occur in certain edge cases. If you have very short retention policies (retention of less than 5 days), then it is useful to schedule CR Garbage Collection more frequently (once or twice a week).

[Marianne]

In addition to above excellent process, you may want to download and read through the Dedupe Guide: http://www.symantec.com/docs/DOC5187

Data removal process can be found on p. 224.