[Corrupt Backup - how to delete or remove?]

John, a fake file will not work.  It must be an actual backup.  There must be some check when the file is accessed.  I use that method when this occurs in several environments I oversee.  

 

Thanks

[Corrupt Backup - how to delete or remove?]

For anyone that stumbles across this in the future...

A reboot will clear this up as mentioned above.  However, for those who can not or do not want to reboot.

 

You will need to create a good backup of the same type as the corrupt backups.  So for example 

 

View current backups (corrupt or non-existent)

 

>show backup

1)      FileName:  ns-backup-20160209_0601.tgz Level:  full

2)      FileName:  ns-backup-20160211_0601.tgz Level:  full

 

Create a new good backup.  Note a known good backup can be copied to the NetScaler if you are already at the 50 backup limit.

 

>create backup ns-backup-20170522_1330 -level full

 

Drop to the shell

 

>shell

 

Change to backup file directory

 

# cd /var/ns_sys_backup/

 

List

 

# ls

ns-backup-20170522_1330.tgz

 

find the good backup, in this case ns-backup-20170522_1330.tgz and copy it to the names of the corrupt or missing backups

 

# cp ns-backup-20170522_1330.tgz ns-backup-20160209_0601.tgz

 

# cp ns-backup-20170522_1330.tgz ns-backup-20160211_0601.tgz

 

Exit shell

 

# exit

 

and now you can remove the corrupt\missing backups using cli or gui

 

>rm backup ns-backup-20160211_0601.tgz

>rm backup ns-backup-20160209_0601.tgz

 

 

Its the long way around, but if a reboot is out of the question, and you have hit the 50 backup limit, this can be a real life saver instead of downtime.  If your backup naming convention is good, this can be scripted as well.  Hope this helps someone else out.