Welcome, Guest. Please login or register.

Author Topic: Best Practices for Data Restoration 3.1.4  (Read 4772 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline AndyFC

Re: Best Practices for Data Restoration 3.1.4
« on: November 16, 2020, 07:05:25 PM »
I've written a very brief script, and tend to back up to an SD card although the script can backup any device/volume to any other device/volume. There's no logic to check time stamps or anything.

The script prompts for the source volume/directory and a destination volume/directory and clones the files, leaving a file in the root of the backup with the date and time of the backup.

The same script can be used to copy data back.
« Last Edit: November 16, 2020, 07:06:11 PM by AndyFC »
A1200 in DIY Tower. 3.2 ROMs (softkicking 3.2.3), OS 3.2.3, CF card, CD RW and IDE to SD adapter running off the internal IDE port (using the A4000 4-port IDE adapter from Amigakit), Pistorm 32 lite with Pi4/2GB/Emu68 or Blizzard 1230-IV, with 32MB 60ns RAM and 50MHz 68882 FPU.
MorphOS on PowerMac G5 and ATI 9600 pro
 

Offline AndyFC

Re: Best Practices for Data Restoration 3.1.4
« Reply #1 on: November 21, 2020, 09:15:42 PM »
I've tidied up my backup script and uploaded to Aminet.

QuickBackup (Beta) should be available from Sunday.
A1200 in DIY Tower. 3.2 ROMs (softkicking 3.2.3), OS 3.2.3, CF card, CD RW and IDE to SD adapter running off the internal IDE port (using the A4000 4-port IDE adapter from Amigakit), Pistorm 32 lite with Pi4/2GB/Emu68 or Blizzard 1230-IV, with 32MB 60ns RAM and 50MHz 68882 FPU.
MorphOS on PowerMac G5 and ATI 9600 pro
 
The following users thanked this post: lionstorm