![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Scripted approach to archives and backup Topic Summary: Does DOORS support a Synergy style, backup operation? Created On: 23-Nov-2006 12:07 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
I'm planning a migration to DOORS8 from 7.1, and want to get a bit more hands on with the administration of DOORS as well. Is there anyway to script a nightly backup operation whereby the DOORS database is archived to the server and the file then backed up using the backup tool to tape? In Synergy I use the ccmdb backup option through a script that runs out of hours, this way the database gets an integrity check and is then packed to an archive file in a seperate partition/directory before backing up the .cpk file(s) (Partly to do with not trying to backup a live Informix DB). Can I acheive this in DOORS, would it have to be done by using a dxl script to do the archive to the server bit, triggered by running DOORS in batch mode from a script? Regards J |
|
![]() |
|
![]() |
|
Yes, I have implemented this for some customers. In DOORS you can archive Project folders into DPA files, and you can develop such a batch mode script that it runs through all the Projects in the database and then archives each to a defined location. This script can be started by some scheduler.
Two problems with this approach: - DOORS Folders at the uppermost level in the database are not archived, but subprojects inside them are (as the archiving operation is only possible for Projects) - If a Project is locked for some reason, it will be not included in the archive run ------------------------- Pekka.Makinen@softqa.fi SoftQA Oy -http://www.softqa.fi/ |
|
![]() |
|
![]() |
|
Your script will need to examine the lockList and remove all the locks first; tough luck for the guy who's editing a module and goes home. The "for Project in database" loop finds all projects that have no parent project. Fortunately when you archive such a project you automatically get all ITS subordinate projects, and thus get all the Projects.
Project Archives are not particularly useful as backup tools. Be sure to back up the file system in ways that have nothing to do with DOORS. - Louie |
|
![]() |
|
![]() |
|
Hi All,
I was deeply interested in the response to this question, but I don't see the script that is mentioned as solving this user's dilemma. I'm pretty sure I can modify it to archive only the projects I need archived on a regular basis, once I get started with it. Thanks, Chris Annal |
|
![]() |
|
![]() |
|
Nevermind. I figured it out from the help files. It's actually a pretty simple script, which would look like the following, with your actual Project name replacing "project_name" below. For each additional project you want to add, just copy the 5 lines of code below, replacing the "project_name" accordingly, then replace the number after message, incrementing it for each project you want to add.
//archive projects string message1 = archive ("project_name","c:\\DOORS_Projects\\project_name.dpa", false) if (!null message1) { ack message1 halt } string message2 = archive ("another_project","c:\\DOORS_Projects\\another_project.dpa", false) if (!null message2) { ack message2 halt } //Note: In the above script the "C" drive was the destination, but any network drive would work, too. Thanks, Chris Annal chrisa@sensis.com |
|
![]() |
Telelogic DOORS
» Administration
»
Scripted approach to archives and backup
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.