Skip to main content
  • EN

Good morning everyone. Here is the 2nd VMCE Practice Question for the week. Please remember to hide your comments!

With the release of Veeam v12, the new VeeaMover feature was added. Excited to try this out, you as the Backup Administrator test moving backups in a Backup Job from one Repository configured with immutability to another Repository, also with immutability enabled. After the move, you notice the source backups in the Backups > Orphaned section in the Home node of the Veeam Console. Why are the backups from the source Repository shown here?

  1. This is expected behavior
  2. Because you just imported backups to a new Reository
  3. A user with the Backup Operator role just imported backup files and you weren't made aware of the import
  4. You have not assigned the source Repository to a Backup Job yet
  1. This is expected behavior

 

  1. This is expected behavior

 

a - This is expected behavior

 

  1. This is expected behavior

The files will be locked by immutability settings until they age out, at which point they should clear up automatically.

 

  1. This is expected behavior

 

And the answer to this week’s 2nd question is…

The answer is a. This is expected behavior. Let’s go over the other listed options → B. is accurate in that when you add a Repo and scan it for Backups, if backup files are on the Repo, they will be shown as stated in the question. Problem is, answer b. isn’t the task performed so isn’t correct. C. is simply a “distractor”; and d. is simply inaccurate because the Repo is indeed assigned to a Job as the question states...you’re just moving Backups to a new Repo. For more info on this behavior, see URL below:

https://helpcenter.veeam.com/docs/backup/vsphere/backup_moving.html?ver=120

 

I’m late, réponse D 🙂

 

Comment


Terms & Conditions