Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Bash Help - Running Mover on the Backup Unraid Server

Featured Replies

This is what I'm working with:  I have my Main Unraid server backing up files on my Backup Unraid server.  It does this by a bash script using rsync.  There are SSH keys configured so the Main can write to the Backup server.  The Backup spends most of its time at sleep, with the script running on the Main waking the Backup server before executing the rsync.  The Backup server currently has no cache drive installed.  Writing directly to the array.  Backup server goes to sleep after 15 minutes of inactivity.

 

I'm thinking of installing a cache drive in the Backup server.  But the cache drive won't help if the Backup server is asleep at the scheduled Mover time.  So the question I have is:

 

Can the Mover be invoked on the Backup server by a command I can add to my script that is run on the Main server?  If so, what would that look like?

 

TIA

 

 

 

 

Why do you even want a cache drive on the backup server?  
 

Mover is going to be much slower at moving files to the array than rsync would be in writing files to the cache so the backup server would need to be powered on for significantly longer than when you run without the cache and write directly to the array.

 

Mover is designed to run in idle time when the server is powered on but not otherwise doing much.    From your description this is not how your backup server is expected to run.

 

  • Author
3 hours ago, itimpi said:

Why do you even want a cache drive on the backup server?  

 

To reduce the amount of time the Main server is transferring files/running the backup script.

 

The Backup server has only one function - a simple NAS that only is accessed by the Main server once a week.  I am not concerned of the extra power used by the Backup doing a two-stage write operation (writing to cache then move to array).  The transfer between Main and Backup servers would be significantly faster writing to SSD cache vs HDD array.

You can just add to your script:

 

/usr/local/sbin/mover

 

  • Author

My script runs on the Main server.  I wish to run the Mover on the Backup server after the rsync from Main -> Backup has completed.

 

@JorgeB Wouldn't adding /usr/local/sbin/mover to the script run the Mover on the Main server, and not the Backup server?

Edited by ConnerVT

3 minutes ago, ConnerVT said:

@JorgeB Wouldn't adding /usr/local/sbin/mover to the script run the Mover on the Main server, and not the Backup server?

It would, you can do:

ssh <backup server IP> "/usr/local/sbin/mover"

 

  • Author

Excellent.  Thank you!  That is just what I was looking for.

 

I had hoped it was as simple as this.  Generally, when I start thinking like this, it ends up costing endless hours of traveling down the wrong path to the simple solution.

😖

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.