![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Stopping DOORS database Topic Summary: Stopping and starting the DOORS database before and after backups Created On: 8-Feb-2005 15:24 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Thanks for the feedback. I guess we'll continue as we are until we get to XT! | |
![]() |
|
We currently use a scheduled batch file with the command net stop "DOORS 7.1 Database" to stop the DOORS database before taking our nightly tape backup.
Does anyone do anything in addtion to this? Is there a method for kicking users out and clearing locks automatically? We're running Windows 2000 Adv Server. |
|
![]() |
|
![]() |
|
We have found no need to remove lockfiles in v7.
For reference, here is the nightly script we run to back up our databases. Unlike your setup, we run our database on UNIX.. We bring the database down, make a quick tarfile of the entire DB (which is later stored on tape), and bring the database up. This takes only a matter of minutes.. I don't like killling the server while users could be still logged in, but besides telling them that they should be logged out at 3AM, there isn't much else I can do.. Any tips, anyone? ==================================================== DOORSHOME=/applic_net/doors/doors7db SERVERDATA=$DOORSHOME/data PATH=$DOORSHOME/bin:$PATH PORTNUMBER=36680 DOORSDATA=$PORTNUMBER@ontario export DOORSHOME SERVERDATA PATH PORTNUMBER DOORSDATA # build file name. backupfilename=doors7db-data-backup.`date +%d_%b_%y`.tar; # Dump list of low-level DOORs v7 connections to file. netstat -a | grep 36680 > /applic_net/doors/doors7db/netstat.out # Take DOORs v7 database down. $DOORSHOME/bin/dbadmin -data 36680@ontario -killserver #Tar up data directory, and place it on the /backup slice. cd /mnt/doors_data/aurora tar cf /backup/$backupfilename data #Bring the database back up, and leave a flagfile in /doors for debugging. echo Bringing v7.1 database back up.. /sbin/init.d/doors7db start touch $DOORSHOME/start.flag #Compress the new tarfile using the strongest gzip algorithm. /usr/local/bin/gzip -9 /backup/$backupfilename echo "Done!" ==================================================== --Scott Catterill --Network Admin, General Dynamics Canada |
|
![]() |
|
![]() |
|
I've never done this but have been tempted. You could create a DOS *.bat file that uses the "dbadmin.exe -d 36677@ServerName -u" command, and outputs that to some log file. That log file then has a line for every logged in user.
Execute the bat file from DOORS via 'system ("GetUsers.bat")'. Find a way to wait for the log file to be created. Open the log file, reading each line, and get the process ID of everyone that's logged in (ignoring the "administrator" line that represents the bat file itself). Then issue some sort of "kill user" command via the DXL "system" command. Then close and power down DOORS. Eager minds would like to know if you ever get that to work. - Louie For whatever its work, IT here does backups without logging everyone out. They just copy the "data" folder as-is. |
|
![]() |
|
![]() |
|
Thanks for the feedback. I guess we'll continue as we are until we get to XT!
|
|
![]() |
|
![]() |
|
Hi Louie,
though the Thread is yet very old, I would like to put in a new idea:
If you use FlexLM you may be able to force to return the licenses. DOORS checks about every 7 min for the license and detects, that it is gone and wants to close immediately regularly. The user is prompted to save all current data. But what if the user is not present to answer the question? Then the data are still not saved ...
Regards
Hubertus
|
|
![]() |
Telelogic DOORS
» Administration
»
Stopping DOORS database
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.