Running out of disk space

Join our new BDRSuite Community Forum and connect with fellow members for better collaboration and support!

Ask Your Question

We are currently running out of disk space on the Backup locations. 1) I understand that it depends on the amount of data we are backing up, but is there a way to determine how much compressed and de-dup space is actually being used by a VM? It seems that the amount of Repository disk space being used is always increasing, even though the VMs themselves are not getting larrger at the same rate. 2) Do you have a utility or a way to verify that there aren't "lost blocks"? For instance, I deleted a backup job that, according to the console, was taking over 1TB of space. After I deleted that job, I only saw about 400GB of disk space returned. I don't know for certain the size of the repository folder before I deleted it. Any help or suggestions are appreciated. Thanks for your time!

edit retag flag offensive close merge delete

asked 2016-01-18 16:12:04 -0500

bboyer
1 ●2 ●2 ●2

4 replies

Re: Running out of disk space

by mathivanan

Hi,

Thanks for writing to Vembu Technologies.

1.Please be informed, as per the current design of Vembu BDR Suite products, it is not possible to check the exact compression and dedupe ratio from user interface. We are already having this feature in our road map and it will be available in anyone of the upcoming release.

Also, please note that, by default you will get around 40 - 60 % storage reduction (including compression and de-duplication). As you already know, this ratio may vary depends on the source data.

The reason for the storage growth may be due to the retention and additional full backup configurations. If you would like to keep last 90 days of restore points or would like to keep multiple full backup data, that backup job may require more storage then the source data. Hence check the retention and additional full backup policies.

2.The data size shown in the web console is the uncompressed size where as the actual compressed size would be shown in the backup storage location. For the deleted backup job, after storage reduction, it consumed 400 GB in the storage location.

In the backup server web console, we have an option called "Reports -> Backup verification report" which is used to verify the status of a backup job on a regular basis. Enabling this option, will automatically boot the backed up machine and take a screen shot.

Hope the above is clear.

edit flag offensive delete

answered 2016-01-19 00:31:29 -0500

mathivanan
1

updated 2016-01-19 00:58:01 -0500

nagarajan
341 ●4 ●7

Re: Running out of disk space

by clunsford

Was checking Community for anything on Dedupe, and saw that there was a plan to add dedupe statistics, it's been three years since this post, and still no deduplication status to view in the BDR web client.

edit flag offensive delete

answered 2019-05-02 08:17:03 -0500

clunsford
1

Re: Running out of disk space

by Nivas

As of now, you cannot check the storage reduction rate of the backup data from the UI of Vembu BDR Server. However, you can use the web services API to check the storage reduction rate. I will update the details of web services API in this thread shortly.

From our upcoming release, you can check the storage reduction rate in the UI of Vembu BDR Server.

edit flag offensive delete

answered 2019-05-04 13:07:55 -0500

Nivas
321 ●2 ●3

Re: Running out of disk space

by Nivas

As we mentioned earlier, you can get the compressed size of backup jobs using 'LISTRECOVERYJOBS' API request where 'USED_SIZE' refers to the used size of the particular backup.

Refer the Vembu's API documentation for more details.