PCI compliance refers to the law around financial transactions, specifically credit/debit card transactions. A certain level of security is required in order to be allowed to facilitate these transactions. If you accept payments via credit card and want to run them through your sever, then the connection between your server and the payment network must have a minimum required level of security.
 
This security is encoded in the transfer protocol between your server and the payment network, which is called “Transport Layer Security”, also known as “TLS”. Because of recent changes in the law, you must have the most up-to-date version of TLS (at least version 1.2). You will fail a PCI compliance certification if you do not have the right version of TLS.
 
Additionally, this TLS update can affect some other programs on your server. Specifically, this can affect your ability to log in to your server remotely via a program called SSH (“Secure Socket Shell”). The most up-to-date version of SSH available on legacy versions of SCO (i.e., 5.05, 5.06, 5.07, 5.07V, and 6.0) does not play well with the necessary TLS version. Contact us to get a custom version of SSH that works with legacy versions of SCO that also meets PCI compliance standards.

You can create a tar archive to a file instead of a device such as a tape drive.  To save the /etc directory to a file called /tmp/myfiles.tar type the following.

tar cvf /tmp/myfiles.tar

This command working on SCO Xenix, SCO UNIX 3.2v4.2, 5.0, 5.2, 5.4, 5.5, 5,6,5,7 and 6.0.

Typing tar and enter will give you help on the command tar and default devices that command can use.   You can change your default by editing /etc/default/tar.

Key     Device             Block   Size(K)   Tape
 0      /dev/rfd048ds9      18      360       No
 1      /dev/rfd148ds9      18      360       No
 2      /dev/rfd096ds15     10      1200      No
 3      /dev/rfd196ds15     10      1200      No
 4      /dev/rfd0135ds9     18       720      No
 5      /dev/rfd1135ds9     18       720      No
 6      /dev/rfd0135ds18    18      1440      No
 7      /dev/rfd1135ds18    18      1440      No
 8      /dev/rct0           20         0      Yes
 9      /dev/rctmini        20         0      Yes
 10     /dev/rdsk/fp03d     18       720      No
 11     /dev/rdsk/fp03h     18      1440      No
 12     /dev/rdsk/fp03v21   10     20330      No

This is valid for all versions of SCO Xenix and SCO UNIX

tar tvf device name will list a tar backup.  Use tar and enter for default shortcuts to your devices. If you need to list a device listed in the shortcuts use the number.  For example for device 8, the tape drive, use tar tv8.  To list a tar backup into a file list the file name called /tmp/myfile.tar use the command tar tvf /dev/myfile.tar.

This command is valid for all versions of SCO Xenix and SCO UNIX.

The following command will backup the entire system using cpio to the tape drive that can be accessed by device /dev/rStp0.

find / -print -depth |cpio -ocdumbB -I /dev/rStp0

This cpio command should backup the entire system including the devices such as terminals and printers listed in the /dev directories.   This might not backup applications that have servers running in memory unless the service is shutdown during the backup.  We suggest you use a commercial backup software that does constant testing and improvements to their product for your system backup.

The following command will list the cpio backup to a file called /tmp/cpio.listing.

cpio -ivtB -I /dev/rStp0 >/tmp/cpio.listing

You can then use a viewer such as more to examine the file.

more /tmp/cpio.listing

The following command will extract a tape to the /tmp/tape.restore directory.

cd /tmp/tape.restore

cpio -icdumvB -I /dev/rStp0

This command might run your system out of free space.  This is also restoring to the /tmp/tape.restore directory and not your live system.  Restoring on file might cause a system to fail since a number of files might contain linked data.  Do a tape listing and just restore what you need using the following command.

cd /tmp/tape.restore

To restore a file

cpio -icdumvB -I /dev/rStp0 /u/usr/data/myfile

To restore a directory you must use a wildcard

cpio -icdumvB -I /dev/rStp0 /usr/*

We strongly recommend using commercial backup programs which allow for menu driven restore solutions that are more reliable than operating system utilities.

Edit the file /etc/edge.exclude and add the files or directories you want to exclude.  Below is an example of the contents of this file.

./usr/lib/edge/lists
./tmp_mnt
/usr/lib/edge/system/locks
/usr/lib/edge/system/pipes
/usr/lib/edge/system/tmp
/usr/lib/edge/system/pconfig/asyncn
/usr/lib/edge/config/devices.cda
/usr/lib/edge/system/mnt/*

A Backup Edge lockfile is created when a backup starts.  The lockfile might to continue to exist if a backup is hung in memory or the backup was interrupted by a system crash.  First verify the backup is not hanging in memory by typing  ps -ef|grep edge.

If a backup is hanging  in memory, a new backup will not start.  The current backup is logged in a directory called /usr/lib/edge/lists/backupname  There is a file called backup_system_master.txt and verify_system_master.txt which logs the backup and then the verify of the backup.  Review the last several lines of each of these two files for reasons why a backup will not complete.  Kill the backup or reboot the system to stop a backup stuck in memory.  Remove the file called schedule.lck from this directory to allow another backup to start.