Tweet
Our Setup:
We operate inside a large firm with roughly 400 workstations firm-wide. When users log off, a 'VRayUser' with its own set of policy/privileges is logged in automatically and starts Backburner as a service. When a user logs in, the VRayUser is logged out and BB service (and all other apps started by that user session) are stopped. We also have dedicated slaves in the server rack that are up all the time, but far far fewer of them than the available user slaves.
We start VRaySpawner jobs via BB command line. We shut them down manually by deleting the BB job when we are done so that others can use the slaves as usual for animations, strip renders etc.
The Issue:
When we have a DR job using a user workstation, all works as expected; the spawner fires up and we can use it for DR. But we are finding that when a user logs in and the spawner is killed, those buckets hang and don't get picked up by other slaves.
regards,
jonah
We operate inside a large firm with roughly 400 workstations firm-wide. When users log off, a 'VRayUser' with its own set of policy/privileges is logged in automatically and starts Backburner as a service. When a user logs in, the VRayUser is logged out and BB service (and all other apps started by that user session) are stopped. We also have dedicated slaves in the server rack that are up all the time, but far far fewer of them than the available user slaves.
We start VRaySpawner jobs via BB command line. We shut them down manually by deleting the BB job when we are done so that others can use the slaves as usual for animations, strip renders etc.
The Issue:
When we have a DR job using a user workstation, all works as expected; the spawner fires up and we can use it for DR. But we are finding that when a user logs in and the spawner is killed, those buckets hang and don't get picked up by other slaves.
regards,
jonah
Comment