Hi everyone,
Vertica is a database cluster used for "big data" https://goo.gl/1PgM0a
From system administrator's point of view, it's a shared-nothing cluster running on linux.
We have installed a 3 node cluster on sles, configured a backup job with VMTools quiescence disabled. It seems that the brief stun during snapshot creation/removal is not tolerated from che Vertica cluster, which shuts down itself.
Naturally the best approach is to reduce the impact of the snapshot on VMs (i.e. upgrading from ESXi5.5 to 6.x, and implementing Storage Snapshot integretion on Veeam), but it's possible that even after the best tuning, the Vertica Cluster will remain "too sensitive". So it will probably necessary to implement a script to put the DB in halted state before backup and restart it later.
Has someone here experience with this particular product?
Thanks in advance.
-
- Veeam Legend
- Posts: 128
- Liked: 38 times
- Joined: Sep 26, 2013 8:40 am
- Full Name: Alessandro T.
- Location: Bologna, Italy
- Contact:
Protecting HP Vertica Cluster
Alessandro aka Tinto | VMCE 2024 | Veeam Legend | VCP-DCV 2023 | VVSPHT2023 | vExpert 2024
blog.tinivelli.com
blog.tinivelli.com
-
- VP, Product Management
- Posts: 7077
- Liked: 1510 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Protecting HP Vertica Cluster
No, but general rules for SnapShot commit applies here.
Reduce VM disc count (to 1-4), Install ESXi 6 with Feb 2016 Patch level (new Snapshot commit technology), usage of block instead of NFS technology.... as well place all disks incl boot disk on fast storage. Usage of Backup from Storage Snapshot is as well a good ideas as you said. Avoid HotAdd backup mode (with NFS Storage).
Many cluster heartbeats can be tuned as well.
Reduce VM disc count (to 1-4), Install ESXi 6 with Feb 2016 Patch level (new Snapshot commit technology), usage of block instead of NFS technology.... as well place all disks incl boot disk on fast storage. Usage of Backup from Storage Snapshot is as well a good ideas as you said. Avoid HotAdd backup mode (with NFS Storage).
Many cluster heartbeats can be tuned as well.
-
- Veeam Legend
- Posts: 128
- Liked: 38 times
- Joined: Sep 26, 2013 8:40 am
- Full Name: Alessandro T.
- Location: Bologna, Italy
- Contact:
Re: Protecting HP Vertica Cluster
yes i have forced all my proxies in network mode, waiting for the storage snapshot integration.Andreas Neufert wrote:No, but general rules for SnapShot commit applies here.
Avoid HotAdd backup mode (with NFS Storage).
Many cluster heartbeats can be tuned as well.
I have searched the documentation of this database cluster, but i haven't still found any "sensitivity tuning" parameter. I will try asking on their forum.
At the moment we are going to implement a pre/post script to shutdown and restart the db before/after the job. I will post here when done, maybe it could bo useful for someother in future.
thank you for your reply.
Tschüß
Alessandro aka Tinto | VMCE 2024 | Veeam Legend | VCP-DCV 2023 | VVSPHT2023 | vExpert 2024
blog.tinivelli.com
blog.tinivelli.com
-
- Enthusiast
- Posts: 51
- Liked: 3 times
- Joined: Apr 19, 2013 8:30 pm
- Full Name: Kellen Flood
- Contact:
Re: Protecting HP Vertica Cluster
Has anyone had any additional experience with Veeam and Vertica?
Who is online
Users browsing this forum: evandrosp, Google [Bot], Majestic-12 [Bot], Semrush [Bot] and 232 guests