BACKUPMON BACKUPMON v1.5.10 -Mar 1, 2024- Backup/Restore your Router: JFFS + NVRAM + External USB Drive! (**Thread closed due to age**)

[visortgw]

@Viktor Jaep Can you please look into disabling scheduled backups? If I turn them off and then save settings, they are re-enabled.

 

[Viktor Jaep]

@Viktor Jaep Can you please look into disabling scheduled backups? If I turn them off and then save settings, they are re-enabled.

I can't seem to replicate this. When I disable my scheduled backups, the option shows correctly in the menu... shows correctly in the backupmon.cfg file, and the entry is removed from the service-start file. Can you specify some steps on how you can repeat this?

 

[visortgw]

1. Disable via menu.
2. Save (cron entry is removed).
3. Return to setup.
4. Schedule shows as enabled (config file shows value of "1" as well).

 

[Ripshod]

1. Disable via menu.
2. Save (cron entry is removed).
3. Return to setup.
4. Schedule shows as enabled (config file shows value of "1" as well).

Reboot after dsabling - I think the cron is still active even though the entry is removed from services-start.

Edit: Just disproved myself, ignore that.

 

[Viktor Jaep]

Reboot after dsabling - I think the cron is still active even though the entry is removed from services-start.

The script removes it from both the services-start file and from cru... I'm not finding any traces after disabling the scheduler. I've tried your steps, but they work for me, and doing what is expected.

EDIT1: Could you have a manual cron job in there that's not called "RunBackupMon" by chance?

EDIT2: Could there be a permissions issue on the backupmon.cfg file, where it's not able to write changes, or are you able to manipulate the file with other changes?

 

[visortgw]

The script removes it from both the services-start file and from cru... I'm not finding any traces after disabling the scheduler. I've tried your steps, but they work for me, and doing what is expected.

Could you have a manual cron job in there that's not called "RunBackupMon" by chance?

The cron job goes away as it should, but the menu shows enabled when I go back into setup.

 

[visortgw]

The script removes it from both the services-start file and from cru... I'm not finding any traces after disabling the scheduler. I've tried your steps, but they work for me, and doing what is expected.

EDIT1: Could you have a manual cron job in there that's not called "RunBackupMon" by chance?

EDIT2: Could there be a permissions issue on the backupmon.cfg file, where it's not able to write changes, or are you able to manipulate the file with other changes?

Permissions are set to 666. Other changes apply correctly.

 

[Viktor Jaep]

The cron job goes away as it should, but the menu shows enabled when I go back into setup.

Make sure you are saving... I can replicate this if I don't save and press "e".

To replicate what you are seeing on my end:
1. Go into config
2. Press 8 for scheduler
3. Press 0 to disable scheduler
4. Press "e" to exit and discard changes

When you go back into backupmon -> config, it will show the scheduler as enabled, but the services-start and cru entries are deleted, but it never saved the changes to the scheduler entry to the config.

To replicate what I'm seeing:
1. Go into config
2. Press 8 for scheduler
3. Press 0 to disable scheduler
4. Press "s" to save config and exit

Now when you go back to the config screen, it shows the scheduler as disabled... the services-start and cru entries are deleted, and the backupmon.cfg was saved correctly.

 

[visortgw]

Make sure you are saving... I can replicate this if I don't save and press "e".

To replicate what you are seeing on my end:
1. Go into config
2. Press 8 for scheduler
3. Press 0 to disable scheduler
4. Press "e" to exit and discard changes

When you go back into backupmon -> config, it will show the scheduler as enabled, but the services-start and cru entries are deleted, but it never saved the changes to the scheduler entry to the config.

To replicate what I'm seeing:
1. Go into config
2. Press 8 for scheduler
3. Press 0 to disable scheduler
4. Press "s" to save config and exit

Now when you go back to the config screen, it shows the scheduler as disabled... the services-start and cru entries are deleted, and the backupmon.cfg was saved correctly.

Using latest beta:

1. cat backupmon.cfg. SCHEDULE=1.
2. Go into config.
3. Press 8 for scheduler.
4. Press 0 to disable scheduler. Shows disabled (i.e., "No").
5. Press "s" to save config and exit.
6. cat backupmon.cfg. SCHEDULE=0.
7. Go into config. It shows enabled (i.e., "Yes").
8. Exit without saving.
9. cat backupmon.cfg. SCHEDULE=1, but no cron entry.

 

