Feature Request: RTS Usage in UI/EM

Availability for the Always-On Enterprise

Feature Request: RTS Usage in UI/EM

Veeam Logoby cdesch » Wed Nov 23, 2016 1:27 pm

Hi all,

to see if any proxy has some free capacity in terms of sessions, capacity ect. ?
At the moment we could only see the used capacity in the RTS.ResourceUsage.log ?

Would be very nice to see this values in the UI and/or EM.
Thx Chris
cdesch
Veeam ProPartner
 
Posts: 19
Liked: 6 times
Joined: Wed Jul 06, 2016 11:25 am
Full Name: Christian Desch

Re: Feature Request: RTS Usage in UI/EM

Veeam Logoby PTide » Wed Nov 23, 2016 2:55 pm

Hi,

Are you referring to the "max concurrent tasks" number in proxy settings? If so then I'm not getting how the presence of the value in UI would help you unless you start all your jobs manually?

Thanks
PTide
Veeam Software
 
Posts: 3017
Liked: 245 times
Joined: Tue May 19, 2015 1:46 pm

Re: Feature Request: RTS Usage in UI/EM

Veeam Logoby foggy » Wed Nov 23, 2016 3:03 pm

Shouldn't this dashboard help?
foggy
Veeam Software
 
Posts: 14716
Liked: 1075 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Feature Request: RTS Usage in UI/EM

Veeam Logoby cdesch » Wed Nov 23, 2016 6:29 pm

No the Dashboard does not show what i want. I'd like to see what is the current load of proxies or repository session .. i've attached what the RTS log shows:
Code: Select all
- snip -
[20.11.2016 21:05:31] <238> Info     *******************************************************************************************************************
[20.11.2016 21:05:31] <238> Info     |--------------------------------------------------------------------------------------------------|
[20.11.2016 21:05:31] <238> Info     | Resource name                  | Usage | Id                                                      |
[20.11.2016 21:05:31] <238> Info     |-------------------------------------------------------------------------------- vSphere Proxies -|
[20.11.2016 21:05:31] <238> Info     | proxy25.dom.loc                | 16    | {1ec059dd-805e-4195-bf83-06dc11974b0a}                  |
[20.11.2016 21:05:31] <238> Info     | proxy05va07.dom.loc            | 3     | {ac6bbd2a-7770-4466-8ca5-1a270bff2d41}                  |
[20.11.2016 21:05:31] <238> Info     | proxy05va02.dom.loc            | 3     | {e884a641-9519-4783-aaa6-24c8b47910a3}                  |
[20.11.2016 21:05:31] <238> Info     | proxy05va04.dom.loc            | 2     | {2c712f62-6293-42fb-ad81-31dcd278520e}                  |
[20.11.2016 21:05:31] <238> Info     | proxy05va22.dom.loc            | 2     | {49cda662-11d1-4d3c-852c-370efe330b88}                  |
[20.11.2016 21:05:31] <238> Info     | proxy05va03.dom.loc            | 3     | {01bdb4ee-880e-4d93-b52f-3c5048e13ae0}                  |
[20.11.2016 21:05:31] <238> Info     | proxy05va09.dom.loc            | 2     | {3805eca3-d203-4e2e-9f9d-3f21ad3e2686}                  |
[20.11.2016 21:05:31] <238> Info     | proxy24.dom.loc                | 19    | {05d2707f-a7bb-4620-ab38-64c93aa3ee8a}                  |
[20.11.2016 21:05:31] <238> Info     | proxy05va21.dom.loc            | 3     | {a9a1bf26-7067-4c89-a4fa-7c7fbc154035}                  |
[20.11.2016 21:05:31] <238> Info     | proxy05va06.dom.loc            | 2     | {4c236631-32d7-4b66-befe-9fb6359bdb40}                  |
[20.11.2016 21:05:31] <238> Info     | proxy05va10.dom.loc            | 2     | {942003d0-1b0f-47b4-b8bf-a52ee37dbdc9}                  |
[20.11.2016 21:05:31] <238> Info     | proxy05va01.dom.loc            | 2     | {85a1bece-dacd-43ad-b5d2-bfbeffed271d}                  |
[20.11.2016 21:05:31] <238> Info     | proxy05va05.dom.loc            | 3     | {5bdda3be-98fe-461b-9657-c7aa6ff206ed}                  |
[20.11.2016 21:05:31] <238> Info     | proxy05va08.dom.loc            | 2     | {aebbcb8d-8e85-46c9-ab80-d37f7c5993b5}                  |
[20.11.2016 21:05:31] <238> Info     |----------------------------------------------------------------------------------- Repositories -|
[20.11.2016 21:05:31] <238> Info     | dd05_pr05_ext001           | 4     | {97044e6a-649e-4dac-81f6-cb30220cdbf1}                  |
[20.11.2016 21:05:31] <238> Info     | dd06_pr05_ext001           | 10    | {79c5e02b-1df4-44c0-8729-c71f5304332a}                  |
[20.11.2016 21:05:31] <238> Info     | so01_pr05_ext001           | 98    | {56627d22-d2fd-48b9-8912-4bc045262eb2}                  |
[20.11.2016 21:05:31] <238> Info     |--------------------------------------------------------------------------------------------------|
- snip -
cdesch
Veeam ProPartner
 
Posts: 19
Liked: 6 times
Joined: Wed Jul 06, 2016 11:25 am
Full Name: Christian Desch

Re: Feature Request: RTS Usage in UI/EM

Veeam Logoby foggy » Wed Nov 23, 2016 9:26 pm

cdesch wrote:No the Dashboard does not show what i want. I'd like to see what is the current load of proxies or repository session

The dashboard shows the number of tasks that the proxy is currently processing. Here's also a similar dashboard for repositories.
foggy
Veeam Software
 
Posts: 14716
Liked: 1075 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Feature Request: RTS Usage in UI/EM

Veeam Logoby Vitaliy S. » Thu Nov 24, 2016 4:32 pm

Just to add to Alexander's reply: both proxy and repository dashboard can also show you how much CPU/Memory resources were consumed by each job running through that proxy/repository. Together with these main dashboards for concurrent tasks monitoring you can use data from CPU/Memory/Disk/Network tabs to analyze if you have enough room space for additional backup/replication jobs.
Vitaliy S.
Veeam Software
 
Posts: 19539
Liked: 1097 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: No registered users and 33 guests