Tape service

.yarnrc.yml

@@ -1 +1,6 @@
+approvedGitRepositories:
+  - "**"
+
+enableScripts: false
+
 nodeLinker: node-modules

docs/.vitepress/config.mts

@@ -919,9 +919,9 @@ function sidebarAdministerScience() {
           link: "/administer-science/data/",
         },
         {
-          text: "Tape archive",
+          text: "Tape backup",
           collapsed: true,
-          link: "/administer-science/data/tape-archive/",
+          link: "/administer-science/data/tape-backup/",
         },
         {
           text: "FAQ",

docs/administer-science/data/tape-backup/index.md

@@ -0,0 +1,49 @@
+---
+title: Tape Backup
+category: Data
+outline: 1
+description: This page gives information about how tape backup works using LTO tapes as a medium.
+---
+
+# What is tape backup
+
+Our tape service uses the LTO (Linear Tape-Open) format optimised for high capacity and storage density. LTO tapes provide a reliable way to store your data offline for maximum protection against malicious attacks such as ransomware. The tape service can also be used as a cost-effective way to maintain a backup of your lab data.
+
+## What is LTO tape
+
+LTO is a magnetic tape storage technology widely used for backup, archiving, and data transfer. As an open standard, LTO is not controlled by a single manufacturer, which promotes compatibility and innovation across the industry. Known for its reliability, capacity, and cost-effectiveness, LTO tapes are designed to store vast amounts of data securely over extended periods.
+
+## Reliability
+
+One of the standout features of LTO tapes is their exceptionally low error rate. With a bit error rate of just 1 error in 10^19 bits, LTO tapes are approximately 10,000 times more reliable than hard disks and 1,000 times more reliable than SSDs. This reliability is achieved through advanced error correction code (ECC) technology, which ensures data is written accurately and any errors are promptly detected and corrected. This makes LTO tapes an ideal choice for backup and archival purposes where maintaining data integrity over long periods is essential.
+
+## Security features
+
+LTO tapes are an excellent choice for storing sensitive data. One key feature is the ability to encrypt data on-the-fly, providing a strong defence against unauthorised access. Additionally, LTO tapes can be configured in a WORM (Write Once, Read Many) format, which prevents data from being altered or deleted once written. Another security aspect LTO tape offers is ability to store your data offline in a secure location. This way even if system and data is compromised, your data stays safe, inaccessible from the internet.  
+
+## Tape archive vs tape backup
+
+**Tape archive**
+
+A tape archive is a long-term storage solution for data that is no longer in regular use or data that requires extra safety measures to store. Archived data is typically stored offline for up to 10 years. Archive jobs are run in "Copy" mode, meaning your data is written to two separate tapes to ensure recoverability. After a successful write, archive tapes are removed from the tape library and stored offline in a secure location. Depending on dataset size, recovery may take additional time since the tapes need to be returned to the library manually.
+
+**Tape backup**
+
+Unlike tape archive, regular tape backup is designed to minimise costs while maintaining a high level of data integrity and security. Tape backups run automatically on a predetermined schedule and are retained for a predefined period. Recovery is usually much faster than with tape archive, although several factors can affect the recovery timeline.
+
+## Recovery from tape
+
+Recovery differs between tape archive and tape backup.
+
+In most cases, individual files can be recovered from a tape backup quickly. This is not always the case with a tape archive. If you need to recover a file within one year of the archive job, file-level recovery is possible. After one year, which is the most common scenario for archived data, a full job recovery is required. This is due to measures we take to manage the size of our backup catalog, which would otherwise grow indefinitely.
+
+## Tape backup software
+
+We are using bacula community edition which is an open source sofware that has been around and actively developed since January 2000. This sofware allows us to scale our tape service efficiently, reduce costs and maintain high level of data integrity and security.
+
+You can read more on bacula [here](https://en.wikipedia.org/wiki/Bacula).
+Official documentation of bacula can be found [here](https://docs.baculasystems.com/index.html)
+
+## How can I get my data on tape?
+
+You can start by visiting our [service desk](/administer-science/service-desk/lab-orders#tape-backup).

docs/administer-science/service-desk/lab-orders.md

@@ -439,15 +439,16 @@ Once data on volume is deleted, it can not be recreated. You must ensure that yo
 * **Expected response time:** Days
 * **Cost:** No additional costs.
 
-### Tape archive
+### Tape backup
 
-Click button below to order a long term archiving of your data
+Use below form if you wish to order a scheduled backup to tape or one-time archive of your data.
+If you want to learn more on what tape is and how it works, click [here]()
 
-<SDButton form="request_tape_archive" />
+<SDButton form="request_tape_backup" />
 
 * **Who can order:** Lab leader and coordinator.
-* **Required information:** size of dataset and retention period.
-* **Expected response time:** Weeks.
+* **Required information:** Size of dataset and retention period.
+* **Expected delivery time:** Up to 2 weeks.
 * **Cost:** Can be found in our [price list](/administer-science/prices/pricelist#current)
 
 

docs/public/cfg/service_desk.yml

@@ -2456,21 +2456,23 @@ request_update_data_rep:
     ]
   attachments: []
 
-request_tape_archive:
-  title: "Order tape archive"
+request_tape_backup:
+  title: "Order tape backup"
   template:
-    subject: "Tape write - {labname}"
+    subject: "Tape backup - {labname} - {tape_backup_type}"
     body: |
-      Hi HUNT Cloud team,  
+      Hi HUNT Cloud team,
 
-      I would like to order a tape archive for my dataset.  
+      I would like to order a tape backup for my lab.
 
       ---
-      Labname: {labname}  
-      Type of tape write: {tapewrite_type}
-      Size of dataset: {data_size} TB  
-      Description of dataset: {data_desc}  
-      Retention period: {retention}  
+      Username: {username}
+      Lab name: {labname}
+      Backup type: {tape_backup_type}
+      Scope: {tapewrite_type}
+      Size of dataset: {data_size} TB
+      Retention period: {retention}
+      Backup interval: {backup_interval}
       ---
 
       Let us touch base on Slack to discuss the details.
@@ -2495,42 +2497,84 @@ request_tape_archive:
         field: "textfield",
       },
       {
-        label: "Type of tape write",
+        label: "Backup type",
+        key: "tape_backup_type",
+        field: "autocompleteone",
+        options:
+          [
+            { text: "One-time tape archive", value: "Archive" },
+            { text: "Scheduled regular backup", value: "Scheduled" },
+          ],
+      },
+      {
+        label: "Scope of tape write",
         key: "tapewrite_type",
         field: "autocompleteone",
-        options: [{ text: "Full volume backup", value: "Full volume" }, { text: "Selected dataset backup", value: "Selected Dataset" }],
+        options:
+          [
+            { text: "Full volume backup", value: "Full volume" },
+            #{ text: "Selected dataset backup", value: "Selected dataset" },
+          ],
+      },
+      {
+        label: "Volume to back up",
+        key: "volume_target",
+        hint: "Select the volume. Leave as N/A for selected dataset backups.",
+        field: "autocompleteone",
+        options:
+          [
+            #{ text: "Not applicable (selected dataset)", value: "N/A" },
+            { text: "archive", value: "archive" },
+            { text: "archive2", value: "archive2" },
+            { text: "archive3", value: "archive3" },
+            { text: "work", value: "work" },
+            { text: "work2", value: "work2" },
+            { text: "work3", value: "work3" },
+            { text: "scratch", value: "scratch" },
+            { text: "scratch2", value: "scratch2" },
+            { text: "scratch3", value: "scratch3" },
+          ],
       },
       {
         label: "Size of dataset (in terabytes)",
         key: "data_size",
-        hint: "Field should include only numbers",
+        hint: "Estimated size of data to be written to tape.",
         suffix: "TB",
         min: 0.1,
         max: 25,
         step: 0.1,
         field: "number",
         default: 1,
       },
-      {
-        label: "Data set description (optional)",
-        key: "data_desc",
-        pattern: "^$|[-a-z0-9]{3,}",
-        default: " ",
-        hint: "You can describe type of data and how it is currently stored.",
-        autocapitalize: "off",
-        field: "textfield",
-      },
       {
         label: "Retention period",
         key: "retention",
-        pattern: "[-a-z0-9]{3,}",
-        hint: "How long should we store the data on tape (max 10 years for single tape write)",
-        suffix: "Years",
-        min: 1,
-        max: 10,
-        step: 1,
-        field: "number",
-        default: 5,
+        hint: "How long data is kept on tape before recycling.",
+        field: "autocompleteone",
+        options:
+          [
+            { text: "30 days", value: "30 days" },
+            { text: "3 months", value: "3 months" },
+            { text: "6 months", value: "6 months" },
+            { text: "1 year", value: "1 year" },
+            { text: "5 years", value: "5 years" },
+            { text: "10 years", value: "10 years" },
+          ],
+      },
+      {
+        label: "Backup interval",
+        key: "backup_interval",
+        hint: "For scheduled backups only. Select 'Not applicable' for one-time archive.",
+        field: "autocompleteone",
+        options:
+          [
+            { text: "Not applicable (one-time archive)", value: "N/A" },
+            #{ text: "Daily", value: "Daily" },
+            #{ text: "Weekly", value: "Weekly" },
+            #{ text: "Monthly", value: "Monthly" },
+            { text: "Quarterly", value: "Quarterly" },
+            { text: "Yearly", value: "Yearly" },
+          ],
       },
     ]