MDS R77.30 restore. Some unexpected things.

[Dzenboy]

Hi, all!
Have some odd things whith mds r75.30 restore from two different backups.

1. First backup was created at lab stage (versions and hotfixes was documented). Now I'm trying to restore it in lab enviroment and see "cannot complete the process due to package compression error".
2. Second backup is from production (versions and hotfixes are the same and it's documented too). After trying to restore it I see that all o'k, but cma's not started, managment not started too and so on. Mdsstat says that here is a little part of all CMA's from backup presented.
version of gtar used is 1.13.25.
Is this problem of gtar? Any ideas?

[cciesec2006]

Hi, all!
Have some odd things whith mds r77.30 restore from two different backups.

1. First backup was created at lab stage (versions and hotfixes was documented). Now I'm trying to restore it in lab enviroment and see "cannot complete the process due to package compression error".
2. Second backup is from production (versions and hotfixes are the same and it's documented too). After trying to restore it I see that all o'k, but cma's not started, managment not started too and so on. Mdsstat says that here is a little part of all CMA's from backup presented.
version of gtar used is 1.13.25.
Is this problem of gtar? Any ideas?

Are you using checkpoint backup command or "mds_backup" command? For Checkpoint MDS system, "mds_backup" method is the way to go, IMHO. That's what I've been doing for the past 15 years.

[Dzenboy]

Are you using checkpoint backup command or "mds_backup" command? For Checkpoint MDS system, "mds_backup" method is the way to go, IMHO. That's what I've been doing for the past 15 years.

Yes, it was mds_backup.

[cciesec2006]

Yes, it was mds_backup.

What is the file size of the mds_backup? It should be less than 2GB. I think there are "known" issues if the file size is > 2GB but checkpoint has claimed that the issue has been fixed. Mine mds_backup has always been < 2GB because I do not backup logs and other un-used stuffs. I think there is a file that you can exclude them in the mds_backup process.

[Dzenboy]

What is the file size of the mds_backup? It should be less than 2GB. I think there are "known" issues if the file size is > 2GB but checkpoint has claimed that the issue has been fixed. Mine mds_backup has always been < 2GB because I do not backup logs and other un-used stuffs. I think there is a file that you can exclude them in the mds_backup process.

Approx 12 GB. No logs. varopt > 11 GB. Now looking for what inside.

[Dzenboy]

Approx 12 GB. No logs. varopt > 11 GB. Now looking for what inside.

>30 CMA inside. No logs, tmp and so on. Every CMA around 1 GB unpacked. Seem's to be ok.
It's look like the problem is in the gtar version.

[cciesec2006]

Approx 12 GB. No logs. varopt > 11 GB. Now looking for what inside.

11GB is definitely an issue. Check to see how many revision control you have in the database? Those can add up very quickly.

[Dzenboy]

11GB is definitely an issue. Check to see how many revision control you have in the database? Those can add up very quickly.

\conf\db_versions is 20 bytes.

[Dzenboy]

Has anyone rpm of tar 1.15.x or above for Splat? Share it, plz!

[Dzenboy]

This is R75.30 issue post. I 've tryed to correct but..

[mcnallym]

When you do the mds_backup then along with the backup then also places the gtar files etc that need to use along with the backup file to restore.

Is important that use those gtar from where the backup created todo restore

When providing mds_backup to check point tac then always have to forward the other files in the directory as well such as the gtar et

[Dzenboy]

When you do the mds_backup then along with the backup then also places the gtar files etc that need to use along with the backup file to restore.

Is important that use those gtar from where the backup created todo restore

When providing mds_backup to check point tac then always have to forward the other files in the directory as well such as the gtar et

Yes, i know this all.
Another odd thing that backup was made at 75.30 when restored says that we need 75.20 to restore it. Yes, there was upgrade from 75.20 but is this normal behavior?