• EN
Solved

Using Backup Repository 1 scale-out repository extent (unable to meet data placement policy)

chandrasinghe
Userlevel 2

Hi Community,

 I have configure my secondary backup location as aws-s3 object storage. previously I used virtual tape backup to aws via aws tape gateway. Now It gave warning when backup to aws-s3.

 

 8/17/2022 7:10:36 PM :: Using Backup Repository 1 scale-out repository extent (unable to meet data placement policy)  

icon

Best answer by haslund 18 August 2022, 12:24

View original

6 comments

haslund
Userlevel 7
Badge +14

Is there sufficient space on backup repository 1?

Check out my blog on https://rasmushaslund.com - Rasmus is a Veeam Certified Trainer and passionate about all community work.
Chris.Childerhose
Userlevel 7
Badge +20

Is there sufficient space on backup repository 1?

That was going to be my first question. 😂

Chris Childerhose - VMCA2022 | VMCE2023 | Veeam Vanguard 7* | Veeam Legend 3* | vExpert 5* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
chandrasinghe
Userlevel 2

Is there sufficient space on backup repository 1?

Yes, Sufficient storage there locally. Since it is AWS storage capacity may not issue.

Chris.Childerhose
Userlevel 7
Badge +20

Here is a detailed explanation of the file placement with Veeam which might help with your issue - Backup File Placement - User Guide for VMware vSphere (veeam.com)

Chris Childerhose - VMCA2022 | VMCE2023 | Veeam Vanguard 7* | Veeam Legend 3* | vExpert 5* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
MicoolPaul
Userlevel 7
Badge +20

What is the current health of your backup repository in your SOBR? Have you had any previous repositories in the SOBR? Just thinking of the obvious things here:

 

  • If the policy was set to data locality and not to create new full backups when the existing extent is offline (though I’d expect a different error this way). What policy have you got set for your SOBR? Data Locality or Performance?
  • What backup method have you got configured? Reverse incremental, forward incremental, forever forward incremental?
  • As you can’t actually backup directly to S3, it can’t be backing up to S3 but to local instead, then with a copy/move offload later on. So the error must be related to your local repository backups. Can you supply further errors in the logs? How much capacity would a full backup be for your backup job? And what is the free/total capacity of your extent?
Michael Paul - #VeeamLegend | #VeeamVanguard | Veeam Certified Architect | VMware vExpert | https://micoolpaul.com | Twitter: @MicoolPaul | Mastodon: @micoolpaul@masto.nu | Bluesky: @micoolpaul.bsky.social
haslund
Userlevel 7
Badge +14

Is there sufficient space on backup repository 1?

Yes, Sufficient storage there locally. Since it is AWS storage capacity may not issue.

Keep in mind backups are not written directly to AWS, but must first land on local storage.

How many local repositories so you have?

How much capacity for each?

How much free space for each one?

Check out my blog on https://rasmushaslund.com - Rasmus is a Veeam Certified Trainer and passionate about all community work.

Comment


Terms & Conditions