nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Question on promoting large amount of data using O

Balu110

I have a requirement to promote about 1GB of data on a regular basis (contains 800 to 900 files) to various servers. So I would like to clarify the following:

1- how do I calculate memory required on OD base and receivers to promote 1G of data?
2- is there any restrictions on total number of files being promoted to servers?
3- is there any restrictions on individual file size?

Any help is greatly appreciated.

Currently we are running TS 6.1 and OD 5.6 on Solaris 8.

Thanks in advance,
Balu.

Find more posts tagged with

Comments

Adam Stoller

Is this a transactional or non-transactional deployment?
This is a big factor in determining the amount of disk-space you need on the receivers and the amount of time it takes to complete the deployment (non-transactional is faster and uses less disk-space)
Also - are you running with the GUI / Reporting features enabled? That tends to slow down deployments even more.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Balu110

Hi Fish,
This is crucial data promotion for the client and being implemented into serveral servers. So I am thinking of enabling tranactional.

Currently we are not using GUI for Open Deploy. How do I enable/disable GUI/ Reporting features?

Thanks,
Balu.

tmp.zip

Adam Stoller

In the server configuration for both sides of the deployment (i.e. odbase.xml and odrcvr.xml) there is a setting for enabling event reporting - you want to make sure it's set to "no" - and if you have to change the file in order to do so, remember to stop/start the OD server process afterwards to make it take effect.

If you're doing a transactional deployment of potentially 1 Gb of data - you need to make sure that there is at least 3 Gb free on the receivers (on the partition where the data lives) because you stand the chance of having 3 copies of each file on the server at some point during the deployment
(foo, foo.iwold, foo.iwnew)

[*The latest version of OD provides for the ability to specify a different location for the temporary files - so you might be able to have space used in a different partition -- not sure what effect, if any, this has on time of deployment but my guess would be that it might lengthen it because you would end up with cross-partition copies taking place in the deployment rather than simple atomic renames]

Another thing to consider is the network bandwidth between the Base Server and Receiver(s) - the better the connectivity and bandwidth between the servers, the faster the transfer - and vice versa.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com