Siemens SINUMERIK 840D sl Commissioning Manual page 847

The action "Save" or "Backup" creates a backup of the CF card in FILENAME. If the action is
used from a service system, the backup receives the files of the underlying controller, not of
the service system itself.
Archive and backup files larger than 4GB
If the Backup is written on a FAT32 target file system, no file size of more than 4GB is
permitted, then the Backup is divided into several files, which are correspondingly smaller
than this threshold value.
In the target file names, which are indicated during the call of"sc save", an indication is given
in this case which part of a number of backups it is and of how many files it consists: The call
of "sc save /tmp/backup.tgz" thus generates, for example, the files "/tmp/backup.01of02.tgz "
and "/tmp/backup.02of02.tgz ".
Options
The following options are used for selecting which directories of the file system are to be
written to the archive:
-full:
-addon:
-oem:
-user:
-addon+:
-oem+:
If "sc save" is used directly on the controller and the subsystems are running, this may lead
to inconsistencies between saved files, because they can still change during the backup
process. Therefore, in this case "sc save" normally ends in an error message to inform you
that subsystems are still running.
● If you want to create a backup anyway, you can use the -force option. "sc save" still
● The -update option writes an Img-D control file to the archive. This makes it possible to
Example:
sc save -user /tmp/drv01/backup.tgz
NCU operating system (IM7)
Commissioning Manual, 03/2013, 6FC5397-1DP40-3BA1
complete backup (default): all files of the controller, incl. Boot Loader
only /addon directory
only /oem directory
only /user directory (user data)
/addon, /oem and /user
/oem and /user
issues a warning, but the process continues. If "sc save" is started from the service
system, no subsystems of the controller are running and "-force" is not necessary.
use the archive at a later date via "sc restore -update".
Configuring the system
2.5 Description of the actions
51