Contact & Subscribe RSS

LinkedIn
RSS

Posts tagged "veeam"

VEEAM Task failed Error: Exception of type ‘System.OutOfMemoryException’ was thrown

Last week I had the following error when starting a Veeam backup job. I thought my proxy servers where out of memory, so I rebooted them. Then I started the backup jobs again, with no result.

Solution:
To solve this issue you must logoff all the other RDP sessions, which have a disconnected session with the Veeam console open. Alternatively, give the Veeam backup server more resources so there is more memory available.

Exchange backup VEEAM

Veeam Backup and Replication gives the possibility to create a consistent backup from your Exchange farm. This can be a standalone Exchange system or an Exchange DAG cluster. It makes use of the Microsoft Exchange VSS writers inside the VM. The Veeam server creates a RPC connection to the Exchange servers, and place some backup scripts on the /ADMIN$ share. When the backup starts Veeam starts this script which talks to the Microsoft VSS Writers to create a consistent backup.

Enable application aware processing

To create an application aware backup in Veeam you must enable the “Application aware processing” option in the Veeam job properties. Then go to applications for application specific settings. In this tab you can configure VSS, Log and error settings. Configure settings which are suitable for your systems.

User rights Veeam Exchange backup

Select credentials which have full rights (read / write) to all files in the folder with the database.
For direct restore to your exchange farm the user must also have full access to the Mailbox. This user permissions can be set with the following command:

When you have a service account for restoring to all mailboxes you can use Exchange impersonation. This can be set with the following command:

 

Back-up Exchange DAG Cluster

When you create a backup of an Exchange DAG Cluster node, default all active and passive nodes are available for restore. So theoretically you only have one backup of 1 exchange node.

Tips for creating backup of your Exchange DAG Cluster:

  • Backup both of your exchange servers in one backup job, this gives you better dedup results.
  • Don’t backup your exchange nodes in separate jobs at the same time, this can cause a failover.
  • Veeam backup can cause load on your exchange server, the best situation is to create a new exchange cluster node server with only passive mailboxes.
  • When your exchange servers failover during a backup you can increase the failover time of your exchange cluster nodes. Commands for changing the cluster parameters:

 

 

 

Veeam Backup free

Veeam delivers powerful backup software for backup your virtual or psychical servers (veeam endpoint). The backup method for VMWare or Hyper-V virtual systems is agentless. There is no need to install something on the guest system. Veeam Connects to the Hypervisor layer, creates a snapshot, transports this snapshot to a backup repository and saves it. Veeam make use of the Hypervisor API to create a backup. When there is some application installed on the system there is a possibility to create a what they called application aware backup. The Veeam service connects with RPC to the virtual system and make use of the application VSS writers to create a consistent backup.

VEEAM Backup free features:

Veeam Free make use of the VeeamZIP to create ad hoc backups of the virtual machine for operational, portability or archival purposes.

Following features are enabled in the free edition:veeam_endpoint_backup

Backup & Restore: Full back up creation and restore.
VM File recovery: The possibility to restore VM files (vmdk, vmx for example).
Veeam Explorer: Restore AD, SQL, Exchange or Sharepoint objects.
Native tape support: copying files to tape drives.
Backup encryption: Allows you to encrypt the backup files.

Veeam Backup psychical server, client or desktop

Veeam endpoint protection allows you to make use of a stand-alone Windows service for backup of your physical client or server. It does not require a dedicated server or repository’s. You just install the software on each server you want to protect. The windows server makes use of a little local MS SQL DB. It is possible to integrate Veeam endpoint with Veeam Backup and Replication software. This allows you to save your endpoint backup on a Veeam repository.
Note: Veeam Endpoint does not support Application VSS writers yet. So the backup is not Application consistent. But for many situations is a crash consistent enough.

Features Veeam endpoint backup:

Backup & Recovery: Choose to back up your entire computer, volume or just a couple of maps.
Scheduler: When do you want that the backup task runs?
Backup target: Where do you want to place the created backup? When you choose a removable device (USB stick) you can choose to detach the device when ready. This protect the device from ransomware.
Bitlocker: Veeam endpoint supports bitlocker encrypted drives.
Create recovery media: In case of a full system crash you can use your created recovery boot USB stick.
Support: Veeam gives free support, because they want to be the best. Yes this is awesome 

Veeam download

Click here

Start VEEAM Job Task Scheduler

The VEEAM job scheduler is really basic. It’s not possible to schedule a job on different times in a week for example.
You can create a task schedule job to start the back-up on every possible time.

Start -> Task scheduler -> Create Task

– Name (Job name and Time)
– Check Run whether user is logged on or not
– Check Run with highest privileges
– Configure for: Windows server 2012 R2 (or other late OS)
– Triggers (choose a time)
– Action -> New -> Start a program
– Program script: powershell
– Arguments:

Start job normally:

Start full backup you give the value -fullbackup after start-vbrjob:

 

VEEAM Failed to flush change tracking data. Using full scan incremental run.

Changed block tracking information is no longer being read, causing entire disks to be read instead of just the changed blocks.
This is a very generic error, so it is quite difficult to say what has happened.

Hyper-v Solution:

Run “sc stop veeamfct” and “sc start veeamfct” on the Hyper-V hosts affected to restart the Veeam Change Tracking service, and then see if the errors are resolved afterwards.

VEEAM KB1881

OR

When you run VEEAM V8, you must install patch 1. After this update the Flush change tracking data errors are gone.
This patch can be downloaded from the here:
VEEAM KB1982