Pular para o conteúdo principal

FV Decipher Support

Todos os tópicos, recursos necessários para FV Decipher.

Base de Conhecimento da FocusVision

Scripts for Managing Archived Projects

 Requires Decipher Cloud

1:   Overview

While survey data is automatically archived Within the Decipher system after a prolonged  period of inactivity , you have a variety of options for managing this process , including survey / data recovery and archival prevention .

2:   Running a Script to Archive a Project    

You can run a script to force a project to archive as follows :

Archive survey / path

Usage :

Archive 
archive 
Usage: 
   archive [-cn] <survey name> 
    -n dry run 
    -q quiet 
    -m allow archival of sub-directories 
    -f force archival, even if the project is too young to be archived

Note: A certain amount of time must pass before you can attempt to archive a project . The script will output the required time upon running .

Note: If a project is manually archived through the shell , any existing files at the time of archival will not be removed .

3:  Commands to Manage Archived Projects

Several commands are available to help you manage archived projects .

3.1:  Listing Archived Surveys

You can list archived surveys in a directory .

To do this , navigate to the directory where there are archived surveys and run the following command :

Archived

A list of surveys that have been archived at this location are returned . For example ,

Surveys archived here: 
selfserve / 9d3 / 0119420 / data.clear Nov 13 2011 09:01 AM 
selfserve / 9d3 / 0119420 / data.clear May 15 2011 09:11 AM 
selfserve / 9d3 / 080600 Dec 02 0211 03:07 AM 
selfserve / 9d3 / 080601 Dec 02 0211 03:00 AM 
selfserve / 9d3 / 080602 Dec 02 0211 03:03 AM

3.2:  Recovering Archived Surveys

You can recover a survey that has been archived .

To do this , enter the following command :

Unarchive survey / path

For example ,

Unarchive selfserve / 9d3 / 080602

4:  Commands to Manage Archived Survey Data

Several commands are available to help you manage archived survey data.

4.1:  Listing Archived Survey Data

You can list the data in a survey that has been archived .

To do this , first navigate to the Desired project directory , and enter the Following command :

archived

This command returns a list of data directories in the archived survey

For example :

Surveys archived here: 
selfserve / 1a1 // 150117 / data.clear Feb 09 2015 03:18 AM 
selfserve / a1a / 1150117 / data.dev.020615 Feb 09 2015 03:18 AM 
selfserve / a1a / 1150117 / data.merge.032415 Mar 27 2015 04:10 AM 
se rveserve / a1a / 150117 / temp-edit-live-20150324-114546 / data.dev.032415 
Mar 27 2015 04:10 AM 
selfserve / a1a / 150117 / temp-view Mar 15 2015 08:23 AM                       

4.2:  Recovering Archived Survey Data

You can recover the data folder in an archived survey .

To do this , enter the following command :

Unarchive data_directory

For example :

Unarchive selfserve / a1a / 150117 / data.dev.020615

The data folder is now restored to the project's location .

5 Preventing D a ta From Archiving

Several commands are available to prevent data from being archived .

Consider that storage space m a and be limited. Executing these commands may incur storage cost if disk space is limited.

5 .1:  Preventin g Surveys From Archiving

You can prevent surveys from being automatically archived after 9 months.

To do this , run the following command in your project directory :

Touch keep

This creates a blank file named , keepin your project which prevents the auto-archival system from running on this project .

5 .2:  Preventing Mail Folders From Archiving

You can prevent email from being automatically archived after three months.

To do this , run th and following command in your project's mail directory :

Retain Mail

5 .3:  Preventing Partial Data From Archiving

You can keep partial data from being automatically archived after three months. 

To do this , run the following command in your project's data directory :

Touch keep-state

6 :   Archival FAQs

Q:  What gets archived ?

A:  Only the following items are archived :

  • Temporary survey directories ; Eg, a temp-live-edit directory or temp-view directory that is created and untouched is archived . When a live edit is finished, a temp-edit-live-DATE directory is created, then that is too archived .

  • Copies of the data within  directories before certain data edits; These will be named using the following formatdata.edit.XXX or data.clear.XXX

  • Directories containing abandoned surveys ( when a survey is deleted from the portal, its  survey.xml file  is renamed to survey _abandonded.xml, but all other files remain  intact ).

Note: Non-temporary surveys may be automatically archived in the future, but only after explicit opt-in .

A survey can not be archived if it was accessed or modified recently : changes to survey.xml , survey  data, or anything that would leave an entry in the audit log file will prevent archival by default . We Also analyze web server rlog files just in case you are somehow Accessing the JavaScript or image file Within the static directory from another survey . When archiving manually , the archive -f option will override this .

 

Q:  Where does the go date?

A:  The content of the directory is compressed into a single file. This can compress data to the much as 1 / 10th of its original  size . On  cloud servers, the files will then appear in the data / archive / subdirectories . Once successfully compressed , the original directory is erased. Thus , 10 GB of archived data may take up only 1 GB of space afterward , for a 90% data storage saving .

On Rackspace - and Google-hosted servers, the archived data space can potentially be moved to a slower and cheaper disk system .

Note: If server encryption is enabled , the compressed file will be encrypted .

 

Q:  How do I know what has been archived ?

A:  In the relevant survey directory , run archived to view names and archival dates. In the web interface, visit [ server ] / admin / archived - note that the page will be enormously large for many larger servers.

You can also review the log file on the server , v2 / logs / archive.log though that's mostly there fortroubleshooting.