Purging Old Data

[Shestakov]

Well yes, if you want to have a lot of historical data for 7 hosts, 36 datastores and 157 VMs 10GB is not enough.
However, shrinking to 5 months can be enough for a while. Thanks!

[Hovi]

Hello,

I have the similar problem.

On version 8.0.0.1669 there is a "Full database" alert active, DB has about 9,5 GBs. I tried to set data retention period to 6 month, but I am stil able to see older data and stats and of course there was no effect on DB size.

Could you please advice - retention is set two days ago.



Thanks

Petr

[Vitaliy S.]

How many objects (VMs/hosts/datastores) do you monitor with your installation?

[Hovi]

Infrastructure is vSphere 5.5
8 hosts
about 160 VMs
14 datastores
DB overgrows after about 8 months (installed 10/2014)

[Shestakov]

Have you increased a number of monitored objects(datastores, VMs, Hosts) since 8 months ago?
Also, note that the task to clean database by retention executes once a day in Veeam One Monitor, once a week in Veeam One Reporter.
Thanks!

[Hovi]

As I checked, there are 3 new datastores and about 20 new VMs in last months.

New setting has been applied two days ago, Reporter is not used by the customer.

I made another DB backup and try to decrease retention to 2 months to be sure.

Thanks.

[Shestakov]

Since the number of objects is constantly changing you can`t predict the exact number of months your DB can handle.
Another easy way to cope with small database is switching to the Advanced scalability mode. Rarer renewal intervals, but more historical data is to be stored.
Thanks!

[Hovi]

Hello again,

thanks for the tip - I did not know about the parameters coming with Advanced scalability mode.

It looks there is something wrong with my installation - with 2 months retention period set, I am still available to see data from the begining and DB says there is about 400 MB free space according SQL Management studio.

Do you have any idea how can I fix this state, please?

[Shestakov]

Hello Petr,
I would suggest contacting our support team for the logs investigation.
Once you do, please post your support case number for the case monitoring purposes. Thanks!

[Hovi]

Hello,

problem seems to be solved. The problem was in SQL Express installation - after last update there was two instances - 2008 and 2012. After cleanup the old version everything goes OK - with 4 months data retention period there is DB about 8 GBs.

Thnaks for your hints!

[Shestakov]

Thanks for updating Petr!
Have you figured it out with Veeam support? If yes, please provide the case number, so I can get details.
Thanks!

[EBoucq]

Hi,

My SQL database reached the max of 10 GB (SQL Express) so I ran VeealOneSettings.exe to decrease the retention period to 6 months.
What's the next step to really see the size of the .mdf decrease ?

Thank you.

Regards,
Eric

[Shestakov]

Hi Eric,
Note that task to clean database by retention executes once a day in Veeam One Monitor, once a week in Veeam One Reporter. When did you change the retention?
Thanks!

[EBoucq]

Hi Nikita,

Thanks for your reply.
I changed the setting this morning. That explains why I didn't see any improvement yet
So I guess I have nothing else to do but wait.
Eric.

[Shestakov]

Correct.
Let me know if you have any results in a week.
I would also suggest to review the topic for the relevant information. Thanks!

[EBoucq]

At the same time, I tried to remove a Veeam server from the backup infrastructure view in the Data Protection View but it says 'deleting' and it's been showing that info for 3 hours.
could this be related to the fact the database is full ?

Thanks.
Eric

[Shestakov]

Full database should not interrupt with VBR servers removal.
Try to refresh/restart Veeam One monitor.

[EBoucq]

Hi,

After 24 hours, the database is still 10 GB and it still says deleting in the Data Protection View tab where I tried to remove a Veeam B&R server....

[Shestakov]

Hmm.. That is an unexpected behavior.
Please contact Veeam technical support for the detailed investigation.
Thanks!

[BSalyer]

I currently have VeeamOne installed (8.0.0.1669) under the Free license and monitoring 5 Hyper-V Hosts, 46 VM clients.
I installed it on 1/7/16 and my database is currently 15GB. I'm sure that's not terrible, but I'd like to limit the size of the database to prevent it from growing extensively as it did in my late attempt at Veeam. Previously I had 12 hosts on it and the database grew to over 800GB, we had to turn it off to prevent impacting other systems and I'm getting back around to working on it. I have another 7 hosts to add, and roughly another 70 clients, but I'm not sure what this will do to the database size.

I know prior to update 2 there was an issue with Veeam collecting too much data from Hyper-V. I'd like to avoid that situation this time around if I can.

I set the Historical Data Retention Period to 1 months per the VeeamOne support tool.

If it helps, the database lives on a server running Microsoft SQL 2012 (11.0.2218)


Is there anything else I can do, or look at, to make sure the database size stays reasonable? What kind of size could I expect for a 12 host, ~120 client database?

[Shestakov]

Hello,

Keep in mind that new Historical Data Retention Period needs time to be renewed. When did you set it?
15GB is not enough for 12 hosts with 120 VMs. How many months of monitoring would you like to have?
Thanks!

[Vitaliy S.]

You can fine tune the amount of Hyper-V events stored in the database with the help of our support team.

[BSalyer]

Since I'm on the free version I thought I could only view 7 days of data - which would make anything beyond that superfluous.

I'm just not sure what to expect for database size. I wasn't expecting 15 gb over 2 days with 5 hosts 46 clients - of which several ended up not reporting in after the first day. it just seemed like a large size for the comparatively little data.

I'll update to v9 and contact the support team per Vitality's recommendation if I continue to have problems with hosts reporting in, or database size.

[Shestakov]

I'm just not sure what to expect for database size. I wasn't expecting 15 gb over 2 days with 5 hosts 46 clients - of which several ended up not reporting in after the first day. it just seemed like a large size for the comparatively little data.

That`s true. It looks like too much for 5 hosts and 1 months period. So contacting support is a good idea. Please provide your support case number once you have it.
Thanks!

[Vitaliy S.]

Since I'm on the free version I thought I could only view 7 days of data - which would make anything beyond that superfluous.

That's correct, but please keep in mind that we still store data according to the configured retention policy settings. This will allow you to report on any data once you decide to switch to full license. Many customers found it handy especially for capacity planning and deployment project reports.

[LeoKurz]

Hi Eric,
Note that task to clean database by retention executes once a day in Veeam One Monitor, once a week in Veeam One Reporter. When did you change the retention?
Thanks!

Any chance to trigger these processes manually (reboot)?

__Leo

[Vitaliy S.]

Our support team might have a script to initiate this task on demand. Out of curiosity, what's your DB current size and how many objects do you monitor (VMs, hosts, datastores)?

[LeoKurz]

I'm working as a consultant in different environments and I see the problem with the DB exceeeding the express limit of 10G regulary. Most customers running 4-10 Hosts with 200-500 vms. Most customers don't have the need for a retention time of 12 months, so reducing the time is mostly the solution. Would be nice, if I could force the purge of the old data manually.

__Leo

[Vitaliy S.]

Might be a good option to ask during initial setup/configuration. Thanks for the feedback!

[haslund]

Hi Dmitriy,

You can change retention policy settings via our support tool.

Here is a way to open it via Monitor GUI (v8 only): http://helpcenter.veeam.com/one/80/vsph ... tings.html

Alternatively, you can navigate to this tool manually:

Code: Select all

C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

Let me know if that helps!

Very useful!