Hi,

I would like to get some info regarding AFSDB-records.

Here some background info:
  * 30000-40000 afs-clients running on Linux/Solaris.
  * client-version: 1.2.x and 1.4.x
  * 2 cells with 3 x AFSDB-servers for each cell
  * near all clients have a static CellServDB file
  * only access to the 2 cells in the intranet
The basic setup of the cells was done in the end of the 90. and only for one 
site. After several years the usage has increased and now many site worldwide 
are using the AFS-cells.

Because there are some changes in our IT-envirenment we have to move the 
AFSDB-servers to a new central DataCenter. And this require a change of the 
CellServDB on every afs-client.

We have created 2 DNS-domains (like our two AFS-cells) that include the 
AFSDB-records for every AFSDB-server.
All new installed afs-clients will get the following config:
  * afsd options: "-afsdb -dynroot -fakestat"
  * CellServDB will include only the cell-name without any AFSDB-IPs (needed 
because we use dynroot)
       >CELL-1
       >CELL-2
So new afs-clients will get new AFSDB-Server config automatically via DNS.

Questions: 
  * What is the behavior of a running afs-client if we change an AFSDB-record 
in DNS (because one of the AFSDB-server is moved to a new location)?
  * Will the changes be done automatically on the afs-client? 
  * Also for the Cache Manager's kernel-resident list of database server 
machines?


We have an update-script for the existing old afs-clients that have a 
CellServDB file with static IP info. This will be run daily via cron.
It fetch a central CellServDB file (if it difer with the local one) and change 
the kernel-resisdent list via 'fs newcell …'
Questions:
  * How can we migrate those clients to use the AFSDB-records without rebooting 
(will the kernel-resisdent list updated if the afsd started with -afsdb)?
  * Or is the reboot needed to get rid of the kernel-list?
  * Which is the oldest afs-version that have support for -afsdb?

We will change only one AFSDB-server per week so the clients have time to make 
the changes via the script.

I hope you can give me some feedback.

/Ralf
   

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to