rsync doesn't sync to remote server, but rather the source machine's boot volume

    After 'successfully' syncing my RAID1 array to a backup server of mine, I thought it was fine. Until I discovered my boot volume was full when it wasn't a couple hours ago.

    Turns out rsync synced my data to the boot volume instead of the destination server that I excplicitly specified in the job I set up.


    Is there any way to actually get the data to move to the destination server?

    Thanks

    Crazy person.

    MAIN: HP DL360e Gen8, 1x Xeon E5-2407v1, 8GB 1333MHz ECC, 500GB RAID1 - OMV5 (All-purpose)

    BACK: HP ML110 G6, Xeon X3430, 3GB 1333MHz ECC, 500GB RAID1 - OMV5 (Storage array backup)

    Exactly how and where was the target backup server specified?

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Zitat von gderf

    Exactly how and where was the target backup server specified?

    It was specified in the destination box as '[HELIUMSYNC@]192.168.0.39:STORAGEBAK'.


    Right now I've 'fixed' it by doing a weird route through the Remote Mount plugin, but I doubt this is a good way to go about it.

    Crazy person.

    MAIN: HP DL360e Gen8, 1x Xeon E5-2407v1, 8GB 1333MHz ECC, 500GB RAID1 - OMV5 (All-purpose)

    BACK: HP ML110 G6, Xeon X3430, 3GB 1333MHz ECC, 500GB RAID1 - OMV5 (Storage array backup)

    Sounds like the destination was some sort of created mountpoint that rsync writes to, but if the device that is being mounted isn't mounted, the mountpoint, usually a directory, will be written to instead. That can cause the drive to fill up.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden