|
|
|
|
| Welcome, Guest | Home | Search | Login | Register | |
| Author | QuicKeys to automate network backups (Read 13541 times) | ||||||||||||||
|
68040
512 MB ![]() ![]() ![]() ![]() ![]() Posts: 950 68k - thy kingdom come, thy will be done ! |
on: December 20, 2023, 19:13
I successfully finished my QuicKeys Pro sequence to - in combination with a tiny bit of AppleScripting - backup my volumes over a DAVE SMB share via Synchronice! Pro to network storage. The script auto-mounts the DAVE share, checks for the availability of the mount point and then launches the dir sync process via a preconfigured profile. The best part: I need to monitor none of it. It all happens auto-magically once I select the corresponding volume's sequence from the QK's Finder menu.
|
||||||||||||||
Last Edit: December 20, 2023, 19:16 by 68040
|
68040
|
512 MB ![]() ![]() ![]() ![]() ![]() Posts: 950 68k - thy kingdom come, thy will be done !
Reply #1 on: December 25, 2023, 22:49
|
Ha, I keep bugging you again: Added clean unmount, multiple error handlers and log file display to my QuicKey automated backup sequence. C'mon guys - classic MacOS is good for so much more than just playing Wumpus with it (as fun as that is).
|
Bolkonskij
|
Administrator 1024 MB ![]() ![]() ![]() ![]() ![]() Posts: 2023
Reply #2 on: December 26, 2023, 12:40
|
I fully agree. This sounds interesting, but with the few info given I'm having a hard time to envision it. So how do you initiate the process of backing up to your NAS? You hit a key-combo and leaning back while it does its thing? Or do you have a backup scheduled? (e.g. every evening at 11pm) How long does it take?
|
68040
|
512 MB ![]() ![]() ![]() ![]() ![]() Posts: 950 68k - thy kingdom come, thy will be done !
Reply #3 on: December 26, 2023, 13:53
|
QuickKeys uses its own terminology: * Single simulated commands or events are called "Shortcuts". * A group of shortcuts is referred to as a "Sequence". * Sequences may be recorded in real time (which means the QK macro recorder injects wait events and mouse clicks whenever the user pauses) or in "purified" form (no waits inserted). The main problem is that QK doesn't have a full fledged programming language, unless you use its build it Apple Script interpreter or launch a script file from opsys level. An added issue is that the build in AS interpreter as a few bugs of its own, which is why I rather avoid using that extension (its not a MacOS CDEV). An easy solution to that are the "wait (for)", "goto" and "go sub" instructions. Also, you may copy/paste values in and out of the clipboard, thus passing on success/failue info between parts of your Seqeunce code. This way you can fine control the command flow within your Sequence, based on what happens on screen. You can start a Sequence or a shortcut with a hotkey combination, by timer, opsys even or from the pull down menu. You can inspect any window for content, buttons, check boxes and manipulate the same, too. You can simulate keyboard input or wait for a specific opsys event to occur. So, for the backup I created a link to a DAVE share on my Desktop and then have QuicKeys try to open it. If its not already mounted a popup dialog appears, asking for my login credentials. QK simulates the keyboard input for me and then goes on to launch Synchronize! Pro, if the mount was successful. Next, I tell Sync! Pro what profile to use to synchronize a specific drive to backup (for that I just open the stored profile in the QK Sequence). I have several "jump" instructions in case an(y) error window pops up, branching to different parts of my Sequence to deal with that. Then I tell Sync! Pro via QK to display the log file at the end of the synchronization process (which I do by waiting for the status window to close). Finally I auto-dismount the network share by setting the corresponding value in Sync! Pro (=> dismount when done). The first backups always take the longest (100% sync rate). Currently I am on my second volume: 1.7GB (of changed data) in roughly 18 hours. But the neat thing about this process is that it can be interrupted at any time and continued later on w/o any loss of data.
Last Edit: December 26, 2023, 14:04 by 68040
|
|
Pages: [1]
|
| ||||
|
© 2021 System7Today.com. |



