The post would be easier to read if you put the code examples in CODE blocks.
if [ "$(find "$DIR" -name "$IPSET_NAME" -mtime +7 -print)" = "$DIR/$IPSET_NAME" ]; then
Download_AMAZON "$IPSET_NAME" "$REGION"
fiI have some data for you about this problem. I have a few days where the backup did not complete. See the attached files. For the Restore scripts, I included the end of the file when the backup did not complete completely and one where it did.
Thank you. Unfortunately, the system log didn't provide any useful information to help pinpoint the root cause. Have you run a health check scan of the storage device lately? The health check utility is on the router home page. Or use the fsck utility to scan for bad sectors?
Thanks for the update. A possible conflict with spdMerlin is the only clue we have right now. I'll set up a batch job on my router to see if I can spot any issues.
Saving [Captive Portal settings] 2 secs (22 variables, Bytes=0 Total=8600 )
Saving [Traffic Control settings] 0 secs (11 variables, Bytes=0 Total=8600 )
Saving [VLAN Settings] 0 secs (6 variables, Bytes=0 Total=8600 )
#[Astrill VPN settings] 1 secs (? variables)
Saving [User Adds] 1 secs (0 WARiables, Bytes=0 Total=8600 )#!/bin/sh
UTIL=nvram
BLOC=/mnt/<usb-label>/$UTIL
BARC=$BLOC/archive
BKUP=$BLOC/backup
RETENTION=7
CRUNAME=$UTIL
cru l | grep $CRUNAME >/dev/null || cru a $CRUNAME "0 5 * * * $0 $*"
#exit if directory doesn't exist or not mounted.
[[ -d "$BLOC" ]] || exit 1
[[ -d "$BKUP" ]] && rm -rf $BKUP
[[ -d "$BKUP" ]] || mkdir $BKUP
cd "$BLOC"
/mnt/<usb-label>/nvram/nvram-save.sh -clk -b
#mv "$BKUP" "$BKUP.$(date +"%F_%T")"
sleep 30
mv "$BKUP" "$BKUP.$(hostname).$(date +%Y%m%d%H%M)"
mv "$BKUP.$(hostname).$(date +%Y%m%d%H%M)" "$BARC"
#careful here. You do not want this running if ntp hasn't synced.
find $BARC -name "backup.$(hostname).20*" -mtime +$RETENTION -exec rm -rf {} \;
exit 0# Add NVRAM backup job & run retention
#/usr/sbin/cru a Backup "0 5 * * * /tmp/mnt/sauron-usb/nvram/nvram-save.sh"
/jffs/scripts/systembackup.sh
Migration Mode is for moving the settings from one router to another. In migration mode, model specific information is not included.@Xentrk
Hi!
I'm currently running Version 380.70 on an 87U. Is it still true that I would need to run the script in Migration-mode in order to restore the values between the 380.70 and the newest version? And if yes, what settings would then be lost? All I've found is transmit power but in the documentation it seems suggested that there may be other things as well. I'm very thankful for the time spent making it work between updates. I've been putting off upgrading because the old script didn't support the newer versions and it's too much work to re-enter settings.
I guess it's time to start shooting some screens.
Is the jffs partition enabled? Administration -> System. If it's not enabled, select Yes for the two options below, Apply the settings, then reboot.
Quoting a well known phrase "D'oh"
#!/bin/sh
# Author is Gray Jack the Fixxxer
# SOURCEDIR is the path to NSRU folder
SOURCEDIR=/mnt/swapusb/nsru
# OUTPUTDIR is the path where backups should be created
OUTPUTDIR=/mnt/HSH_HDD/Download2/Backup/NVRAM
# NUMBERBCKS means how much old copies of backup should be left
# NUMBERBCKS=0 means backup will be overwritten every time and no old copy will be left
NUMBERBCKS=2
if [ -f ${OUTPUTDIR}/nsru.tar.gz.bck${NUMBERBCKS} ]
then
rm -f ${OUTPUTDIR}/nsru.tar.gz.bck${NUMBERBCKS}
fi
count=$(($NUMBERBCKS-1))
while [ $count -gt 0 ]
do
if [ -f ${OUTPUTDIR}/nsru.tar.gz.bck${count} ]
then
mv ${OUTPUTDIR}/nsru.tar.gz.bck${count} ${OUTPUTDIR}/nsru.tar.gz.bck$(($count+1))
fi
count=$(($count-1))
done
if [ -f ${OUTPUTDIR}/nsru.tar.gz.bck ] && [ $NUMBERBCKS -ne 0 ]
then
mv ${OUTPUTDIR}/nsru.tar.gz.bck ${OUTPUTDIR}/nsru.tar.gz.bck1
fi
${SOURCEDIR}/nvram-save.sh
tar -czf ${OUTPUTDIR}/nsru.tar.gz.bck -C ${SOURCEDIR}/backup .
rm -rf ${SOURCEDIR}/backup/
mkdir ${SOURCEDIR}/backup/The failure happened again last night after it had been working fine for more than a week. Here is a snippet of the logs when it failed.
On the HND routers, some nvram vars are stored in /jffs/nvram. For those nvram parms, you need to run the jffs-restore.sh script to restore the nvram parms.
This is a difficult one to debug and find the root cause since there are no error messages. It just appears to stop writing to disk.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!