Scheduled backup time seems to concatenate backup process time as back ups go on...
francisqureshi opened this issue · 0 comments
I have been using this script to do nightly Resolve DB backups for the last month.
Thanks so much for creating it!
All is working well but I can see in the logs and files that the backup is slowly slipping forward in time as the backups go on... This seems like something worth flagging if anyone plans to use this long term..
Please see my log:
ResolveDB_23_Q2 was backed up at 2023_10_02_23_05 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was optimized at 2023_10_02_23_06.
ResolveDB_23_Q2 was backed up at 2023_10_03_23_09 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_04_23_14 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_05_23_18 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_06_23_22 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_07_23_26 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_08_23_30 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was optimized at 2023_10_09_23_06.
ResolveDB_23_Q2 was backed up at 2023_10_09_23_34 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_10_23_38 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_11_23_42 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_12_23_46 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_13_23_50 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_14_23_54 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_15_23_59 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was optimized at 2023_10_16_23_06.
ResolveDB_23_Q2 was backed up at 2023_10_17_00_03 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_18_00_07 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_19_00_11 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_20_00_15 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_21_00_20 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_22_00_24 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_23_00_28 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was optimized at 2023_10_23_23_06.
ResolveDB_23_Q2 was backed up at 2023_10_24_00_33 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_25_00_37 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_26_00_41 into /Users/bkup/Desktop/Resolve-database-backups.
ResolveDB_23_Q2 was backed up at 2023_10_27_00_46 into /Users/bkup/Desktop/Resolve-database-backups.
We started the first back up at 23:05 and now we are at 00:46 on backup number 25 so it looks like each back up takes 5mins, then the counter starts again? Essentially adding the time that back up takes to the 24Hr timer.
I worry that if this script gets left unattended it will ultimately spill in the working day and could cause DB slow down/ mess with archive/backup software etc.