Install on Server Core 2008 R2

[spgsit5upport]

Is that supported?

Just tried & I get error on Console start

Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))

Most of the menus do not work

Seb

[Gostev]

As far as actual backup server, no this is not supported. However, backup proxies and backup repositories are supported on Windows Server Core. Thanks!

[spgsit5upport]

Pity, really

Would you at least have an idea WHAT is causing it (obviously something missing)

Seb

[Gostev]

Well, truly the Server Core has a lot of stuff "missing"... this is what core edition is all about. There is little sense of installing Server Core, and then rolling all missing components back - as in that case, you'd better off installing full blown server in this case.

Generally speaking, "native" code works fine on server core. However, everything that uses .NET (such as Veeam Backup server) is not a good candidate for core installs. Basically, the whole B&R UI is written in .NET...

[spgsit5upport]

I wish .net was never invented

Core is great, and certainly for Veeam backup it should be a good candidate (as it does not run anything GUI related)

For me once the jobs are being created & run on schedule & the success mails tgets to my mailbox, I really do NOT need to access it at all

.net 4 for Core exists - http://www.satter.org/2011/04/net-4-on-server-core.html

Yet it does NOT make Veeam backup console run

Seb

[dellock6]

You can use a single Full Installation as Backup Server, ignore all its proxy and repositories functions, and let it act like a central control station. From here you can control a number of proxies, all installed on Windows Core Installations. A nice feature would be the possibility to complete disable proxy and repository functions of the backup server.

regards,
Luca.

[spgsit5upport]

Thanks, good to know.

But for an upgrade from working fine v5 (to test it), it will require additional 2 servers (one for full install & Core for repository)

Why do I use Core? Because it does almost (?!) all I need running off 8 Gb USb SSD (something that I could not do with full install)

Seb

[dellock6]

how many nodes are you using right now with v5? The central server can also act as a proxy if you want.
Also, repository can also be a NAS server with CIFS shares, is not mandatory to be a veeam server, only thing you need is the proxy should be able to reach the repository. For example we are using exagrid storages on many installations as rpositories.

Luca.

[spgsit5upport]

My Core server IS the server with CIFS shares

And the server that runs backup needs to have SAN access (iSCSI in my case), which is handy, as the core has just that

Seb

[Gostev]

.net 4 for Core exists - http://www.satter.org/2011/04/net-4-on-server-core.html
Yet it does NOT make Veeam backup console run

Sure thing - Veeam B&R was built on .NET 2.0... version 4.0 is fairly new, however we are planning to move to it (for unrelated reasons) down the road, so this might help.

Good point on why you are using Core.

[spgsit5upport]

.NET 2.0 can also be installed on Core:

http://blogs.technet.com/b/server_core/ ... 08-r2.aspx

But it does not make it work, hence it would be nice which bit is actually missing. Surely developers know?

Seb

[spgsit5upport]

I can see that Veeam.Backup.Shell.exe uses the following (all are available in Core 2008 R2 SP1)

mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Veeam.Backup.Common, Version=6.0.0.0, Culture=neutral, PublicKeyToken=bfd684de2276783a
Veeam.Backup.Core, Version=6.0.0.0, Culture=neutral, PublicKeyToken=bfd684de2276783a
Veeam.Backup.DBManager, Version=6.0.0.0, Culture=neutral, PublicKeyToken=bfd684de2276783a
Veeam.Backup.UI, Version=6.0.0.0, Culture=neutral, PublicKeyToken=bfd684de2276783a

Seb