Facebook
Twitter- Server operating system version
- CentOS 7.9
- Plesk version and microupdate number
- 18.0.52
Hi Team,
I have a strange issue
We have multiple servers in our environment and we are facing this issue with one particular server. which has plesk version of 18.0.52
While taking server backup via Plesk backup manager to our Amazon S3 , As per schedule it will start around midnight 12AM and it will be keep running for long time like more the 20+hours for around 1.8TB data
We didnt see anything on the backup logs or errors , It will run for 85% to 90% and finally it will fail with below error.
Error: Failed to open the dump backup_2403040046.tar2: Import error: Unable to find archive metadata. The archive is not valid Plesk backup or has been created in an unsupported Plesk version.
We have 2 full backups and 2 weeks of incremental backup . Will that cause because of any backup rotation was not done properly? or due to space constraint ?
We have already tried the below steps:
1. performed plesk repair installation
2. We have check with AWS about the s3 bucket which has any issues , but they confirmed no issues from AWS s3 end.
3. We also tried to delete the "backup_2403040046*" files from the destination location and retried the backup and still the same issue
Kindly advise how to proceed further check and fix it
I have a strange issue
We have multiple servers in our environment and we are facing this issue with one particular server. which has plesk version of 18.0.52
While taking server backup via Plesk backup manager to our Amazon S3 , As per schedule it will start around midnight 12AM and it will be keep running for long time like more the 20+hours for around 1.8TB data
We didnt see anything on the backup logs or errors , It will run for 85% to 90% and finally it will fail with below error.
Error: Failed to open the dump backup_2403040046.tar2: Import error: Unable to find archive metadata. The archive is not valid Plesk backup or has been created in an unsupported Plesk version.
We have 2 full backups and 2 weeks of incremental backup . Will that cause because of any backup rotation was not done properly? or due to space constraint ?
We have already tried the below steps:
1. performed plesk repair installation
2. We have check with AWS about the s3 bucket which has any issues , but they confirmed no issues from AWS s3 end.
3. We also tried to delete the "backup_2403040046*" files from the destination location and retried the backup and still the same issue
Kindly advise how to proceed further check and fix it
