topic Re: CPUSE automatic backups in General Topics

CPUSE automatic backups

SPM — Thu, 10 Oct 2019 14:15:16 GMT

After updating R77.30 to Take345 (from Take338) I've noticed an increased utilization of space in root partition

I don't have much free space left (~3GB, total partition size 18GB). So I don't want to run out of space

Analyzing I found out that in /opt/CPda/backup there are now 3 backups

the backup in the root of /opt/CPda/backup which was taken when upgrading to previous Take 338

and a folder /opt/CPda/backup/CheckPoint#CPUpdates#All#6.0#4#0#BUNDLE_R77_30_JUMBO_HF#345

where there are to more folders "Completely" and "LastTake"

So basically now instead of one backup there are 3 backups, which consume 3 times more space

I guess something changed in how backups taken during update

But do I really need all that backups?? is it safe to delete them & (I am not planing to rollback to previous Take)

here is a full backup files output

[Expert@CP:0]# ls -l /opt/CPda/backup total 562672 drwx------ 4 admin root 4096 Sep 28 02:12 CheckPoint#CPUpdates#All#6.0#4#0#BUNDLE_R77_30_JUMBO_HF#345 -rw-r--r-- 1 admin root 7623548 Nov 24 2018 ReportingServer_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 14285 Nov 24 2018 SecurePlatform_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 50711598 Nov 24 2018 cvpn_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 502484802 Nov 24 2018 fw1_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 5649235 Nov 24 2018 indexer_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 39977 Nov 24 2018 mgmtportal_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 3029451 Nov 24 2018 sim_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 6010542 Nov 24 2018 uepm_backup_HOTFIX_R77_30_JUMBO_HF.tgz [Expert@CP:0]# ls -l /opt/CPda/backup/CheckPoint#CPUpdates#All#6.0#4#0#BUNDLE_R77_30_JUMBO_HF#345 total 8 drwx------ 2 admin root 4096 Sep 28 02:18 Completely drwx------ 2 admin root 4096 Sep 28 02:18 LastTake [Expert@CP:0]# ls -l /opt/CPda/backup/CheckPoint#CPUpdates#All#6.0#4#0#BUNDLE_R77_30_JUMBO_HF#345/Completely total 635376 -rw-r--r-- 1 admin root 7622819 Sep 28 02:18 ReportingServer_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 16509 Sep 28 02:17 SecurePlatform_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 50711314 Sep 28 02:14 cvpn_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 576853604 Sep 28 02:13 fw1_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 5649319 Sep 28 02:14 indexer_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 40274 Sep 28 02:18 mgmtportal_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 3028584 Sep 28 02:18 sim_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 6015114 Sep 28 02:18 uepm_backup_HOTFIX_R77_30_JUMBO_HF.tgz [Expert@CP:0]# ls -l /opt/CPda/backup/CheckPoint#CPUpdates#All#6.0#4#0#BUNDLE_R77_30_JUMBO_HF#345/LastTake total 581224 -rw-r--r-- 1 admin root 7624021 Sep 28 02:18 ReportingServer_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 16509 Sep 28 02:14 SecurePlatform_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 148055 Sep 28 02:02 common_backup_file.tgz -rw-r--r-- 1 admin root 52002192 Sep 28 02:14 cvpn_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 519750664 Sep 28 02:10 fw1_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 5920007 Sep 28 02:14 indexer_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 40232 Sep 28 02:18 mgmtportal_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 3040944 Sep 28 02:18 sim_backup_HOTFIX_R77_30_JUMBO_HF.tgz -rw-r--r-- 1 admin root 5996419 Sep 28 02:18 uepm_backup_HOTFIX_R77_30_JUMBO_HF.tgz

Re: CPUSE automatic backups

Nick_Doropoulos — Thu, 10 Oct 2019 19:56:48 GMT

Hello SPM,

As far as I'm aware, no backups at all are needed to remain on a device so long as the following conditions exist:

- You are not planning to perform a local backup restore.

- There are copies of all backups stored on an external location.

Moreover, most of your backups appear to be too old anyway. Consequently, I would do the following:

- Take copies of all backups and ensure they are saved in an external device.

- Delete the existing backup files, starting with the biggest ones.

- Follow sk60080 and sk63361 to clear further disk space.

I hope this helps.

Re: CPUSE automatic backups

Boaz_Orshav — Tue, 15 Oct 2019 10:24:28 GMT

The backups are required for several purposes.

1. Uninstall. If you try to uninstall the jumbo, you shall get two options (completely, latest) and this is why there are two backup folders.

2. Even more important - when you try to install the next take, the CPUSE shall look for the backup files in order to clean some old files and rebuild the latest and complete backups.

Please do not delete the backup files as it might cause installation problems in the future.

Boaz

Re: CPUSE automatic backups

G_W_Albrecht — Tue, 15 Oct 2019 10:55:08 GMT

I would suggest the following:

- uninstall all Jumbo Takes in CPUSE

- delete all installation packages in CPUSE

- look if anything is left using SSH (and delete if true)

- install latest Jumbo Take again

Re: CPUSE automatic backups

SPM — Tue, 15 Oct 2019 11:38:19 GMT

1. Can you elaborate what these options means - Completely and Latest.

So I was on Take338 before installing Take345

So Latest should mean - go back to Take338

And Completely - go back to without any Take, like newly deployed

Am I right?

And since before Take345 there were no such folders I guess this is something new, right?

2. OK, I can understand two folders, but why I have backup files created during installation of previous Take ( Take338),

shouldn't they be deleted?

Re: CPUSE automatic backups

SPM — Tue, 15 Oct 2019 11:41:16 GMT

@G_W_Albrecht wrote:
I would suggest the following:
- uninstall all Jumbo Takes in CPUSE
- delete all installation packages in CPUSE
- look if anything is left using SSH (and delete if true)
- install latest Jumbo Take again

really? on a production system

that is not an option