Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
> Hi > > I am using DRBD on SLES9 to replicate the CVSNT repository . It is working > fine , but i have some questions on DRBD . > > -- Although i am using DRBD , i want to take the daily backup of data to a > tape drive . I want to take the backup from the secondary DRBD machine only > (every day) . Is this is possible ? . I know that , we can't mount the > secondary machine's DRBD partition onto the filesystem . I am not interested > to Chane the secondary to primary on every day for backup purpose . > This has been discussed many times on the list, you should only try to back up from the machine that is in drbd primary state. > -- If i am using DRBD with Linux HA (heartbeat) , if the primary DRBD node > goes down , the secondary DRBD node automatically changes to primary ? ( I > don't want to manually execute the commands to change from secondary to > primary ) . > Take a look at this thread I started on the cvs list. "cvs as a heartbeat client (questions)" http://lists.gnu.org/archive/html/info-cvs/2004-03/msg00182.html basic summary: to stop: 1) we need to stop new cvs connections from being established pserver -> mod [x]inetd configs to disable connections restart [x]inetd for changes to take place. rsh -> mod [x]inetd configs to disable connections restart [x]inetd for changes to take place. ssh -> stop sshd rsh and ssh could also be stopped with /etc/nologin. 2) to bring any running cvs's down gracefully killall -q -SIGTERM cvs give it a little time then beat any left into submission with killall -q -9 cvs to start: reverse what you did in 1 for stop. for status: report the state of the control method (i.e. have you modified the files to stop or allow run?) > Please anyone answer to my questions . Thank you. Sorry, I have not yet gotten permission to release the cvs_ha script I wrote. -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter