![]() Step 5: Tell Arq to run the script before starting backup Next, run your script in Terminal: ~/Desktop/MountNas.sh If it’s already mounted, go to the Finder and click the button to “eject” (unmount) it. Step 4: Test the scriptįirst, make sure your NAS isn’t already mounted by running: mountĪnd checking the output for your NAS. Step 3: Make the script executableīack in Terminal, type: chmod +x ~/Desktop/MountNas.sh Pick File->Save from TextEdit’s menu and save your file as “MountNAS.sh” on your Desktop. Password -> your account password on the NAS User -> your account name on the NAS from Step 1 Osascript the name of the NAS device from Step 1īignas (in 2 places!) -> the name of the NAS share from Step 1Īfp -> the protocol found in Step 1 (“afp” if you see “afpfs” in Step 1 “smb” if you see “smbfs” in Step 1) # Otherwise, the osascript will pop up an unwanted dialog. # If the NAS isn't reachable via ping, exit 1. Then copy/paste the following into Text Edit: #!/bin/bash Click the Format menu and pick “Make Plain Text”. Open TextEdit and click New Document to create a new text file. Let’s make a script that mounts your NAS. “afpfs” -> the protocol used to connect to it.“bignas” -> the name of the NAS share on the NAS device.“stefan” -> the account name used to connect to the NAS device.To recap, the key items in that line are: The “afpfs” tag means the Finder mounted it using AFP if you see “smbfs” instead, it means the Finder mounted it using SMB. The Finder mounted it at /Volumes/bignas. I connected to it with the username “stefan”. In my case, my NAS is called “big” and the share on it is called “bignas”. One of the lines in the output will mention your NAS and look something like this: on /Volumes/bignas (afpfs, nodev, nosuid, mounted by stefan) To find out how, browse to your NAS volume in the Finder then open the Terminal app and type mountĪnd press Return. When you connect to your NAS to your Mac by browsing to it in the Finder, the Finder takes care of “mounting” the NAS volume for you. Step 1: Figure out how the Finder mounts your NAS So, if you want to back up, say, a NAS that isn’t always connected, you may need to tell Arq to connect to the NAS first. NAS Backup on MacĪrq will back up whatever folders you tell it to back up, but it doesn’t know where those folders really exist on your Mac. Arq 6 will take care of mounting the NAS for you. Please note: This article only applies to Arq 5. (For Windows skip to the “NAS Backup on Windows” section.) And you have full control over when the scripts run.Arq can backup NAS shares. You can customize different scripts for different backup jobs. You can have as many scripts running, on any schedule, as you’d like. If it sees messages, it moves them to trash (deleted in 30 days). If it doesn’t see any messages in “backup-logs”, then it generates an E-Mail. Then I have the following (super simple) code running on Google servers. If it does not have “(0 errors)”, then it sticks in my inbox. If it has “(0 errors)” in the subject, then a Gmail filter puts it in “backup-logs” and removes it from Inbox. To answer your question, the date/time of the generated E-Mail from Arq (sent when a backup job completes) serves as the backup date (the “ping”, if you will, that the backup ran). Once my conversion is completed, I’ll make trivial changes for Duplicacy once I decide what my scripting will generate. I’ll run this until I complete my conversion. The below is for Arq Backup (I’m migrating from Arq to Duplicacy so I can pick up Azure as a target). Not sure how I feel about a “one-man show”. Using is interesting, I wasn’t aware of that.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |