Hi,
Today I created my first backup of my two mail servers in cluster, these two ubuntu linux servers are located on Vsphere, after job finished I see that my cluster have status "stopped" with error at the same time when veeam finished his backup job. Is any additional steps I need to configure to backup linux vm located on vsphere?
-
- Enthusiast
- Posts: 82
- Liked: 5 times
- Joined: Sep 03, 2020 10:32 am
- Full Name: Wojciech
- Contact:
-
- Veteran
- Posts: 1143
- Liked: 302 times
- Joined: Apr 27, 2020 12:46 pm
- Full Name: Natalia Lupacheva
- Contact:
Re: Veeam stopped my mail server cluster
Hi Wojciech,
You have configured vm backup job, right?
The backup job creation process should be similar for vSphere VMs on Linux/Windows - you see the same steps here.
Thanks!
You have configured vm backup job, right?
The backup job creation process should be similar for vSphere VMs on Linux/Windows - you see the same steps here.
Thanks!
-
- Enthusiast
- Posts: 82
- Liked: 5 times
- Joined: Sep 03, 2020 10:32 am
- Full Name: Wojciech
- Contact:
Re: Veeam stopped my mail server cluster
so what could I configure wrong way?
I did not checked "Enable application aware processing" or "Enable guest file system indexing"
These two servers in cluster share the same /opt volume using DRBD, and this volume is accessible only for master server in cluster.
I did not checked "Enable application aware processing" or "Enable guest file system indexing"
These two servers in cluster share the same /opt volume using DRBD, and this volume is accessible only for master server in cluster.
-
- VP, Product Management
- Posts: 7081
- Liked: 1511 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Veeam stopped my mail server cluster
I think you ran into a stun because of VMware Snapshot processing.
You can verify this without Veeam.
Create a VM Snapshot in vCenter (without any additional checkbox), wait the same time as the backup took, then remove the snapshot again.
You will likely face the same issue. If this is the case you need to work with VMware and your storage vendor on performance.
If you use VMware NFS based datastores and use Veeam HotAdd backup processing there could be some additional stuns by design of VMware. If this is the case let me know here and I can guide you further.
In the end if nothing helps, you can use our Veeam Agent for Linux managed by Veeam Backup & Replication to backup the system.
Other topic, you need potentially to change your DRBD cluster setting to a higher latency for failovers. You can test it with vMotion/StorageVMotion or VM snapshot creation/removal. Those processes should not failover the workload.
You can verify this without Veeam.
Create a VM Snapshot in vCenter (without any additional checkbox), wait the same time as the backup took, then remove the snapshot again.
You will likely face the same issue. If this is the case you need to work with VMware and your storage vendor on performance.
If you use VMware NFS based datastores and use Veeam HotAdd backup processing there could be some additional stuns by design of VMware. If this is the case let me know here and I can guide you further.
In the end if nothing helps, you can use our Veeam Agent for Linux managed by Veeam Backup & Replication to backup the system.
Other topic, you need potentially to change your DRBD cluster setting to a higher latency for failovers. You can test it with vMotion/StorageVMotion or VM snapshot creation/removal. Those processes should not failover the workload.
Who is online
Users browsing this forum: Bing [Bot] and 36 guests