Table of Contents
Copy Modes
Overview
cdc.io was created to overcome the limitations of working with containers. By default, dtCyber opens the container files in shared-write-binary mode which enables the possibility of other applications performing options on the active “disk packs”. The practice can be very convenient, but also very dangerous.
The following Modes are indicated by the cat.compare function and should be self-describing.
Modes
About: LIVE COPY
Unless you know exactly what you are doing, you should refrain from copying into a running system.
The following table provides some guidance, but it is always better to be safe than sorry.
| Mode | Notes |
|---|---|
| AUTO(copy in-place) | Files with this mark are of equal size and may be copied to an active system. CONDITIONS
Copying files with this mark require caution. It is possible to do a safe transfer IF and ONLY IF the file contains NO EM 1) resident elements such as |
| AUTO(create) |
Files with this mark indicate that the file is not found on the opposing cluster. While Danger Files with this mark must NEVER be transferred to a running system. |
| REALLOC([A|B] is larger) |
Files with this mark indicate that the file allocations differ. While Danger Files with this mark must NEVER be transferred to a running system. |