BACKUPMON BACKUPMON v1.8.20 -Oct 12, 2024- Backup/Restore your Router: JFFS + NVRAM + External USB Drive! CIFS/SMB/NFS! (Thread Closed!)

[visortgw]

And that's the problem, I can't mount another one. I even tried with SMB 1.0.

mount -t cifs \\\\192.168.1.2\\NetBackup /tmp/mnt/netbackup/ -o "username=*********,password=*********,vers=2.0"
mount: mounting \\192.168.1.2\NetBackup on /tmp/mnt/netbackup/ failed: No such device

Try creating mount point via command line: mkdir /tmp/mnt/netbackup

$ls -al /tmp/mnt
drwxrwxrwx    7 TheS1R   root           160 Oct 24 00:35 .
drwxrwxrwx   29 TheS1R   root          3160 Oct 24 09:22 ..
drwxrwxrwx    2 TheS1R   root            40 Oct 23 11:08 NetBackup1
drwxrwxrwx    2 TheS1R   root            40 Oct 24 00:35 NetBackup2
drwxrwxrwx    6 TheS1R   root          4096 Jun 20 18:18 TheS1RsUSB
drwxrwxrwx    8 TheS1R   root          4096 Jun 29 03:09 bckupTheS1R
drwxrwxrwx    2 TheS1R   root            40 Dec 31  1969 defaults
lrwxrwxrwx    1 TheS1R   root            16 Dec 31  1969 nvram -> /mnt/defaults/wl
# mount -t cifs \\\\192.168.222.5\\NetBackup /tmp/mnt/NetBackupDoesNotExist/ -o "username=rsyncUser,password=rsyncPassword"
mount: mounting \\192.168.222.5\NetBackup on /tmp/mnt/NetBackupDoesNotExist/ failed: No such file or directory
# mount -t cifs \\\\192.168.222.5\\NetBackup /tmp/mnt/NetBackup1/ -o "username=rsyncUser,password=rsyncPassword"
# ls /tmp/mnt/NetBackup1/
TheS1RsGT-AXE16000  TheS1RsGT-BE98Pro
# umount /tmp/mnt/NetBackup1
# ls -al /tmp/mnt
drwxrwxrwx    7 TheS1R   root           160 Oct 24 00:35 .
drwxrwxrwx   29 TheS1R   root          3160 Oct 24 09:23 ..
drwxrwxrwx    2 TheS1R   root            40 Oct 23 11:08 NetBackup1
drwxrwxrwx    2 TheS1R   root            40 Oct 24 00:35 NetBackup2
drwxrwxrwx    6 TheS1R   root          4096 Jun 20 18:18 TheS1RsUSB
drwxrwxrwx    8 TheS1R   root          4096 Jun 29 03:09 bckupTheS1R
drwxrwxrwx    2 TheS1R   root            40 Dec 31  1969 defaults
lrwxrwxrwx    1 TheS1R   root            16 Dec 31  1969 nvram -> /mnt/defaults/wl

 

[bidh]

@bidh

This was done in error on firmware versions 3006 and has since been resolved on Merlin firmware.
As mentioned by @RMerlin here: https://www.snbforums.com/threads/a...vailable-for-wifi-7-devices.90487/post-914044
And in commit: https://github.com/RMerl/asuswrt-merlin.ng/commit/d483436bfd11524125afab4ae1e5551116a27f8d

Of course, the removal on the 3006 has no impact on your 3004 firmware. Even when it comes to 3004.388.8_2 cifs works without issue on Merlin firmware.
If it's missing on Gnuton I would open an issue on the Gnuton GitHub.

As I said cifs.ko is missing and I already notified it on github.
And nfs.ko is apparently also missing from that firmware on that router.

I reused the same mount point to check if the problem was the communication to the NAS or creating the mounting point.

[B]visortgw[/B]:

Try creating mount point via command line: mkdir /tmp/mnt/netbackup

I created the folder before trying mount -t cifs.
So, I'll stick on doing backups on that 2d partition, partition that can be accessed on the network.

For the record, I am now using Synology Active Backup to backup on the NAS the backup folder from the AX58Uv2 smb fileserver.
Without any trouble.

Thanks for your time.

 

[Ripshod]

Does backupmon create a log file (TL;DR)? While troubleshooting a seperate problem I noticed autopurge has not been working on my setup, even though it's enabled and set for 30 days my NAS still retains daily backups going all the way back to June.
My config:

BTUSERNAME="*****"
BTPASSWORD="***************"
UNC="\\\\10.0.0.15\\backup"
NFSMOUNTOPT=""
UNCDRIVE="/tmp/mnt/backups"
EXTDRIVE="/tmp/mnt/asus"
EXTLABEL="asus"
BKDIR="/Network/Router"
BACKUPMEDIA="Network"
EXCLUSION="/jffs/addons/backupmon.d/exclusions.txt"
BACKUPSWAP=0
SMBVER="3.02"
SCHEDULE=1
SCHEDULEHRS=2
SCHEDULEMIN=10
SCHEDULEMODE="BackupAutoPurge"
FREQUENCY="P"
MODE="Basic"
PURGE=1
PURGELIMIT=30
AMTMEMAIL=1
AMTMEMAILSUCCESS=0
AMTMEMAILFAILURE=1
SECONDARYSTATUS=1
SECONDARYUSER="gilly"
SECONDARYPWD="UmUyNDY1ODI1NSEK"
SECONDARYUNC="\\\\10.0.0.15\\removeable"
SECONDARYNFSMOUNTOPT=""
SECONDARYUNCDRIVE="/tmp/mnt/secondarybackups"
SECONDARYBKDIR="/Router_Backups"
SECONDARYBACKUPMEDIA="Network"
SECONDARYEXCLUSION="/jffs/addons/backupmon.d/exclusions.txt"
SECONDARYFREQUENCY="P"
SECONDARYMODE="Basic"
SECONDARYPURGE=1
SECONDARYPURGELIMIT=30

