Editing Scanco Administration (section)

====Project Backup/Archive====
*Refer to [[Media:Microct_project_backup.pdf|'''Project Backup SOP''']] or [[Media:Microct_project_backup.docx|''' its Word format''']] for reference.


=====Backup Project=====
Regularly backup projects on a monthly basis using command <code>$ @com:BACKUP_PROJECT.COM</code>
*The script is submitted to the queue and upon completion the log is emailed to the user.
*a SAVset (an OpenVMS file type similar to a zip file), a project info file and a file list are created in DISK5:[BONELAB.PROJECTS.BACKUP] for the microCTs and DISK4:[BONELAB.PROJECTS.ARCHIVE.ARCHIVE] for the XtremeCTs.
*The saveset along with two TXT files created will be automatically SFTP to Winston:\\Backups\backup\
*After the transfer, the saveset file on disk are deleted, leaving only two TXT files on the project disk.
*Only keep the two most recent backups for each project, A or B version name appended on the project name:
:*Backup version "_A" for odd months (Jan, Mar, May, Jul, Sep, Nov), e.g. YZHU_A_OTHER_2017-01-12.SAV
:*Backup version "_B" for even months (Feb, Apr, Jun, Aug, Oct, Dec), e.g. YZHU_B_OTHER_2020-04-08.SAV
*The user MUST verify that the backup completed successfully.
*SAVsets greater than 250 GB cannot be transferred by automatic SFTP, use interactive/manual SFTP instead to transfer to Winston. 
*If you are backing up a very large project, please check the server disk space before starting the backup. 

<pre>
$ @com:BACKUP_PROJECT.COM
===========================================================
BACKUP PROJECT TOOL V1.2 (XtremeCT)
 P1:LOCATION        DISK4:[BONELAB.PROJECTS.DUNCAN]
 P2:TYPE            1=MOUSE,2=RAT,3=HUMAN,4=OTHER
 P3:PROJECT         CAMOS
 P4:PERSON          Ying Zhu
 P5:DESCRIPTION     A monthly backup
 P6:EMAIL           me@ucalgary.ca
 P7:SFTP            y,n
 P8:START           y,n
</pre>


[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]

=====Restore Project=====
In the commands directory (com) is a BACKUP_RESTORE.COM script which will automatically generate a script to restore a user's project.  
*The saveset file has to be moved to Winston:\\Backups\archive folder to be restored.
*The user will be asked if they wish to restore to the original location, or to a new location.
*The script is submitted to the queue and the log from the restore job is emailed to the user. 
*The user MUST verify that the job completed successfully.
<pre>
$ @COM:BACKUP_RESTORE.COM
</pre>
 

=====Delete Project=====
In the commands directory (com) is a BACKUP_DELETE.COM script which will automatically generate a script to delete all the files and subdirectories of a specified path.
*The command script is opened so that the user can check the files to be removed to go ahead.
*You will need to manually delete the root project directory after it's empty.
<pre>
$ @COM:BACKUP_DELETE.COM
</pre>
 

=====Known Bugs in Project Tools=====
*Long file name won't work (28 letters work but not 32 letters).
*if the user specifies too long a file name, the Project Backup Scripts will fail with the following error:
     RMS-E-CRE, ACP file create failed
     SYSTEM-W-BADFILENAME, bad file name syntax


[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]

=====Moving data disk directories=====

Sometimes when the data disk (DISK2) is getting too full measurement directories can be moved to a temporary location. We can move from DISK2 to another location:

 BACKUP DISK2:[XTREMECT2.DATA.00002784...] DISK7:[XTREMECT2.DRF_STORE.00002784...]/LOG/VERIFY

and back again:

 BACKUP DISK7:[XTREMECT2.DRF_STORE.00002784...] DISK2:[XTREMECT2.DATA.00002784...]/LOG/VERIFY

Check out the options for the <code>BACKUP</code> command for more options. One that might be useful is the <code>/DELETE</code> option, which deletes the files after verifying the move.

Sometimes the <code>uct_backup</code> tool loses information about where the data is stored after it's been moved back to DISK2. In this case you can reset the location as follows:

:*Start <code>uct_backup</code>
:*Navigate to the scan in question and you'll see the IMA section is blank
:*While holding the <code>SHIFT</code> key click on the radio button for IMA
:*In the blank text box, type "DK0" and the rest of the path should automatically fill out
:*Save the new path location information

Now you can run <code>UCT_EVALUATION</code> as you normally would. Do not use <code>DEF UCT_DEFAULT_ISQ DISK2:[XTREMECT2.DATA.00002784.00012345]D0013456.ISQ</code> because the evaluation will not complete properly because information about sample/measurement will not be available.

[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]

=====Archive Project Saveset to Tape=====
Projects should be stored safely onto a backup tape once complete.  
Prior to archiving a project please create a directory in DISK4:[BONELAB.PROJECTS.COM] of the project name. Please copy over the com.dir so we can keep all of the scripts on the openVMS system 

<b>Summary</b>

The following steps summarize the process:
:* Archive the project directory to the tape (detailed instructions below).
:* Change tape to "read only" to protect contents
:* Check tape saveset to ensure proper backup
:* Write name of tape on the project LOG sheet
:* Copy project LOG sheet and bring to Bone Imaging Laboratory "completed" project book
:* Bring copy of tape to the Bone Imaging Laboratory for safe keeping
:* <b>Delete</b> the contents of the project from the disk

In the project, there should be the regular set of directories including DOC, COM, MODELS, LOG.  Once the project is stored to tape, ensure that the log sheet for that project include a note stating which tape it was backed up to.  Take a photocopy of the log sheet and add it to our Bone Imaging Laboratory project book for COMPLETED projects.

In the following example, a project titled BERN is backed up onto tape.  Ideally, the name of the SAV file on tape is the same as the project (i.e., BERN).  Note that <b>SAV files must have names with no more than 13 characters (including the .SAV)!</b>

The following example backs the BERN project/directory onto tape IMA001.  For large projects and/or critical projects, it is advisable to dedicate an entire tape.  The three dots (...) indicate that ALL subfolders of DK0:[MICROCT.PROJECTS.BERN] will be included.

<pre>
$ mount/foreign tp0:

$ backup/log dk0:[microct.projects.bern...]*.*;* tp0:proj_bern.sav -  ! writes a saveset to tape
        /block=65534 /label=IMA001 -
        /media_format=nocompaction     ! NEVER use the /rewind option here

$ backup/log tp0:*.sav/select=*.isq DISK4:[BONELAB.PROJECTS.TBONE.ISQ_FROM_TAPE...]/by=parent  ! extracts all ISQ files from the tape

$ dismount tp0:  
$ dismount tp0: /nounload ! same as previous command, but does not eject the tape (i.e. if you want to read the tape once more)
</pre>

Note that the <code>/rewind</code> option should never be used for backup as it instructs the tape drive to rewind after backup is complete causing a major risk of over writing.

Sometimes it might be handy to exclude certain files.  For example, to exclude RSQ files: <code>/excl=*.rsq</code>

A good reference for backup commands and ideas are available in the <code>UM:UCT_MOVE_FILES.COM</code> script which is used by the <code>UCT_BACKUP</code> program.  See also the <code>help backup</code> instructions:
<pre>
$ help backup
</pre>

To view the contents of a tape to ensure you've successfully stored your project use the following commands (further details in "HowTo: View save set (SAV) contents"):

To just view if the saveset is on tape (but not its contents):
<pre>
$ mount/ov=id tp0:
$ dir/date tp0:*.*
$ dismount tp0:
</pre>

Note: you can also save the saveset list in a text file using the /output qualifier.

To view the files within a saveset on tape, and save the results in a file called <code>results.txt</code> This .txt file can be found in IDISK1[XTREMECT2]:
<pre>
$ mount/foreign tp0:
$ backup/list=results.txt tp0:*.*
$ dismount tp0:
</pre>

To delete a set of directories, use the <code>dl</code> command.
<pre>
$ cd ur BERN
$ del *.*;*   ! Deletes ALL files in a directory
$ dl *.dir;*  ! Will only delete empty directories (not nested directories)
</pre>


[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]

=====Extract Project Saveset from Tape=====
To restore a project, you have two choices:
*1. Login as user <code>calibration</code> and then go to the projects directory. From there:
<pre>
$ spb (bypass priv)
$ backup/log tp0:proj_davison.sav/rewind [*...]
</pre>
This puts all the files back in their original directory structure.

*2. As user <code>microct</code>
<pre>
$ mount/foreign tp0:
 
$ backup/log tp0:proj_davison.sav/rewind/select=[microct.projects.davison...]
     disk2:[microct.projects.davison...]

OR

$ backup/log tp0:*.*/rewind disk3:[microct.projects.vitamink.models]
</pre>
Make sure to write the <b>same</b> path in the /select as the output (except for the 
actual disk2 portion).  Alternatively, you could unpack it into a slightly different root
directory (i.e., TMP) by changing the output path.

The three dots infers to use the same paths in the saveset as the file structure put onto disk.


[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]