I’m planning on purchasing another server just for licensing and I though I’d take the load off of the primary server which acts both as Domain Controller as well as a File Server in my company and move Deadline Repository to this new server with much less load.
The question is, how much space Deadline Repository needs? Thes erver will only have one HDD with about 150GB, and about 50GB free of space. We don’t submit our scene files to the Repository though, so, will there be any problem in the near future with this config? That the Repository will be sitting on a different machine than the actual project data?
All will be setup within one network, one Domain, one physical place actually.
So basically, this new server will act as a dedicated Deadline Repository as well as license server, so, not much load will be put upon this machine.
The setup you described should work fine, and it’s actually quite common to have the repository on a dedicated server and project data on another server.
The repository size on disk starts at less than 150 MB, and grows and shrinks with the number jobs in the queue. Since you’re not submitting the scene files with the jobs, this will greatly reduce the repository’s foot print (each job will probably take up less than 1 MB on average, but this really depends on the number of tasks for the job). As long as you make it a habit to clear out old jobs, you should be fine. If you have Statistics Gathering enabled in the Logging section of the repository options, be aware that the reports folder in the repository will continue to grow as stats are logged for completed jobs.
So, according to this document, I shouldn’t move the entire repository to a dedicated server, but rather have the Repository on the File Server, and only run Pulse from the dedicated one?
Also, do I have to install the whole Repository to the other server, or will it be enough to just copy over the “bin” folder and run Pulse manually?
It really depends on the number of nodes you have. The paper always keeps scalability in mind, and at some point it becomes inefficient to have Pulse running on the same machine that the repository is installed on. If you are running 20 nodes or less though, it’s probably safe to keep them on the same machine.
You shouldn’t run pulse directly from the bin folder in the repository. You should install the Client software, as Pulse is part of that installation. The bin folder in the repository is only meant for performing auto-upgrades. Here is the Pulse setup documentation for further details: software.primefocusworld.com/sof … line_Pulse
