SQL for Veeam (installing)

[Koldov]

Could someone please explain how to add Veeam 'instance' to SQL please (Eli5).

 

I have a Windows server, I have Microsoft SQL so when installing Veeam I just point somewhere and it creates a database, right?! Apparently not...

 

Then I chose the default PostgreSQL and I'm having all sorts of issues with that because the server is too locked down or something... ('can't write to Temp and Script host isn't enabled')...

 

So I just want this done as my WSB is failing and giving me general issues and thought Veeam was the way to go. I installed it on my other server and didn't seem to have this much hassle at the first hurdle (plenty more to come though I'm sure).

 

It's an old SIMS server, so SQL is there still, but this seems to be the only 'instance' I can choose... obviously I don't want it there.

 

The terminology always throws me too as I rarely ever look at SQL.

 

HOST - Is the server (OS)

 

SERVER - Is the SQL server

 

INSTANCE - Is the ???

 

DATABASE - Is the database

Edited December 7, 2023 by Koldov

[DavR]

Veeam should be installed in it's own instance, so SERVERNAME\VEEAM12 or whatever. Don't install it into an existing instance, unless it's an existing Veeam instance and you're upgrading. I think it might also need a separate instance for logs/config as well, it's been a while since I've installed Veeam.

 

The installer should let you create a new instance just for this, and it will configure it the way that it needs. If for some reason it isn't, do you have the option to clear all existing SQL instances off that server? That way it will force the installer to sort out it's own SQL needs.

[Koldov]

Yeah, I was hoping it would do exactly that but I can't seem to find the part of the installer that does it!

 

At that point it appears to be asking for the instance (provides the SIMS instance as default) and doesn't really appear to have anywhere to say 'tick a box to create a new one'...

 

I 'could' clear out all other instances, however this was an old SIMS server (now dormant) and although I've now moved SIMS off to its own VM and it appears to be working OK, I'm a bit reticent (to say the least) of completely killing it 'just in case'... I mean who knows in a year or so if something happens and the answer to fix it lies in the files/settings/database sitting on that server and I've deleted everything...

 

I'll keep trying to figure it out today, but is there anyway to 'make' an instance that I can point the Veeam installer to?

[2ilent8cho]

The terminology always throws me too as I rarely ever look at SQL.

 

HOST - Is the server (OS)

 

SERVER - Is the SQL server

 

INSTANCE - Is the ???

 

DATABASE - Is the database

Think of the Instance as a SQL Server. You can have more than 1 instance, and each one can have its own files, databases and security. The best analogy I can think of (though analogies don't always translate perfectly), is think of each Instance being a HyperV VM on a Hyper V Server. So you have HOST = Windows Server 2019, Server = HyperV , Instance = HyperV VM , Database = The data on the VM.

[Koldov]

Thanks all, I may have to rethink this though as I'm guessing I have just shot myself in the foot....

 

Considering this is our recently mothballed ex-SIMS server and as I have only just cut over in the last couple of months I kept everything 'as is' in stasis and just disabled the SQL services for SIMS.

 

But here's where I still don't get the terminology...

 

If I wanted to keep the 'SQL Server (SIMS2014)' down but still use SQL for Veeam, how is that possible? It seems as if it should be...

 

[DavR]

I had a quick Google - it turns out Veeam B&R doesn't include SQL any more. You must either create a new instance in PostgreSQL, or, install the Veeam database into an existing SQL instance - https://www.reddit.com/r/Veeam/comments/12hab4t/when_installing_veeam_backup_12_fresh_can_you/.

 

I really wouldn't attach that database to another SQL instance, so looks like you'll be needing to use PostgeSQL as per this guide.

[Koldov]

I went nuclear and downloaded SQL Server 2019 (as I'd read you can install more than one version)... installed that and pointed it there to create its own instance.

 

Seems to have worked OK...

[DavR]

Yup, that'll do it!