Skip to main content
  • EN

Happy Humpday again Community! Today is a bit special with regards to VMCE questions. Sadly, I only have a few remaining, but the good news is the few remaining are provided from YOU, the Community members. Today’s question is from fellow Veeam Legend and UK VUG Leader ​@MarkBoothman . Thank you for helping the VMCE Community with today’s question Mark! 😊

For those new to the VMCE page, please hide your comment (guess). To do so → before typing your response, click the ellipsis (3 dots) icon on the far right of the format toolbar at the top in your comment box and select the Spoiler option. This will place a ‘hide comment’ text box in your comment box area. Click inside this hide comment text box and start typing your answer (guess). Be careful to not click outside of the box or your comment will show after saving. We want your comment to not show after clicking the Send button so others can take full advantage of these practice questions. Also, please no need to do a ‘quote’ comment of this question; I would like to keep these practice questions neat. Let me know if you have issues. Good luck on the question!

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

A compliance auditor has recently reviewed your Veeam environment and recommended that, while configuration backups are enabled, you should encrypt these backups and ensure they are stored separately from the Veeam server. What must you do to follow this recommendation?

  1. From the main menu, select Configuration Backup, ensure "Enable configuration backup to the following repository" is checked, leave the default values, then select save
  2. From the main menu, select Configuration Backup, ensure "Enable configuration backup to the following repository" is checked, and change the repository to one of your SOBR repositories
  3. From the main menu, select Configuration Backup, ensure "Enable configuration backup to the following repository" is checked, and change the repository to one of your SOBR repositories. Check "Enable configuration backup file encryption" and add a password. Then, record the password in your password management system ensuring access is restricted to the relevant staff
  4. From the main menu, select Configuration Backup, ensure "Enable configuration backup to the following repository" is checked, and change the repository to one of your standard repositories on separate hardware from your VBR server. Check "Enable configuration backup file encryption" and add a password. Record the password in your password management system ensuring access is restricted to the relevant staff
  1. From the main menu, select Configuration Backup, ensure "Enable configuration backup to the following repository" is checked, and change the repository to one of your standard repositories on separate hardware from your VBR server. Check "Enable configuration backup file encryption" and add a password. Record the password in your password management system ensuring access is restricted to the relevant staff

 

D. From the main menu, select Configuration Backup, ensure "Enable configuration backup to the following repository" is checked, and change the repository to one of your standard repositories on separate hardware from your VBR server. Check "Enable configuration backup file encryption" and add a password. Record the password in your password management system ensuring access is restricted to the relevant staff

 

D

 

backup is already configure, so issue is to enable encryption. Configuration backup cannot be set on sobr. So answer is D

 

Nice to see community questions! 

Answer is D. , excluding C. because SOBR are not supported for configuration backups.

 

  • d - From the main menu, select Configuration Backup, ensure "Enable configuration backup to the following repository" is checked, and change the repository to one of your standard repositories on separate hardware from your VBR server. Check "Enable configuration backup file encryption" and add a password. Record the password in your password management system ensuring access is restricted to the relevant staff

 

A wee bit early, but I’m on vacay...so gonna get the answer to this week’s Community-based VMCE question posted. See below…

For this question, there are 2 requirements from the auditor which must be met → have the config backups encrypted, and have those same backups stored separate from the VBR server. The only option listed which meets these requirements is d. From the main menu, select Configuration Backup, ensure "Enable configuration backup to the following repository" is checked, and change the repository to one of your standard repositories on separate hardware from your VBR server. Check "Enable configuration backup file encryption" and add a password. Record the password in your password management system ensuring access is restricted to the relevant staff. Why? a. and b. do not enable encryption, so those are a “no” from the get-go. Why is c. not correct? SOBR is not a supported Repo for config backups (see 2nd URL below), thus why d. is the correct option.

 

For further info, see URL below:

https://helpcenter.veeam.com/docs/backup/hyperv/config_backup_encrypted.html?ver=120

https://helpcenter.veeam.com/docs/backup/hyperv/sobr_limitations.html?ver=120#limitations-for-jobs

 

I’ve been off for a few days so I’ll answer before checking what the answer was. I’m going to say D. I would also add that care should be taken that this encryption password shouldn’t only be stored in a password manager, if it’s self hosted and backed up by Veeam. I always recommend printing out the password and sticking it in a fireproof safe, or keeping a copy at home.

 

Comment


Terms & Conditions