The idea is have a single host for all the various dCache postgresql databases (both namespace, srm, pin manager and space manager) and we will run the PnfsManager with the chimera backend on the same host.
It should be great have a second and identical host as a warm standby, using continuous WAL archiving of postgresql. That way you will have a copy of all databases which are almost up to date (within a few minutes).
Following FNAL dCache configuration, pay attentio to make a independent disk layout for databases, logs and system. An extreme advice is set all loggin parameter in pnfsSetup to 0 (no logging) and redirect all log output from the PNFS server to /dev/null. Also raid10 on database disk should be good.
Postgres
cd /tmp/ wget http://yum.pgsqlrpms.org/reporpms/8.3/pgdg-centos-8.3-4.noarch.rpm rpm -ivh pgdg-centos-8.3-4.noarch.rpm yum install postgresql postgresql-server chkconfig postgresql on service postgresql initdb chkconfig postgresql on && service postgresql start /usr/bin/postgres --version
Java
chmod +x jdk-6u12-linux-x64-rpm.bin ./jdk-6u12-linux-x64-rpm.bin java -version
PNFS
It is know a dependency with an libpq.so.4
for 32 bits. The first workaround is include a symbolic link of /usr/lib64/libpq.so.4
to /usr/lib/libpq.so.4
. The second one is install pnfs-postgresql using rpm -ivh --nodeps
.
osg-se.sprace.org.br
) at /etc/grid-security
and also a symbolic link to certificates directory. Use automount
to mount our computer element directories:
echo "/osgce /etc/auto.spraid01 --timeout=30" >> /etc/auto.master echo "OSG -rw,soft,bg,rsize=8192,wsize=8192,tcp 192.168.1.150:/OSG" > /etc/auto.osgce chkconfig autofs on ln -s /osgce/OSG /OSG ln -s /osgce/globus/TRUSTED_CA /etc/grid-security/certificates
To change our pools to a 64 bits node host, important directories:
spraid02.poollist
) file stored in the config/ directory of the dCache installation. This entry contains the path to the pool directory, the name of the pool and various settings.
Follow these steps to move a pool. Let's assume you move pool POOL_1 from SOURCE to DEST. SOURCE and DEST may
/opt/d-cache/bin/dcache stop
.
Important: Do not start the pool at SOURCE after you moved the files.
Alternatively we can bring the two new pool nodes online in the existing setup with new pool names, and the use the migration command of the pools to move the data - this command is available from dCache 1.9.1 and onwards.
migration move new_pool1should do the trick. Run "help migration copy" for a description of all the options.
Following some advices from FNAL presentation it is a common mistake put gridftp doors on admin node.
It means that we want to migrate our PNFs to a different host, so we need to export our database. In our SOURCE admin it is done like a
/opt/d-cache/bin/dcache stop /opt/pnfs/bin/pnfs stop pg_dump -U pnfsserver admin >admin.dump pg_dump -U pnfsserver data1 >data1.dumpnow inject it in your fresh install DEST admin node (we assume that all configuration files are set up)
dropdb -U pnfsserver admin dropdb -U pnfsserver data1 createdb -U postgres admin createdb -U postgres data1 psql -U postgres adminand restart your pnfs system.
* May be consider change to a Chimera , following these instructions http://trac.dcache.org/projects/dcache/wiki/pnfsDump2MigratePnfs2Chimera
![]()
Updates
Fulano em dd/mm/aaaa
Coloca o que fez.Ciclano em dd/mm/aaaa
Mais comentarios
-- MarcoAndreFerreiraDias - 23 Feb 2009
I | Attachment | History | Action | Size | Date | Who | Comment |
---|---|---|---|---|---|---|---|
![]() |
FacilitesTalk-dCache_3-30-9.pdf | r1 | manage | 503.3 K | 2009-04-23 - 23:14 | UnknownUser | |
![]() |
PostgresBasics.pdf | r1 | manage | 229.8 K | 2009-04-23 - 23:15 | UnknownUser | |
![]() |
sprace_distribuicao.jpg | r1 | manage | 93.0 K | 2009-02-28 - 02:07 | UnknownUser |
antalya escort bursa escort eskisehir escort istanbul escort izmir escort