Offload Scan Server and SVA

[virtualchunk]

Hi,

using Move for about 150-200 Citrix XenApp Server (about 5000 Users) is there a best practice

for the amount of Scan Servers? This workload should be classified as High Load.

Furthermore is it Best Practice to Keep the scan Network traffic within the Blade Center ?

I heard something about that could be achieved with SVA Manger Appliance ? If so, how ?

Best Regards,

Marc

[rajinp]

Is customer using sva manager ?

[virtualchunk]

No, not now. With sva manger, is it possibel to keep scan traffic inside a Blade Center Chassis ?

Is this a best practice to keep scan traffic "local" ?

[rajinp]

SVA Manager is for load balancing not to keep the scan traffic local.

scan traffic will be between client and OSS.

[Troja]

Hi, if every blade is a ESX host this could be possible.

Because, when using the Cloud Connector you know the virtualization host where the virutal machine is located. Based on this Information the Systems can be tagged and afterwards configured to use specific OSS. 🙂

Cheers

[frank_enser]

If he's using ESX, he could use MOVE Agentless. Then he would be sure, that the scan traffic will be hypervisor local

And best practice for MOVE Multiplatform is having multiple OSS, in case a OSS unexpectedly goes down (or is having Windows Updates ).

[virtualchunk]

The ideas was, to tag the machines to connect them to the Offload Server running in the same Blade Center.

Yes that should be possible. What what if the vm will be moved to another blade center ? Is there a way to

retag the machine dynamicly ?

Another thing i cant find an answer: i read a offload server is for about 200 clients. But what if those clients

are Terminalserver running 5000 Users ? Is there any sizing guidelines available ?