Skip to main content
  • EN

The 2nd question for this week is below. Please remember to hide your guesses/comments.

~~~~~~~~~~~~~~~~~~~~

You recently upgraded your Veeam Backup environment to version 12 because one of the new features you have a need to use immediately is Move (repository) due to minimal remaining storage space in a Job's Repository. You begin the Move process on the affected Job and notice for some reason the Job is Disabled. Why is this the case?

  1. Your Junior Backup Admin with the Restore Operator role disabled the Job
  2. The Repository associated with the Job has run out of storage space
  3. This is expected behavior
  4. The Backup Job is running

And below is the answer for the 2nd question of this week:

Option a. is a distractor and irrelevant. Backup Jobs do not disable if a Repo runs short of space; they either provide a warning or fail altogether, so b. is not correct. And, if a Job is running (d.), it’s not disabled 😊 , leaving the only viable correct option of c. This is expected behavior . For more info, see URL below.

URL:

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

 

Comment


Terms & Conditions