We're in the process of upgrading our infrastructure and have been edged into the VMWare world. We've been having discussions around the use of Veeam for backups (initiated by the vendor, not us). Is it worth entertaining Veeam at all? We'd probably still want to do probkup for the actual databases, it's more the rest of the box configuration I guess...
I'm aware that we would need to use freeze and thaw scripts (proquiet), but how long would the proquiet be active for? Is it just for the snap, or is it for the whole process?
Any other comments?
You have a few options. The easiest would be to probkup online the DB and accept that the Veeam'd backup of the DB is not usable. But the shell is so you could prorest on top of it. Another option is not to backup the DB filesystem at all - just the probkup file. I would not bother with proquiet stuff but if you do, the freeze is typically a few seconds. You have to grep out the message in the db.lg to know for certain that it's done. There was an enhancement request some years ago to prevent proquiet from returning to the cmd line until the proquiet actually finished but I'm not sure if/when it was implemented.
Thanks Paul. I've read on page 19 of www.progress.com/.../Track%205%20-%20Getting%20the%20Most%20Out%20of%20Virtualization%20of%20Your%20Progress%20OpenEdge%20Environment_v1.pdf that taking the snaps willy nilly can cause db down. Is that a concern with Veeam?
We're in the process of upgrading our infrastructure and have been edged into the VMWare world. We've been having discussions around the use of Veeam for backups (initiated by the vendor, not us). Is it worth entertaining Veeam at all? We'd probably still want to do probkup for the actual databases, it's more the rest of the box configuration I guess...
I'm aware that we would need to use freeze and thaw scripts (proquiet), but how long would the proquiet be active for? Is it just for the snap, or is it for the whole process?
Any other comments?
Flag this post as spam/abuse.
1) Use VEEAM w/ proquiet and the scripts – if you will be snapshotting the VM where the database is regardless, you have to use the pre/post freeze scripts
2) Have another disk on the VM, set its type to independent (it’s by default excluded from snapshots), have a database there and use probkup online to backup it up.
Thanks Paul. I've read on page 19 of www.progress.com/.../Track%205%20-%20Getting%20the%20Most%20Out%20of%20Virtualization%20of%20Your%20Progress%20OpenEdge%20Environment_v1.pdf that taking the snaps willy nilly can cause db down. Is that a concern with Veeam?
Flag this post as spam/abuse.
Thanks everyone - really helpful. I think the best bet for us is to have the databases and associated files on a disk that's not covered by Veeam. I will pass that on to the vendor.