Veeam Installation



  • G'Day Lads and Lasses,

    I'm Installing Veeam B&R 7 on it's own server and I'd like to check a few things before completing the installation:

    • Is it best practice/a good idea to install Veeam onto a different drive to the OS (eg Install on K: instead of C:)?
    • Should I use a local SQL Express Installation or use a seperate SQL server?

    Also, in the EULA (Yes, I read it šŸ˜› ) it stated that Veeam could essentially check up on my stuff to ensure that we were abiding by the EULA.

    • How do they go about this?
    • Has anyone had this happen to them?

    Ā 
    Ā 

    (Topic thumbnail added because I can :P)



  • Where does the topic thumbnail show up?



  • ML 20140527 001.jpg
    Well... in the circle on the topic board (Thread listing/doova-lackey/unruly list of threads) šŸ™‚



  • Ah ha, it only shows up in the "category" screen, not on the unread or recent screens.



  • /Threadjack



  • I don't think having Veeam on another drive makes sense. The data store, yes, but not the application.



    1. No issues with that. Just make sure that the VB&R installation is protected. You can ensure it with the use of configuration backup.
    2. How big your infrastructure is? We typically recommend using full SQL for infrastructures bigger than 1000 VMs.. Otherwise, SQL express is more than enough.

    Thanks.



  • I replied to your other post earlier this morning:
    http://community.spiceworks.com/topic/post/3353674



  • I agree with @Vladimir-Eremin about the config backup. Make sure you are doing this daily. I recently had to restore a configuration backup because I rebuilt my Veeam server, and it saved me a ton of setup time. As for the SQL install, I think Express makes the most sense if you can do it. That way your Veeam server is self-contained, and you don't have to worry about having your Veeam server and a separate SQL Server up to be able to restore from backup in an emergency.



  • A small trick regarding usage of configuration backup.

    If you have a network share, you can create a share disk, map it to instance of VB&R and use as a target repository for configuration backup. Should any disaster situation happen (VB&R server goes down, for instance), all you would need to do is to install Veeam on any other virtual/physcial machine and import previously backed up configuration.

    Thanks.



  • @Vladimir-Eremin said:

    A small trick regarding usage of configuration backup.

    If you have a network share, you can create a share disk, map it to instance of VB&R and use as a target repository for configuration backup. Should any disaster situation happen (VB&R server goes down, for instance), all you would need to do is to install Veeam on any other virtual/physcial machine and import previously backed up configuration.

    Thanks.

    Or, if you have the free space available, make a replica of your Veeam server and a domain controller, then put them in the same location as your backup.



  • Thanks you all for your responses šŸ™‚

    I'll definitely be configuring the Configuration Backup as suggested.

    @alexntg said:

    I replied to your other post earlier this morning:
    http://community.spiceworks.com/topic/post/3353674

    @alexntg I saw that. šŸ™‚ Double thanks to you šŸ˜› I posted in two places for a wider catchment of opinions... and I'm a bit impatient sometimes.


Log in to reply