Backup target without a drive letter for SECURITY
Posted: Fri Dec 04, 2020 8:03 am
When a system is hacked, they usually damage/delete/encrypt data on all available drive letters. Is there a way for R-Drive Image to backup to an NTFS partition without mounting a drive letter?
create /a /o -tid=vpegtcuvdppmgwnva8c8mah1 -s="hdd_vtype=real+hdd_port_num=0+part_size=1000104525824+part_ofs=16777216+part_id=2+part_fs=ntfs+part_mounted=E:\+hdd_target_id=1+part_label=NVMe-DATA2+hdd_name=HPT DISK 0_1 4.00+hdd_bus_type=fibre+hdd_size=1000123400192+hdd_num=8" -a="N:\WCIMAIL-E-DRIVE.rdr" -c=3 -u -bs -bs-apply-before -bs-num-b="2" -s-xr
This script shows it backing up to a file on N:, but can I provide -a= a different value that will target the same partition and place the file on that partition WITHOUT the OS having the drive letter mounted to the target partition? This would be ideal because it would throw off the hacker or script from the true location of the backup data.
Yes I did try creating two mvadd.cmd and mvdel.cmd 'backup aux applications', the scripts work fine if you run them in a command prompt or thru windows explorer to mount and unmount the drive letter, but if you add the scripts to the before and after of a backup schedule and have it run as administrator it still says 'drive does not exist'. I'm assuming r-driveimage checks for the drive letter BEFORE running the backup aux app script!
create /a /o -tid=vpegtcuvdppmgwnva8c8mah1 -s="hdd_vtype=real+hdd_port_num=0+part_size=1000104525824+part_ofs=16777216+part_id=2+part_fs=ntfs+part_mounted=E:\+hdd_target_id=1+part_label=NVMe-DATA2+hdd_name=HPT DISK 0_1 4.00+hdd_bus_type=fibre+hdd_size=1000123400192+hdd_num=8" -a="N:\WCIMAIL-E-DRIVE.rdr" -c=3 -u -bs -bs-apply-before -bs-num-b="2" -s-xr
This script shows it backing up to a file on N:, but can I provide -a= a different value that will target the same partition and place the file on that partition WITHOUT the OS having the drive letter mounted to the target partition? This would be ideal because it would throw off the hacker or script from the true location of the backup data.
Yes I did try creating two mvadd.cmd and mvdel.cmd 'backup aux applications', the scripts work fine if you run them in a command prompt or thru windows explorer to mount and unmount the drive letter, but if you add the scripts to the before and after of a backup schedule and have it run as administrator it still says 'drive does not exist'. I'm assuming r-driveimage checks for the drive letter BEFORE running the backup aux app script!