Veeam Agent - Creation and execution of backups

Hello guys!

Continuing the articles on the Veeam Agent, today I want to talk about creating backups using the agent.

First of all it is important to explain that we have two distinct backup modes with the Veeam agent. Are they:

  • Managed by backup server
    • This mode is used to backup machines that you are sure will never lose contact with the Veeam server. In this mode the job is created and managed by the console and the agent is used only for backup creation. All options for this type of backup are the same as a backup of a VM in ESXi, for example.
  • Managed by agent
    • This mode is used to backup machines that you do not know if they are always connected, such as user stations, for example. In this mode Veeam only creates a policy with the backup settings on the console and applies this policy to the agent on the machine and whoever does the entire execution and scheduling process is the agent. This works so that if there is no contact with the console at some point the backup will start normally because the policy is already applied to the agent.

For details on the two modes click HERE.

In the example I will detail, I am using the agent management mode to demonstrate how it is different from a normal backup job.

So, continuing exactly from where we stopped at post anterior we will create a backup job for Windows 7 where I installed the agent. To do this click on "Backup Job" and "Windows computer ..."

In the new wizard that will be started we must choose exactly the way the job will work. As explained earlier, I'll choose the agent-managed mode to show the new options. If the backup is from a station the only option we will have is the one managed by the agent. Choose the mode that best suits your environment and click "Next".

Define a name for the Job and click "Next".

In the next screen we must add the objects to our job. We can add it via "Protection Group" or "Individual Computer". Choose Protection Group.

In the object selection screen you can choose the entire Protection Group, so if new machines enter this Protection Group they will already be part of the job. Or you can choose a single object within Protection Group.

Choose the objects and click "Next" to proceed.

In the next screen we can choose the type of backup that we will do. Are they:

  • Entire Computer
    • As the name says, it's the backup of the entire machine. Temporary, deleted, and page files are deleted from the backup so that the size is smaller.
  • Volume level backup
    • In this mode you can choose a specific machine volume, such as only the volume of data or only the volume of the operating system. Like the previous, this also the temporary files, deleted files and page files are excluded from the backup so that the size is smaller.
  • File level backup (slower)
    • In this mode we can choose a specific file or folder inside the machine to be backed up. However, with the name itself says, choosing this mode will slow down the backup.

For more information on backup modes click HERE.

Choose the mode that best fits your environment and click "Next."

In the next screen we must choose the destination of our backup. The options are:

  • Local storage
    • This option allows you to back up to a disk connected to the machine being protected. It can be a USB device, Firewire, eSATA, etc. Obviously, it is not recommended to back up to a local disk of the machine.
  • Shared folder
    • This option allows you to back up to an SMB, NAS, or File Server share.
  • Veeam backup repository
    • This option allows you to back up to a Veeam-managed repository.

For more information about backup destination options click HERE.

Choose the best option for your environment and click "Next".

As I chose the option to use a Veeam-managed repository for the destination of my backup, we must specify the name of the Veeam server and the communication port. Since I have only one Veeam server in the environment I should leave the default options and proceed by clicking Next.

On the next screen choose the Veeam repository, set the job retention policy and, if necessary, configure the advanced job options. The advanced options are the same as a normal backup job. I detail these options in this post. Click "Next" to proceed.

In the next screen we must define the schedule of our backup. Unlike other job types, this section is a bit different.

In "Periodically" we can set the time the backup should be done.

Assuming you are probably backing up a station and it is probably shut down every day you can choose which action the agent should take if the machine is turned off at the time of the backup. You can choose between:

  • Skip backup
    • The backup simply will not run if the machine is turned off at that time and will only be run the next day at the same time
  • Backup once powered on
    • If the machine is off at the set time, the backup will run as soon as it is turned back on.

We can further define what should be done after the backup is completed. The options are:

  • Keep running
    • Nothing will happen and the machine will continue to function normally.
  • Sleep
    • After the backup is complete, the machine will enter sleep mode.
  • Hibernate
    • After the backup is completed, the machine will hibernate.
  • Shutdown
    • After the backup is completed, the machine will shut down.

In addition to scheduling by schedule we can also define that the backup is executed depending on an action that occurs on the machine. Are they:

  • Lock
  • Log off
  • When backup target is connected
    • In this case you can still choose to eject the device after the backup is completed
  • Backup up no more often than every
    • If you choose to make a backup at the station every time a Lock occurs, it is important to set the maximum number of backups that will be executed on the day, since this is an action that can occur several times a day.

After choosing the scheduling options for the job click "Apply".

Click "Finish" to finish creating the job.

By clicking on the job we will see that the backup configuration has already been sent to the machine.

If we go to the machine the agent will already be running on the machine and ready to run the backup.

If you find it necessary, you can start the backup by the agent by clicking "Backup now".

After finalizing the backup it is possible to verify that the backup file was generated in our repository.

That's it, everybody!

In the next post I want to demonstrate the example of a restore of our backup made by the agent.

See you!