Veeam GPG key for automating deployments?

[Justin-DynamicD]

Does veeam supply the gpg key somewhere it can be downloaded? As the deb/rpm packages simply add a key and source list, it's actually easier for me to manage and automate the installation via puppet if I add the gpg key and source directly rather than downloading a temporary package as it leaves less artifacts (telling puppet to "temporarily" get a file is just not in it's nature. it's much easier to simple say "look like this").

It was easy enough to read the repo list out of /etc/apt/sources.list.d/, but still need to import the key from somewhere. Even better if one can post the expected thumbprint so I can validate authenticity.

Regards,
Justin

[nielsengelen]

They can be found on http://repository.veeam.com/keys/

If you are using puppet feel free to have a look at https://github.com/nielsengelen/val-puppet

[Justin-DynamicD]

i'll certainly look at that module, appreciated! (is there a way to add a "veeam" keyword to that site? I was just there a couple days ago and didn't find it).

Looking at dependencies it seems it already handles updating the repo? Does this one put the keys in as well so it doesn't snag?

EDIT: yup, opened up the code and you're already adding the key and repos in for me. Very nice! You guys should put this on puppet forge so it can be found more easily!

[Justin-DynamicD]

Followup on this puppet module sense you pointed me to it:

it looks as if only two of the 3 backup types are implemented (file/volume/entire)? The help doc only lists entire or volume, but if i sneak into init.pp I can see you commented all three types. However if I dig even deeper into config.pp the only thing you do is make sure the type != 'entire' then pass it through as a volume object.

Am I reading this right that there is no way to setup a backup job and specify a path (as opposed to a volume?)

[nielsengelen]

Indeed, the puppet class currently allows you to do entire or volume based backups. Just file or folder backups isn't added yet, this is on the todo list. However the module can always be extended as it is free to use .

There are some examples added as well on the GitHub page (https://github.com/nielsengelen/val-pup ... r/examples).

[Justin-DynamicD]

Yeah I started down hat path but it (appears at least) that the puppet module is doing as much as it can as I can't figure out any way to setup a backup job with the "file" type from veeamconfig (which is what the module calls). Instead you have to use the pseudo-gui veeam to do it which isn't automation friendly.

If I can figure out where the backup settings are stored maybe I can edit the settings directly then restart the veeam service, if that works Ill fork and submit a new version with the support. Thank you again!

[nielsengelen]

You can use the veeamconfig commandline to create file backups as well.

You define the folders via the "--objects" parameter then. For example "--objects /root,/home"

[Justin-DynamicD]

Ill have to do more testing but when attempting to set --objects it would complain if said path wasn't a volume. Not critical for my needs it turns out, but something of note:

Code: Select all

sudo veeamconfig job create --help
Veeam Agent for Linux
(c) Veeam Software AG

  Usage: veeamconfig job create [options] [command]

Commands:
  help, --help, -h   - Short help
  fileLevel          - Create new file-level backup job

Options:
  --name <value>                    - Job name
  --repoName <value>                - Repository name
  --compressionLevel <0...4>        - Compression level
  --blockSize <256|512|1024|4096>   - Block size (Kb)
  --maxPoints <value>               - Number of restore points to keep on disk
  --prejob <value>                  - Pre-job command (executed on job start)
  --postjob <value>                 - Post-job command (executed on job finish)
  --objects <value>                 - Comma-separated list of objects to backup (device file in /dev, filesystem mountpoint, LVM volume group name or LVM logical volume name)
  --backupAllSystem                 - Backup all system

Note the objects value is specific about needing volume names/mount points.

I've forked the module provided via my public github, and have been cleaning things up as well as adding features to make it more functional. You can find it/abuse it here: https://github.com/Justin-DynamicD/val-puppet

Key differences:

• fixed some variables that were preventing repos from getting setup properly on CentOS 6/7
• fixed the job configuration on vbrserver deployments so that it correctly processes 'entire' backup types and doesn't default to /dev/sda
• added job_ensure present|absent parameter so that jobs (and their corresponding cronjobs) can be deleted for eas(ier) reconfiguration (more plans here).
• changed cron file creation to include the jobname so that multiple jobs can be created/managed for those who pay for that extra control

There's a lot more I'd like to do (be able to inspect existing job settings and match against submitted parameters then determine if an update is necessary rather than forcing a delete/recreate I have in place now). Honestly the DSL of Puppet is much more limited than MS's PowerShell DSC so I don't know how far Ill get on this goal but we'll see. If it dies on the vine, at least you can maybe merge it back in.

[nielsengelen]

Hi Justin,

Some cool addons there and I might merge these into the class. There are probably more things that can be done hence the class is ment as a start .

I can add you as a contributor if wanted.

[Justin-DynamicD]

I'm more than happy to help commit in anyway. Found an new bug that needs to be sorted out:

veeamsnap will install but only pass "info" back if it OS doesn't have the appropriate kernel headers to allow it to recompile the driver. This means veeam will successfully install but be unable to actually take snapshots/backup. I'll probably have to tweak the class to install the right kernel-devel before trying to install, but likely need to use exec as I don't know how to ensure the version matches the kernel version.

[Justin-DynamicD]

Thank you very much for adding me to the repo. With your permission ill merge my changes in and let you review/approve deny BUT! Another question:

right now it's clearly "val" for veeam agent linux (I imagine). I need to push Windows agents next so I either have to paths:

• I start putting in $osfamily calls and take different actions for different OSes within a singular module. We should probably rename the module if we take this route.
• I create a new vaw_puppet module for windows. I would need a new repo to contribute to if we take this route.

I'm leaning towards the first route, but thought I'd make you aware of my intentions. Take care and thank you again for your support.

Last note: I can't create branches in that repo. Not sure if you want me committing directly to the master.

[nielsengelen]

I didn't add you to the repo yet so I don't think you can merge things . I will look into it a bit later and perform the merges.

In regards to VAW, as there won't be a veeamconfig command the deployment via puppet would be a bit different and I personally think it would be better to have 2 modules for it.