BackupAssist’s rsync ‘seed’ function explained

If you’ve ever used BackupAssist to run an rsync job to a remote NAS device, you may be familiar with the built in ‘seed’ function. This bypasses the need to run a large backup for the first time over the network and instead uses a USB hard drive to move the data manually. After the seed job has completed, the drive is disconnected from the BackupAssist server and plugged directly into whatever is performing the role of the rsync server. Often it’s a NAS device, but I also talk to customers who choose to run either a Linux server which has native rsync support or even a Windows box using the free open source CWRsync service.

By using the seed function, on a standard office Internet connection, administrators can see the first backup taking just a few hours rather than what could potentially have been a few days. The benefit here being it frees up the network for day to day use.

What does the seed function actually do?

When you run a seed job in BackupAssist, two tasks are performed. The first one takes a copy of the data to be backed up as a standard Windows file copy (preserving files and folders and the drive letter of the source). The second creates what’s known as a “bash script” file that can be used at the destination to move this copy of the data to the correct location.

Although it may not appear it at first glance, there’s actually more going on here than simply creating a copy of the data – so now we’ll take a closer look…

So what’s actually happening?

Once the seed job has finished in BackupAssist you’ll see a file’s been created called ‘’ in the root folder of your destination device. This is the bash script and is designed to be run on the destination Rsync server that your backup is configured to connect to.

Below is a sample bash script in its entirety:-

set -x
src=”`echo $0 | sed ‘s![^/]*$!!’`”
if [ -z “$src” ] ; then
mkdir -p “$dest”

rsync -av “$src” “$dest”

At first glance it may not make much sense if you’re not a Linux user, however it’s basically just executing the simple rsync command we see in isolation below.

rsync -av “$src” “$dest”  

Everything above that point in the code is there to configure the two variables for the source folder ‘$src’ (the current working directory the bash script is run from) and the destination folder ‘$dest’ (defined explicitly from the location given when setting up the rsync job in BackupAssist)..

What this shows is the ‘rsync’ command comparing two folders – the source (USB hard drive) and the destination folder where the backup should end up on the NAS. As the destination is blank, all files and folders are copied.

In addition to copying the files themselves by using the rsync command, file deltas are created for each, which are used by BackupAssist when the job runs again. It’s these deltas that are used to compare files being backed up and to work out which blocks of those files have changed. Only the changed blocks are sent over the network and used by the rsync server to re-construct the file, consequently far less bandwidth is used, making it ideal for those sites with low speed Internet connections.

How do I run the script?

To run the script you must be able to either log into your NAS using SSH (usually as the root user),  or if you’re using a Windows server you can use the excellent Putty tool to do this (see my “software tool of the week post” for info on this).

Once you reach the Linux shell, you’ll need to navigate to the mount point for the USB drive. The exact path for this differs with every NAS device so you may need to do some Googling if you struggle to find it.

In my example I’m using a Netgear ReadyNAS and the USB drive  path is ‘/USB/USB_HDD_6/’ but this may be different for your drive.


Once you’ve navigated to the root of the USB drive, simply run that script file with the command ‘./‘ and watch your files start copying. Time to make a cuppa…

6 thoughts on “BackupAssist’s rsync ‘seed’ function explained

  1. Hi. I seeded a remote backupasssist job and performed the first day’s update. Cool. Now I realize there are other directories that should be added to that backupset. How do I seed the new directories? Do I need to performs a complete reseed (takes a long time) or is there a way to do the incremental part only? Thanks for the help. Alex

    • Thanks for getting in touch Alex…

      If you edit the job and add the new directories, then reseed the job to the same portable destination device you seeded it to last time then providing the existing data still exists on that device then the job should only copy the new folders and changes to it (bear in mind it’s like a local Rsync job though so it still needs to analyse that destination for changes).

      Likewise, when you run the bash script on the destination it’s also like a local Rsync job so only changes or new files will be copied to the destination but you would still need to allow time for that data to be analysed for changes.

      The other option would be to take the destination NAS on-site so it’s local to BackupAssist and temporarily update the destination in the job so it’s the local IP of the NAS then run the job. Once complete set the destination in the job back to the external IP and take the NAS back to its remote location. The next time the job runs it will only copy changes in files and new files only.

      Hope that helps!

      • A local rsync… I see.

        I guess under no circumnstances would a normal copy of the seed directory work, right? Needs the processing to integrate the new with the previously existing files.

        Thanks James,


      • Hi Alex,

        The bash script process creates the required rsync delta’s on the destination which are used to determine if the file on the destination has changed or not.

        Just copying the folders manually won’t create these deltas so when you run the job after doing that the job would just copy the folders over again.


Let us know what you think....

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s