Yeah, things are working as they should.
The only thing I'm not liking is the fact that Ghost is appending a three digit suffix to each new backup.
For example; Backup001, Backup002, etc.
When the limit is reached, (4 in my setup), Ghost just continues with the suffix. (i.e., Backup005 being the newest and Backup001 being deleted)...
Perhaps some tweaking to the code responsible for renaming is in order?
As is stands right now, I'm back to using my batch file for the renaming and backup limiting...
Maybe the tech team can gleen some info from this batch file on how Ghost's built-in renaming should work?...
@ECHO OFF
REM This ensures the correct directory is chosen.
REM X:\Backup_Directory = the drive\folder used to store backups.
X:
CHDIR X:\Backup_Directory
REM Most applications like to run pre/post commands (such as this batch file) INSTANTLY after performing a task.
REM Unfortunately, the OS needs a few seconds to refresh the folder so the files actually exist when this batch file is run.
REM This next line forces a wait command. 3000 = 3seconds
REM If needed, just remove the REM from in front of the word PING.
REM PING 1.1.1.1 -n 1 -w 3000 >NUL
REM This line checks that the latest backup actually exists.
IF NOT EXIST X:\Backup_Directory\Weekly_Backup_Job.v2i EXIT
REM Just an FYI, Backup4.v2i = oldest while Backup1.v2i = newest backup
IF EXIST Backup4.v2i DEL Backup4.v2i
IF EXIST Backup3.v2i REN Backup3.v2i Backup4.v2i
IF EXIST Backup2.v2i REN Backup2.v2i Backup3.v2i
IF EXIST Backup1.v2i REN Backup1.v2i Backup2.v2i
REM Weekly_Backup_Job.v2i = whatever your backup gets named by Ghost.
IF EXIST Weekly_Backup_Job.v2i REN Weekly_Backup_Job.v2i Backup1.v2i
EXIT