Guest disk space custom alarm

[curvoolico]

Hi,

I've now upgraded to Veeam One 9 U1 and I'm creating custom Guest disk space alarms hoping that the duplicate alarms issue is solved.
When creating the alarms I came up to some questions:

The Idea is to create alarms for DB SQL VMs with absolute values conditions for the DATA disks ans relative values for the OS disk.
So I created 2 rules linked with OR.
What is the convention to input the disk name (e.g. for the OS disk) and how to exclude that name from the second rule (DATA disks) keeping the wildcard?

Thanks!

[Shestakov]

Hi Manuel and welcome to the community!
You can either type the disk(s) name(s) all post * to include all disks.
Could you specify the goal you are trying to achieve?
Thanks!

[curvoolico]

Hi and thanks!

The idea is to have the rule on top applied to C: and the one below applied to all the other disks excluding C:

[Shestakov]

Thanks for the clarification!
You can`t use wildcard with exclude, so the way to go is to set names of all disks you want the rule to be applied to(everything except C:).

[curvoolico]

Thanks,

So <>C: is not possible?
And how should I declare the disks names? Can I use the drive letter? (e.g D:;E:;F:)

[Vitaliy S.]

Yes, that's correct.

[curvoolico]

Unfortunately it doesn't seem to do it
I've tried with the top rule enabled and disabled....
Is there a way to immediately see if the alarm is being correctly applied instead of waiting some minutes to see if it fires up? I've defined big thresholds so I can test.

[Vitaliy S.]

Manuel, disks should be specified in this format:

Code: Select all

C:\; D:\; E:\;

[curvoolico]

Thanks a lot!
It's now working!

[curvoolico]

Hi,

Now the alarms are working but there seems to be a bug in the e-mail notification.
If the VM has some disks above the threshold they will appear marked as below the defined threshold of -1GB?

[Shestakov]

What is the threshold you set for that disk? Is it 13GB as well as for F:\ ?

[curvoolico]

Yes the same threshold to all defined disks:
d:\;e:\;f:\;g:\;h:\;i:\;j:\;k:\;l:\;m:\;n:\;o:\;p:\;q:\;r:\;s:\;t:\;u:\;v:\;w:\;x:\;y:\

[curvoolico]

But now we're receiving some more alarms and it seems ok without doing any change.
Now it just shows the "problematic" disks...

[Shestakov]

That looks like a bug.
At first because the threshold became different for the disks, secondly because it`s triggered for D:\ which has 26.5 GB of free space.
Could you contact Veeam support team to investigate the issue?
Thanks!

[curvoolico]

Ok many thanks!

[Shestakov]

Once you have a support case number, please post it here for us to follow the investigation.
Thanks!

[FranceLink]

Hi,

I set alarm for Guest disk space with specific thresold.
If I set * in "disks to monitor", alarm works fine.

But if I set specific disk, alarm never fire.
I tried :
C:
C:\
C:\;
"C:"
"C:\"
"C:\;"

No one works..

I use Veeam One 9.5 on Windows Server Standard 2008 R2.
Cluster is 2008 R2 Datacenter using Hyper-V.

Thanks for your help.

[Shestakov]

Hi Gwenaël,

Code: Select all

C:\

is the right format. If it doesn't work, feel free contacting support team.
Thanks!

[FranceLink]

Hi,

Thanks for your answer. Just tried it again, no result.

Unfortunatly I don't have any support contrat any more.

I don't understand why. I think it's to the OS version related cause no one seems to have this problem.
We willl change to 2016 in a few month, I'll see if it correct it.

If any one have some information related to this problem, feel free to help!

Thanks.

[Shestakov]

To be exact it's C:\ for vSphere and C: for Hyper-V.
Does the alarm work on default "any", i.e. * ?

By the way, support is available for everyone on "best effort" level.

[FranceLink]

Hi,

I tried C:, it doesn't work..

Yes it works with the * wildcard immediatly.. Very strange !

Thanks for this precision.

[Shestakov]

Another guess is case-sensitive database.
Try C: and c:
Change delay to 1 minute, not to wait rule execution for long.

[FranceLink]

Hi,

Hey, you'r right !

It's the opposite, when I set C:, it doesn't work, but c: yes ! unbelievable..

An other problem is that Vm disk size refreshing time is very long !

I set check every 15 minutes, I make free space on VM with alarm 45 minutes ago and it's always not corrected.
Do you know what is the refreshing delay? In Veeam One, the disk size is bad (it's the size before I removed files from disk, I can confirm real disk size is correct).

Thanks,

[Shestakov]

Glad it works finally. We will correct the tooltip.
Actually if you don't have any problems with data collection (no corresponding alarms triggered), the guest disk rule should be fired in accordance with the "delay".

[FranceLink]

Yes I think it could be great

delay is set to 15 minutes.
Alarm changed 3à minutes ago, 1 hour after correction.. !

Not a bug problem.
I juste installed update 3, saw some delay problems where corrected, 'll keep you informed.

[Shestakov]

Do you have any data collection alarms triggered?
Are you on typical or advanced scalability mode?

[FranceLink]

After installing U3, disk size update takes about 1 hour..
I'm in typical deployement (3 host, 100VM).
No data collection alaram triggered..

[Shestakov]

Thanks Gwenaël.
We will double-test the alarm with R&D team and see if we can speed up the alarm execution.

[FranceLink]

Thanks !

[Shestakov]

Hello Gwenaël,
I'm back from testing. The alarm execution should take up to 10 minutes, not taking delay into account.
In fact the info is collected along with VI topology and usually takes 3-5 minutes, thus 1 hour is not an expected behavior and we would like to investigate the issue.
So please contact Veeam support team. You may refer to this thread to speed up the investigation.
Thanks!