Table of Contents
c.backup
Backup Structure
The backup feature creates a βmetacopyβ of each PLATO found file on the source
filesystem and stores a display code
version of the file in a parallel directory and file structure on the host filesystem.
This structure may then be placed under source control (such as GIT, Mercurial, or other modern source control systems) and 'diff'ed and 'version'ed, just like any other source file.
Caveats
The display code
format (just like the PLATO/NOS files themselves) has no notion of βline endsβ as we think of them today. Editing these files requires that you must know exactly what you're doing, or simply look, but don't touch.
Creating the Backup
Using the example CYBIS/R1
directory structure:
Create a new directory called Backups
:
Now issue the following command:
cdc.io c.backup -c "E:\Emulation\TH.CybisRelease1\Disks" -b "E:\Emulation\TH.CybisRelease1\Backups"
For each disk pack found in E:\Emulation\TH.CybisRelease1\Disks
, each Master File is re-created in a host-based directory structure.
For each master file found, a message will be sent indicating the current transfer operation being performed, and the characteristics of the capsule being created:
Tip
This process takes a while. Be patient.
When the backup is complete - the Backups
directory now contains a special structure establishing the backup capsule, for each found master file.
An example of the structure created for master file system5 looks like this:
Each .txt
file contains the display code
representation of the on-disk original file.
Success
These files may now be placed under source control!
About Backup Clusters
To CDC.IO
, Backup Clusters are no different than any other cluster type. They may be cataloged, compared, and participate in file print/copy/restore operations, just like any other cluster.