Skip to main content

VMCE Practice Question - 27 June 2024

coolsport00
Forum|alt.badge.img+20

And, the 2nd question for the week is below. Again, please remember to hide your comments. Good luck!

 

After verifying System and Platform requirements, you decide it's time to upgrade your Veeam Backup server from version 11 to version 12.1. Right after the upgrade, you do no further modifications to Veeam as you are excited to try out some new features. The first feature you attempt is to move a single VM from one Backup Job to another. When attempting to do so, you are not able to. What may cause this behavior?

  1. You're running Veeam Foundation Edition
  2. Your Repositories are using Per-VM with a single metadata file
  3. MFA is not enabled
  4. The VM backup file is encrypted
Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00

8 comments

DavideAbrigo
Forum|alt.badge.img+1
  • DavideAbrigo
  • Experienced User
  • 119 comments
  • June 27, 2024
Show content
  1. Your Repositories are using Per-VM with a single metadata file

 

coolsport00
AndrePulia
2 people like this
  • coolsport00
    coolsport00
  • AndrePulia
    AndrePulia
BethSouza
Forum|alt.badge.img+5
  • BethSouza
  • Veeam Vanguard
  • 84 comments
  • June 27, 2024
Show content

d - The VM backup file is encrypted

 

Elizabeth Souza
coolsport00
AndrePulia
2 people like this
  • coolsport00
    coolsport00
  • AndrePulia
    AndrePulia
Gustavo Dutschmann
Show content
  1. Your Repositories are using Per-VM with a single metadata file

 

Chris.Childerhose
coolsport00
AndrePulia
3 people like this
  • Chris.Childerhose
    Chris.Childerhose
  • coolsport00
    coolsport00
  • AndrePulia
    AndrePulia
keiranshelden
Forum|alt.badge.img+1
  • keiranshelden
  • Veeam Vanguard
  • 34 comments
  • June 27, 2024
Show content
  1. Your Repositories are using Per-VM with a single metadata file. 

 

Vanguard | vExpert ‘14-‘23 | NSX ‘18 | Drummer | @Techfieldday delegate | @tech4breakfast Australian Sr. Field Correspondent
Chris.Childerhose
coolsport00
AndrePulia
3 people like this
  • Chris.Childerhose
    Chris.Childerhose
  • coolsport00
    coolsport00
  • AndrePulia
    AndrePulia
Chris.Childerhose
Forum|alt.badge.img+21
  • Chris.Childerhose
  • Veeam Legend, Veeam Vanguard
  • 8497 comments
  • June 27, 2024
Show content
  1. Your Repositories are using Per-VM with a single metadata file

You need to convert the chains for all backups first and then move the VM to a new job.

 

Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
coolsport00
keiranshelden
Link State
4 people like this
  • coolsport00
    coolsport00
  • keiranshelden
    keiranshelden
  • Link State
    Link State
  • AndrePulia
    AndrePulia
Link State
Forum|alt.badge.img+11
  • Link State
  • Veeam Legend
  • 612 comments
  • June 27, 2024
Show content
  1. Your Repositories are using Per-VM with a single metadata file 

need covert legacy chain to neew chain

 

Veeam: VMCA | VMCE | VMXP | Veeam Legend - Microsoft: MCITP | MCP | MCSA | 2008 R2 | 2012R2 | 2016 | MCSE Core Infrastructure | MCSE Cloud Platform - Azure: AZ900 | AZ104| AZ500 - AWS Cloud Practitioner - VMWare: VCP-DCV Vsphere 7.x - Cisco: CCNA (Expired)
Chris.Childerhose
coolsport00
AndrePulia
3 people like this
  • Chris.Childerhose
    Chris.Childerhose
  • coolsport00
    coolsport00
  • AndrePulia
    AndrePulia
coolsport00
Forum|alt.badge.img+20
  • coolsport00
  • Author
  • Veeam Legend
  • 4145 comments
  • June 28, 2024

As I shared in the previous question for the week, it’s Friday, so the answer is below…

Show content

The key to this question is nothing was modified after upgrading. You may be using Per-VM on your Repos, but legacy VBR used a single metadata file for the whole backup job. With the release of v12, this changed to have a metadata file per-VM, allowing for the new VeeaMover feature to move or copy backups to new Repositories. As such, the answer to the question is b. Your Repositories are using Per-VM with a single metadata file ; all other listed options have zero to do with moving/copying VMs.

https://helpcenter.veeam.com/docs/backup/vsphere/per_vm_backup_files.html?ver=120#per-machine-backup-with-single-metadata-file 

 

Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
Link State
AndrePulia
DavideAbrigo
5 people like this
  • Link State
    Link State
  • AndrePulia
    AndrePulia
  • DavideAbrigo
    DavideAbrigo
  • Dynamic
    Dynamic
  • Gustavo Dutschmann
    Gustavo Dutschmann
AndrePulia
Forum|alt.badge.img+6
  • AndrePulia
  • Veeam Legend, Veeam Vanguard
  • 333 comments
  • December 12, 2024
Show content

B - this one is fantastic!!!! I really liked it. congrats.

 

André Pulia - VMCA | VMCE | VMCT | HPECI | VCI | Nutanix Certified Instructor | Twitter: @andrepulia | Blog Site – https://pulia.com.br | https://www.credly.com/users/andre-pulia
coolsport00
AndrePulia
2 people like this
  • coolsport00
    coolsport00
  • AndrePulia
    AndrePulia

Comment


Terms & Conditions