hello and thanks for reading this,
i did try to figure this out myself and searched the internet.
i did find an api for filestation.
i need a way to run/trigger a hybrid backup from another computer.
i tried ifttt but that did not work.
is there an a way to run a backup via command line, api, sending https put, ssh, wget or what?
thanks much,
david
run backup via api, ssh,commandline, https put, wget
-
- New here
- Posts: 9
- Joined: Sun Mar 11, 2018 5:06 am
- OneCD
- Guru
- Posts: 12140
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: run backup via api, ssh,commandline, https put, wget
To run an established Hybrid Backup Sync job, first find the internal job name for your particular backup job from [/etc/config/qsync/qsync.conf]. Each internal job name is shown in square brackets, and precedes the job parameters, like this:
So, this is 'Job0'
Then, to execute this job manually, SSH in as the 'admin' user and run:
If you'd like to detach your terminal while this backup runs, background the job at launch:
Code: Select all
[Job0]
Name = Local Backup 1
StorageID = Storage0
ProfileID = Profile0
...
Then, to execute this job manually, SSH in as the 'admin' user and run:
Code: Select all
qsync -J:Job0
Code: Select all
qsync -J:Job0 &
-
- Getting the hang of things
- Posts: 52
- Joined: Sat Sep 05, 2009 7:08 pm
- Location: Amsterdam (Netherlands)
Re: run backup via api, ssh,commandline, https put, wget
Thank you for this information. However, when I do this, QNAP says COMMAND NOT FOUND.OneCD wrote: ↑Wed Jan 09, 2019 5:04 pm Then, to execute this job manually, SSH in as the 'admin' user and run:If you'd like to detach your terminal while this backup runs, background the job at launch:Code: Select all
qsync -J:Job0
Code: Select all
qsync -J:Job0 &
sudo find -name qsync -type f
found an executable in /share/CACHEDEV1_DATA/.qpkg/HybridBackup/bin/qsync/qsync
CD't to that directory and started the command with ./qsync -J:Job0
gives error
./qsync: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
Do you have suggestions?