# PBS to stage all data to the node **URL:** \ **Category:** Users/Site Administrators\ **Created:** [September 11, 2019, 9:47am UTC](https://community.openpbs.org/t/pbs-to-stage-all-data-to-the-node/1768 "2019-09-11T09:47:41Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![depaksoni](https://avatars.discourse-cdn.com/v4/letter/d/5e9695/32.png) [@depaksoni](https://community.openpbs.org/u/depaksoni)\ **Post date:** [September 11, 2019, 9:47am UTC](https://community.openpbs.org/t/pbs-to-stage-all-data-to-the-node/1768/1 "2019-09-11T09:47:41Z")
Hi, how to configure PBS to Stage data to the node regards Soni ---
**Author:** ![adarsh](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@adarsh](https://community.openpbs.org/u/adarsh)\ **Post date:** [September 11, 2019, 10:16am UTC](https://community.openpbs.org/t/pbs-to-stage-all-data-to-the-node/1768/2 "2019-09-11T10:16:40Z")
You can do this from within the job script 1. For example: #PBS directives \< main application batch command line \> \< scp or cp or rsync files form the job directory to your source location \> \< cleanup the files in the job directory after the above copy command is successful or keep both \> exit 2. execjob\_epilogue hook which does the scp , cp or rysnc or any remote file copy to the source location and then deletes the files from the sandbox / job directory (or you can keep both ) 3. Write a hook event that alters the STAGEOUT attribute and redirects to the source directory, Thank you ---
**Author:** ![gabe](https://avatars.discourse-cdn.com/v4/letter/g/5daacb/32.png) [@gabe](https://community.openpbs.org/u/gabe)\ **Post date:** [September 11, 2019, 4:49pm UTC](https://community.openpbs.org/t/pbs-to-stage-all-data-to-the-node/1768/3 "2019-09-11T16:49:01Z")
PBS does have a built-in staging mechanism triggered with the stagein and stageout options to the -W (additional job attributes) directive. If you consult the qsub manpage and search for ‘stagein’, you will find the documentation. In my opinion, the documentation for this feature has always been rather confusing and does not provide an example, so here is an example: ``` #PBS -W stagein=/path/to/local/dir@remote.host:/path/to/remote/dir,stageout=/path/to/local/dir@remote.host:/path/to/remote/dir ``` Importantly, and also not mentioned in the manpage, are: 1. The value of PBS\_SCP in /etc/pbs.conf is the command used to perform the copy. I _think_ that the default is to use /bin/scp, however it could be rcp. I make it explicit in pbs.conf. Obviously if using scp, you need to have configured passwordless ssh/scp. 2. The PBS\_SCP command is run on the first node in the job (the mother superior) for both the stagein and stageout. Thus the stagein is a pull done by the compute node and stageout is a push done by the compute node. If you need more sophisticated staging, then I recommend either writing your own script and making it PBS\_SCP, or using the scenarios that @adarsh mentioned. ---
**Author:** ![adarsh](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@adarsh](https://community.openpbs.org/u/adarsh)\ **Post date:** [September 11, 2019, 9:33pm UTC](https://community.openpbs.org/t/pbs-to-stage-all-data-to-the-node/1768/4 "2019-09-11T21:33:41Z")
Hopefully this will help. The file transfer protocol depends what you have configured on the PBS Servers /etc/pbs.conf for STAGEIN (server to compute nodes) and PBS MOMs $PBS\_HOME/mom\_priv/config for STAGEOUT (if $usecp does not exists in mom\_priv/config then it follows what is configured in /etc/pbs.conf on the MOM) Key words to search in the PBS Pro admin guide : $usecp Default copy mechanism is : RCP , otherwise SCP and CP if they are configured in pbs.conf / mom\_priv/config #PBS -W stagein = \@:\ #PBS -W stageout = \@:\ stagein: location of input files ( copy input files to the execution directory or job directory) stageout: location of output files (copy results from job directory or execution directory back to you intended location ) execution\_path: execution directory on the compute node storage\_path: filename on host hostname **The ‘@’ character separates execution path specification from storage path specification** **@ character is just a separator, it does not represent username@hostname kind of specification** Sample: ``` #!/bin/bash #PBS -N pbsproapplicaton #PBS -l select=1:ncpus=1:mem=1gb #PBS -W sandbox=PRIVATE #copy the box.fem file from the current location to headnode:/home/pbsdata/optistruct with the same file name box.fem #PBS -W stagein=box.fem@headnode:/home/pbsdata/optistruct/box.fem #copy all the results from the sandbox or jobdir to headnode:/home/pbsdata/output #PBS -W stageout=*@headnode:/home/pbsdata/output #!/bin/bash #PBS -N pbsproapplication #PBS -l select=1:ncpus=1:mem=1gb #PBS -W sandbox=PRIVATE #copy the box.fem and box.inc files from the current location to headnode:/home/pbsdata/optistruct with the same file name box.fem #PBS -W stagein=box.fem@headnode:/home/pbsdata/optistruct/box.fem,box.inc@@headnode:/home/pbsdata/optistruct/box.fem #copy *.out and *.log result files from the sandbox or jobdir to headnode:/home/pbsdata/output #PBS -W stageout=*.out@headnode:/home/pbsdata/output,*.log@headnode:/home/pbsdata/output ``` ---
**Author:** ![agurban](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/agurban/32/67_2.png) [@agurban](https://community.openpbs.org/u/agurban)\ **Post date:** [September 12, 2019, 4:21pm UTC](https://community.openpbs.org/t/pbs-to-stage-all-data-to-the-node/1768/5 "2019-09-12T16:21:09Z")
Please see the PBS Pro User Guide, section 3.2, “Input/Output File Staging”, page UG-33.