Any thoughts?

 

[Ripshod]

D'oh!!
My excuse is I don't have to access backupmon when it's (apparently) running fine, so I totally forgot about the log. Nothing is standing out and no mention of purging (successful or not).

 

[Viktor Jaep]

D'oh!!
My excuse is I don't have to access backupmon when it's (apparently) running fine, so I totally forgot about the log. Nothing is standing out and no mention of purging (successful or not).

What commandline are you using to run the backup job?

You could also try going into "backupmon -setup" and trying a manual purge to see what it says?

 

[Ripshod]

What commandline are you using to run the backup job?

The backup is in the early hours via cron

10 2 * * * sh /jffs/scripts/backupmon.sh -backup #RunBackupMon#

You could also try going into "backupmin -setup" and trying a manual purge to see what it says?

Manual purge runs fine and clears backups older than 30 days, as per my settings. Autopurge does not.
If this can't be solved it doesn't matter too much - ready for a reset and reinstall this weekend.

 

[Viktor Jaep]

The backup is in the early hours via cron

10 2 * * * sh /jffs/scripts/backupmon.sh -backup #RunBackupMon#

Manual purge runs fine and clears backups older than 30 days, as per my settings. Autopurge does not.
If this can't be solved it doesn't matter too much - ready for a reset and reinstall this weekend.

So weird. It's working fine on my end, basically using the same settings and command. Try running a manual "backupmon -backup" and keep your eye on the screen. It does the purges at the end. See anything that stands out?

 

[Ripshod]

Nothing to see. No mention of the purge even starting.
I'm going to reinstall everything right now, errors are cropping up in other areas (VPN clients etc)

 

[bibikalka]

So I was playing with an AiMesh node - and a question came up if it's possible to tweak backupmon to run without Entware installed?

Are there some unique executables that are needed that Entware provides? Alternatively, one could just send the backup files to some other place with network.

 

[Viktor Jaep]

So I was playing with an AiMesh node - and a question came up if it's possible to tweak backupmon to run without Entware installed?

Are there some unique executables that are needed that Entware provides? Alternatively, one could just send the backup files to some other place with network.

Backupmon does not have any entware-specific binary requirements... should run all on its own. However, if you're looking at using the AMTM email functionality, there may be some entware requirements from that aspect... but that's just a guess. I believe others are using backupmon on their iMesh nodes, and sending their backups to some central repository.

 

[Martinski]

... However, if you're looking at using the AMTM email functionality, there may be some entware requirements from that aspect... but that's just a guess.

The current email library functionality (using AMTM email configuration file) requires only the F/W built-in binaries (e.g. curl & openssl) to work. No Entware packages are needed at all.

FYI.

 

[abcxyz]

Can I use BACKUPMON to to backup to remote server outside router network?

 

[bibikalka]

@Viktor Jaep @Martinski

Alright, looks like I confused backupmon and rtrmon! backupmon is indeed fine, just needs to be configured correctly. rtrmon does want Entware!

 

[Viktor Jaep]

@Viktor Jaep @Martinski

Alright, looks like I confused backupmon and rtrmon! backupmon is indeed fine, just needs to be configured correctly. rtrmon does want Entware!

View attachment 62163
View attachment 62164

Yep, rtrmon definitely needs some entware tools to function completely.

 

[bibikalka]

Yep, rtrmon definitely needs some.entware tools to function completely.

One of these days I'll try to run rtrmon on the AiMesh node, and see what's missing. It's actually one of the more interesting addons that an AiMesh node could use!

 

[BrimoXD99]

I have set Perpetual Backup Retention and then: Purge Backups older than 90 days but it doesn't seem to work.
I see in target folder 114 subfolders:

Even when I count number of folders starting from 03.07.2024 up to today it is 109 folders = 109 backups - still more than 90.
Error log (ve) says nothing about issues with purging older than 90 days backups, the same with "normal log" (vl)
It doesn't look like a problem with permissions:

[EDIT] OK, I see where the problem is: Scheduled Backup Mode. I set it to "1 - Backup Only" but it should be 2 - "Backup + Autopurge" Sorry for "false positive" report

 

[Viktor Jaep]

[EDIT] OK, I see where the problem is: Scheduled Backup Mode. I set it to "1 - Backup Only" but it should be 2 - "Backup + Autopurge" Sorry for "false positive" report

Whew... nice find. You had me worried there for a sec!

 

[JTnola]

@Viktor Jaep do you happen to have directions for the use case scenario of transferring everything from a USB key to a SSD enclosure type situation? If not, I’ll figure it out. But I figured I’d check first. Thanks for this/everything!!

 

[Viktor Jaep]

@Viktor Jaep do you happen to have directions for the use case scenario of transferring everything from a USB key to a SSD enclosure type situation? If not, I’ll figure it out. But I figured I’d check first. Thanks for this/everything!!

No, you could do it, but may take a bit of manual work. It may be easier to copy your backup to a network location, then unplug the USB key, attach the SSD, make sure the label names are the same, and go through the standard restore process.

 

[JTnola]

No, you could do it, but may take a bit of manual work. It may be easier to copy your backup to a network location, then unplug the USB key, attach the SSD, make sure the label names are the same, and go through the standard restore process.

So, to be clear, as long as I use identical naming, the backup of my thumb drive could run on a completely diff device … a SSD enclosure type scenario … and everything will be hunky-dory…?