Comprehensive data protection for all workloads
Post Reply
raphael@schitz.net
Veeam Vanguard
Posts: 66
Liked: 2 times
Joined: Jul 25, 2009 12:14 am
Contact:

Multiple instance of veeamshell in TS environnement

Post by raphael@schitz.net »

Hi, it seams impossible to launch multiple instance of Veeam Backup on a Windows 2003 Terminal Server. Only one user can lauch veeamshell.exe at a time.
Is there any trick or plan to avoid this issue ?

Gostev
SVP, Product Management
Posts: 26679
Liked: 4268 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Multiple instance of veeamshell in TS environnement

Post by Gostev »

Hi Raphael, the upcoming version (4.0) will have a web UI allowing for job management and reporting over multiple instances for multiple users at once, so you should no longer need to launch multiple Veeam Backup user interfaces on the same computer.

raphael@schitz.net
Veeam Vanguard
Posts: 66
Liked: 2 times
Joined: Jul 25, 2009 12:14 am
Contact:

Re: Multiple instance of veeamshell in TS environnement

Post by raphael@schitz.net »

Gostev wrote:Hi Raphael, the upcoming version (4.0) will have a web UI allowing for job management and reporting over multiple instances for multiple users at once, so you should no longer need to launch multiple Veeam Backup user interfaces on the same computer.
Hi Gostev, any ETA for this release ?
Thanks for the answer by the way ;)

Gostev
SVP, Product Management
Posts: 26679
Liked: 4268 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Multiple instance of veeamshell in TS environnement

Post by Gostev »

End of Q3

raphael@schitz.net
Veeam Vanguard
Posts: 66
Liked: 2 times
Joined: Jul 25, 2009 12:14 am
Contact:

Re: Multiple instance of veeamshell in TS environnement

Post by raphael@schitz.net »

All actions would be available in the web GUI ?

Gostev
SVP, Product Management
Posts: 26679
Liked: 4268 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Multiple instance of veeamshell in TS environnement

Post by Gostev »

You will be able to control jobs, but not edit the job's settings. We found that jobs are typically edited very rarely anyway - most oftenly, they are designed/documented/deployed once and never updated after this. However, there will be access to all settings through PowerShell, so if you have scenario requiring you to constantly modify your jobs' settings, you will be able to address it through automation. Alternatively, you will be able to simply give every admin his own Veeam Backup server to play with, yet still preserving centralized reporting and management. This might be even better scenario because it essentially gives centralized backups with decentralized restores (what if a few admins need to restore their data at once - in case of single Veeam Backup server, it will become a bottleneck).

Post Reply

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 34 guests