# xtar czlbf 1024 /Volumes/BackupDisk/backup.tgz. # xtar clbf 1024 /Volumes/BackupDisk/backup.tar. ) | (cd /Volumes/NewMacDisk xtar xbf 1024 -) Supports HFS disks with HELIOS volumes correctlyĬopy the Mac OS X HFS boot disk to a second HFS disk:

HFS de-composite Unicode file names are supported (umlauts, etc. “tar”-based on HELIOS resource file representation (can be restored by a new “tar”)Īllows duplication of Mac OS X HFS bootable disks HFS backup and creation time is saved (not available on UFS) hidden files, type and creatorįile / direcory IDs are saved and restored on HELIOS volumes HELIOS Xtar for Mac OS X can be scripted to easily let youįinder info is saved for files and directories, e.g. If the checkbox is enabled the copy would not be bootable (see following Figure). Important: On disks other than the boot disk, the checkbox “Ignore ownership on this volume” must remain unchecked! When a system cloning is done for that volume it is most important that the access rights are preserved. Rm, rmdir, mv, cp, set, ls, mkdir, touch, upd, chmod, chown, chgrp, idinfo, iddump “dt mv srcfile dstfile” will include the additional information and updates the desktop database so that “Aliases” are still valid, etc. On HELIOS EtherShare server installations, special UNIX desktop tools will take care of the additional resource and Finder information, e.g. Thanks to HELIOS Xtar, it works just fine. the volume is bootable after being restored. This means there is no missing data, e.g. During a restore with Xtar in an HFS volume, the resource and Finder information will be restored into a valid HFS file containing all information. HELIOS Xtar saves each HFS file as two files in the standard “tar” container format to preserve all additional information. rsrc/filename contains the resource fork, Finder info, etc. HELIOS always stores two files in its Xtar archive as well as in HELIOS EtherShare volumes, e.g.:įilename is the data fork whereas. device files, hard links, symbolic links, file and directory permissions, etc. HFS-compatible applications can deal with the additional resource and Finder information but they do not understand UNIX special files, e.g. For example, booting will not work, previews from EPSF files are missing, applications will not detect their own files anymore, etc. This means that the copies will be incomplete and many files will just refuse to work. resource file, creation and backup date, file comments, type & creator, hidden flags, etc.) gets lost using standard UNIX-based tools, such as “cp”, “cpio”, “tar”, “dump”, “pax”, “cat”, “dd”, etc. Finder and Resource information on HFS within one file, but standard UNIX applications can only see the data part, the additional information (e.g.

Disk utility clone