In the end, client machines will locate the different shares that compose your database by mounting those share points on the client machine's filesystem root. Then, when you need to expand the storage space for your Harmony database, you can create a share named /usadata001 on another machine, and another one named /usadata002 on another machine, etc. The best practice is to name the first /usadata share /usadata000, and it is typical, although not mandatory, to store that share on the same machine as the database server. If you intend to use several /usadata shares, they must be numbered them. The result is that the database file structure is entirely accessible on all machines in the network. Likewise, if other servers are used to store scene data, the shares of these servers are mounted on the database server. On client machines, every network share is mounted on the same location as the location of the actual share on their respective server. There can be as many as the studio needs, which allows you to expand the storage capacity of your database server by creating a new /usadata share on a new file server. Those can be hosted on the database server or on any machine on the local network that the client workstations can access. usadata shares, which contain the actual scene data: the drawings, animation, 3D models, scene palettes, etc.
This part of the database must be hosted on the machine that runs the database server service/daemon, to which client workstations will connect directly. The /USA_DB share, which contains the information on all the scenes, environments, jobs as well as shared assets such as palettes and templates stored in environments or jobs.Optionally, it can also host the actual scene data, but other machines on your network can be used for scene data storage as well, as those are two different components of a Harmony database.Ī Harmony database is structured using different network shares: The primary purpose of the database server is to host and manage the information on its Harmony scenes.
0 kommentar(er)
