Sometimes it’s beneficial to know what commands/programs or services are run on the source machine when running Linux CloneManager via the Cristie Virtual Appliance, for instance, the privilages can then be assigned to an account for use in sudoers.
During the initial clone or subsequent sync, the credentials set in the job setup in the VA will be used to authenticate and log into the source system to run the job. The user will need sudo access so it can access all the files needed for a replication
Below is a complete lists: used for deployment; licensing; and replication.
awk
blkid
btrfs
btrfs-show-super
cat
chown
chmod
clonemanagercfg
cryptsetup
cut
cp
debugreiserfs
dmidecode
dmraid
dmsetup
docker
dpkg
fdasd
grep
iscsiadm
jfs_tune
licmgr
lspci
lvdisplay
lvs
mdadm
mkdir
modinfo
mokutil
multipath
mv
ntfsclone
netstat
parted
paste
powermt
pvdisplay
pvs
restorecon
rm
rpm
rsync
sed
service
ss
stat
systemctl
tar
tune2fs
udevadm
vgdisplay
vgs
xargs
xfs_admin
xfs_info
yum
zypper
Locations of Cristie folders and paths used in CloneManager:
/etc/cbmr
/var/log/cbmr
/run/cristie_postrec.pid
/run/systemd/generator.late/cristie_va.service.service
/run/systemd/generator.late/cristie_va_service.service
/sys/fs/cgroup/devices/system.slice/cristie_va.service
/sys/fs/cgroup/systemd/system.slice/cristie_va.service
/etc/systemd/system/multi-user.target.wants/cristie_va.service
/etc/systemd/system/cristie_va.service
/etc/rc.d/init.d/cristie_va.service
/usr/bin/cristie_va_service
/usr/lib64/dattobd/kmod-dattobd-0.10.15-4.19.154.cristie.x86_64.rpm
/usr/share/doc/cristie
/opt/cristie