FEATURE REQUEST: Unable to start FLR helper appliance

[slaburda]

I have a problem during FLR non-Windows systems in Enterprise Manager.
I have defined in Enterprise Manager a role “Restore Operator” for specific group. If user from this group select (in EM) and mount one VM for FLR restore, everything is OK. But if he need to change “Restore point” or VM for restore, he get error “Server error: Unable to start FLR helper appliance because the assigned IP address is already occupied by another appliance”.
I understand this situation, because of course the first FLR appliance running. But I don’t find any button which unmount previous FLR or any settings which allow you to use more than one FLR/IP address. I have opened support case # 02020891 where is a detail description. Recommendation from support is to create feature request ...

Is it possible to add to EM choice unmount mounted FLR appliance or do it automatically when user change restore point or VM for restore?

Thank You for advice,
Stanislav

[foggy]

Hi Stanislav, we were going to add the ability to dismount the appliance. As a workaround, you can log out from EM and log in back, the appliance will be dismounted.

[slaburda]

Hi, thank you for good news. Do you know term when a new build come with this feature?

[foggy]

No, I do not have such information. Btw, another workaround is using dynamic addressing for the appliance.

[dellock6]

Hi,
I feel a bit sorry for this as I've discovered the issue that lead to this new behaviour in 9.5, but it's way better as it is today, trust me. As Alexander suggested, the solution to use multiple appliances is to setup the appliance to use DHCP, and in order to unmount a FLR is to logoff from EM, or to wait for the timeout, that is 20 minutes of inactivity. I'd go for dhcp to be honest, so you don't have to worry with manual umount or limits of FLR's that can be used concurrently.

[dellock6]

Sorry for the small error, I re-checked my notes, timeout is 15 minutes, not 20.

[slaburda]

Thank You for Your response. How does the timeout works? If I mount FLR appliance and making restore not from EM but connecting through putty to FLR appliance and coping data, will the timeout counting down or not?

[dellock6]

Good question, I have not tested this scenario, I'll put it in my tests list, it may take some days to find some free time, unless some of my colleagues have the answer already.

[foggy]

If you perform FLR mount from EM, the session will still be closed once you automatically log off the EM after 15 minutes. Veeam B&R will not be able to "detect" the activity performed on the appliance outside of EM. If the backup is mounted from Veeam B&R console (or PowerShell), it stays active for two days.

[slaburda]

If I log off from EM FLR appliance unmount immediately - I don’t registered any timeout. Do you mean timeout is applied after 15 minutes inactivity in EM? If Yes, is it possible prolong timeout?

[foggy]

Yes, this is timeout for inactivity. You can change the sessionTimeout value in C:\Program Files\Veeam\Backup and Replication\Enterprise Manager\WebApp\Web.config file.

[slaburda]

SessionTimeout is in minutes? Because after time inactivity log me off after 15 minutes. If I neead to set up timeout to 2 hrs what I have to fill in?

[foggy]

Yes, the value is in minutes.

[slaburda]

But the actual value have 30 min but I was log off after 15 min.
<add key="sessionTimeout" value="30"/>

[slaburda]

Hello foggy, I change the sessionTimeout to 60 minutes but session still logout (backup unmount) after 15 minutes inactivity. Do You have idea what's wrong?

[foggy]

I have QA engineer looking into this, will get back once I have any definitive info.

[foggy]

Stanislav, there're actually two timeouts: sessionTimeout you've changed previously handles inactive browser session duration, while there's another one that controls backup mount itself and can be changed via the HKLM\SOFTWARE\Veeam\Veeam Backup Reporting\UserSessionTimeout registry value (in minutes) on Enterprise Manager server.

[slaburda]

Hi foggy,
thank you. Is this correct setting? Is the type of registry value String or DWORD? Reboot server?
[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup Reporting]
"UserSessionTimeout"="30"

Thank you
Stanislav

[foggy]

Yes, the setting is DWORD. Restart the Enterprise Manager service for it to take effect.

[slaburda]

I set timeout to 120 min (in hexa 78), restart EM server but appliance was unmounted after 33 min.
[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup Reporting]
"UserSessionTimeout"=dword:00000078

GUI timeout is OK. I changed it to 480 min and GUI does not logout.

Any idea what can be wrong?
thanks
Stanislav

[foggy]

Could you please also check the following value in configuration file: <add key="cacheTimeout" value="63"/>?

[slaburda]

I have this velue:
<appSettings>
<add key="BES-host" value="127.0.0.1"/>
<add key="BES-port" value="888"/>
<add key="cacheTimeout" value="30"/>
<add key="sessionTimeout" value="480"/>
<add key="requestTimeout" value="900"/>
<add key="enableVcRegistration" value="0"/>
<add key="appVersion" value="9.5.0.0"/>
<add key="logFileName" value="Veeam.WebApp.log"/>
<add key="loginAttemtNumber" value="10"/>
<add key="loginLockTimeoutMinutes" value="10"/>
<add key="vs:EnableBrowserLink" value="false"/>
</appSettings>

[foggy]

<add key="cacheTimeout" value="30"/>

This is why it unmounts after 33 min. Try to set it to a higher value.

[slaburda]

I will try it. Thank you.