[Viktor Jaep]

Using latest beta:

1. cat backupmon.cfg. SCHEDULE=1.
2. Go into config.
3. Press 8 for scheduler.
4. Press 0 to disable scheduler. Shows disabled (i.e., "No").
5. Press "s" to save config and exit.
6. cat backupmon.cfg. SCHEDULE=0.
7. Go into config. It shows enabled (i.e., "Yes").
8. Exit without saving.
9. cat backupmon.cfg. SCHEDULE=1, but no cron entry.

I still can't replicate that. Make sure you don't have a conflicting backupmon.cfg file sitting in your /jffs/scripts folder... that may be messing with your settings. If you do, delete it.

 

[Kingp1n]

@Viktor Jaep

I havent kept up with the updates but if I have 2 partitions (both labeled) in my 1 SSD connected (one has all my scripts i.e. Diversion/Skynet etc....); will the script allow me to save a backup to the NTFS side partition or that was never implemented with the recent updates, correct?

 

[visortgw]

I still can't replicate that. Make sure you don't have a conflicting backupmon.cfg file sitting in your /jffs/scripts folder... that may be messing with your settings. If you do, delete it.

That was it — a stray conflicting backupmon.cfg file in /jffs/scripts. I deleted it, and all is well.
I apologize for wasting your precious time.

 

[Viktor Jaep]

That was it — a stray conflicting backupmon.cfg file in /jffs/scripts. I deleted it, and all is well.
I apologize for wasting your precious time.

Whew! Yeah it wasn't until a later version that I was checking for that file and deleting it after a restore right before it reboots. Must have been a straggler!

EDIT: I'll see if there are some other opportunities to try to delete this file if I'm sure it's not being used for recovery activities... so these instances don't happen again in the future.

 

[Viktor Jaep]

@Viktor Jaep

I havent kept up with the updates but if I have 2 partitions (both labeled) in my 1 SSD connected (one has all my scripts i.e. Diversion/Skynet etc....); will the script allow me to save a backup to the NTFS side partition or that was never implemented with the recent updates, correct?

Well... "theoretically", if you can map a network drive to a folder on that second partition, you could backup from one partition to the other on the same SSD.

 

[visortgw]

Please give this a shot, @Quoc Huynh! Let's see if your USB drive stays mounted after a backup now!

