Login VSI - Adding more VSIShares

Why

The reason for creating more VSIshares is to spread the load from one server to multiple servers. This is done so the VSIshare will not become the bottleneck of the test. We also recommend to disable the main VSIshare (where the Management Console is launched from) as a file / web server so it only functions as a logging server for the test.

Recommended VSIshare amount

The recommendations for the VSIshare / user ratio can be found here.

How To

Step 1

Create or deploy a new machine with a Window Server OS. Or copy the existing VSIshare machine and give it a different hostname, we recommend to give it a logical name. As for the hardware please configure 2vCPU and 4GB of RAM.

Step 2

Create a new folder with a logical name (like VSIShare) on this machine and share this with the Login VSI users. Both share permissions and NTFS permissions must be set to allow the Login VSI users to read, write and modify files. The exact permissions settings can be found here.

Step 3

Copy, from the existing VSIshare, the folders _VSI_Content and _VSI_Websites to the newly created share.

Step 3.1

If your environment has an IIS server setup please make sure that the IIS server is available on all VSIshares and please make sure that the websites are hosted and accessible.

Step 4

Open the Management Console and browse to Infrastructure > Dataservers. Add the newly created share(s) and make sure to disable (or remove the entry of) the existing / main VSIshare.

Step 5

In the Management Console browse to Infrastructure > Webservers. Add the newly created share(s) and make sure to disable (or remove the entry of) the existing / main VSIshare.

Step 6

Make sure the new shares are accessible by the LoginVSI users and start a new test.