Data Management Client Tools

As the section title states, these are tools which allow users to upload files to the grid, replicate data and locate the best (nearest) replica available. These tools were developed to replace the older and slower edg data management tools.

Following is a summary and a brief explanation of the available lcg data management tools.

lcg-aa: Adds an alias in the RMC for a given GUID.
lcg-cp: Copies a grid file to a local destination.
lcg-cr: Copies a local file to a SE and registers the file in the LRC.
lcg-del: Deletes one file (either one replica or all replicas).
lcg-gt: Gets the TURL for a given SURL and transfer protocol.
lcg-infosites: Provides information about resources on the grid.
lcg-la: Lists the aliases for a given LFN, GUID or SURL.
lcg-lg: Gets the GUID for a given LFN or SURL.
lcg-lr: Lists the replicas for a given LFN, GUID or SURL.
lcg-ra: Removes an alias in RMC for a given GUID.
lcg-rep: Copies a file from one SE to another and registers it in the LRC.
lcg-rf: Registers in the LRC a file residing on an SE.
lcg-uf: Unregisters in the LRC a file residing on an SE.

Some points to note:
1) All of the commands (except for lcg-gt) require the (mandatory) specification of the --vo [vo-name] option.
2) The LCG_GFAL_INFOSYS environment variable must be specified and must point to the BDII. This is essential. If not set, the commands can not retrieve the necessary information required for their operation.
3) The lcg-cr, lcg-cp, lcg-rep and lcg-del commands require a valid proxy certificate because the physical files are protected by the grid-mapfile and the local permissions on the file.

Note that the information in the LRC and RMC catalogues is currently not protected. Accordingly, information in the catalogues can be altered by anyone. This issue is being addressed.

Example Use Cases (you can try these at home : )

to come....