What's new?
v1.32b2 - (TBA)
- ADDED: For the capability to distinguish between directly attached USB backup devices, and network backup devices using a new menu item, available in the config menu. (See item #6). When specifying the path to your Backup Target, you will also need to indicate whether it is a "Network" or "USB" target. In the case of a USB Backup Target (directly attached to your router), the script will no longer unmount the device after a backup has been completed. By default, "Network" is selected. Thanks much to @Quoc Huynh for the helpful suggestion!

Download link:

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/BACKUPMON/master/backupmon-1.32b2.sh" -o "/jffs/scripts/backupmon.sh" && chmod 755 "/jffs/scripts/backupmon.sh"

Significant screenshots:

View attachment 53969

I reconfigured backupmon to backup to second external USB drive. It works perfectly, except for some of the logging messages. In the following output, any reference to 192.168.222.5 are inaccurate as they do not apply for Target Media Type of USB. Functionally, it just works — just some cleanup of messages for USB-to-USB backup!:

BACKUPMON v1.32b2

Normal Backup starting in 10 seconds. Press [S]etup or [X] to override and enter RESTORE mode

Asus Router Model: GT-AX6000
Firmware/Build Number: 3004.388.5
External USB Drive Mount Path: /tmp/mnt/TheS1RsUSB
Backing up to \\192.168.222.5\NetBackup mounted to /tmp/mnt/bckupTheS1R
Backup directory location: /TheS1RsGT-AX6000
Frequency: Monthly
Mode: Basic

[Primary Backup Commencing]...

Messages:
STATUS: External Drive (\\192.168.222.5\NetBackup) mounted successfully under: /tmp/mnt/bckupTheS1R
STATUS: Finished backing up JFFS to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000/06/jffs.tar.gz.
STATUS: Finished backing up NVRAM to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000/06/nvram.cfg.
STATUS: Finished copying routerfw.txt to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000/06/routerfw.txt.
STATUS: Starting backup of EXT Drive on Mon Nov  6 13:52:58 EST 2023. Please stand by...
STATUS: Finished backing up EXT Drive in 18 sec to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000/06/TheS1RsUSB.tar.gz.
STATUS: Finished copying backupmon.sh script to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000.
STATUS: Finished copying backupmon.cfg script to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000.
STATUS: Finished copying exclusions script to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000.
STATUS: Finished copying reference nvram.txt extract to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000.
STATUS: Finished copying restoration instructions.txt to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000.
STATUS: Settling for 10 seconds...
STATUS: External USB drive (\\192.168.222.5\NetBackup) continues to stay mounted.

 

[Viktor Jaep]

I reconfigured backupmon to backup to second external USB drive. It works perfectly, except for some of the logging messages. In the following output, any reference to 192.168.222.5 are inaccurate as they do not apply for Target Media Type of USB. Functionally, it just works — just some cleanup of messages for USB-to-USB backup!:

BACKUPMON v1.32b2

Normal Backup starting in 10 seconds. Press [S]etup or [X] to override and enter RESTORE mode

Asus Router Model: GT-AX6000
Firmware/Build Number: 3004.388.5
External USB Drive Mount Path: /tmp/mnt/TheS1RsUSB
Backing up to \\192.168.222.5\NetBackup mounted to /tmp/mnt/bckupTheS1R
Backup directory location: /TheS1RsGT-AX6000
Frequency: Monthly
Mode: Basic

[Primary Backup Commencing]...

Messages:
STATUS: External Drive (\\192.168.222.5\NetBackup) mounted successfully under: /tmp/mnt/bckupTheS1R
STATUS: Finished backing up JFFS to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000/06/jffs.tar.gz.
STATUS: Finished backing up NVRAM to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000/06/nvram.cfg.
STATUS: Finished copying routerfw.txt to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000/06/routerfw.txt.
STATUS: Starting backup of EXT Drive on Mon Nov  6 13:52:58 EST 2023. Please stand by...
STATUS: Finished backing up EXT Drive in 18 sec to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000/06/TheS1RsUSB.tar.gz.
STATUS: Finished copying backupmon.sh script to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000.
STATUS: Finished copying backupmon.cfg script to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000.
STATUS: Finished copying exclusions script to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000.
STATUS: Finished copying reference nvram.txt extract to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000.
STATUS: Finished copying restoration instructions.txt to /tmp/mnt/bckupTheS1R/TheS1RsGT-AX6000.
STATUS: Settling for 10 seconds...
STATUS: External USB drive (\\192.168.222.5\NetBackup) continues to stay mounted.

Perhaps just leaving it with this? Thoughts?

STATUS: External USB drive continues to stay mounted.

 

[visortgw]

Perhaps just leaving it with this? Thoughts?

STATUS: External USB drive continues to stay mounted.

Yes, that's fine, but there are other instances referencing non-applicable network info as well:

• "Backing up to \\192.168.222.5\NetBackup mounted to /tmp/mnt/bckupTheS1R"
• "STATUS: External Drive (\\192.168.222.5\NetBackup) mounted successfully under: /tmp/mnt/bckupTheS1R"

 

[Viktor Jaep]

Yes, that's fine, but there are other instances referencing non-applicable network info as well:

• "Backing up to \\192.168.222.5\NetBackup mounted to /tmp/mnt/bckupTheS1R"
• "STATUS: External Drive (\\192.168.222.5\NetBackup) mounted successfully under: /tmp/mnt/bckupTheS1R"

But this share is still necessary... even though it's a USB drive. What would you have it say?

 

[visortgw]

But this share is still necessary... even though it's a USB drive. What would you have it say?

Possibly:

• "Backing up to USB mounted as /tmp/mnt/bckupTheS1R"
• "STATUS: External Drive (USB) mounted successfully under: /tmp/mnt/bckupTheS1R"

With USB as destination, network info, username, password, ... should have no bearing.

 

[Viktor Jaep]

Possibly:

• "Backing up to USB mounted as /tmp/mnt/bckupTheS1R"
• "STATUS: External Drive (USB) mounted successfully under: /tmp/mnt/bckupTheS1R"

With USB as destination, network info, username, password, ... should have no bearing.

Could you please download v1.32b2 again, and see if the messaging works better for you when backing up USB->USB?

Download:

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/BACKUPMON/master/backupmon-1.32b2.sh" -o "/jffs/scripts/backupmon.sh" && chmod 755 "/jffs/scripts/backupmon.sh"