About servers …

[Namiga]

Let's see if I can explain myself clearly... I'm a bit thick-headed today ;D

I have a client who asks me to set up a guarantee server... but he wants to have a second server in case the first one fails... in a redundant way, that takes control if the first one fails

The bad thing is the data, which must be visible at all times...

The little I know about redundant servers is that they need a storage cabinet, and there the costs skyrocket:llorar:

The question is... is there a way to have redundant servers with shared data without it costing an arm and a leg??

The NAS option as a cabinet doesn't seem very clear to me because of performance issues...

Does anyone know what can be done???

Best regards and thanks

[krampak]

Have you looked into the topic of virtualization like vmware? It might be the easiest way to set up a backup server.

[Namiga]

Well that's what I'm looking at now …. to see how I can do it... What I see as non-negotiable is the issue of if a server breaks down the company doesn't stop... They want to have a second one as a backup... I think what I'll do is set them both up the same and every x amount of time make a copy of the database to a NAS... if it comes to it, put the new server up and dump the last backup... something will be lost... but it will be 15 minutes of work... not days like it is now...

[kynes]

An rsync with a daemon and off you go?

[Bm4n]

I think a network mirror raid and virtual execution on a redundant server would be the most economical.

Sent from my iPad with Tapatalk

[Yorus]

If the server is also a domain server it will be more complicated. A while ago I was looking into how to do it and it was not at all straightforward.

The virtual machines could be a solution, keeping the system and data separate and making a copy of everything every so often. Being virtualized, it can always be brought up on different hardware, although I am not sure if it would cause problems with a domain.

If it is just data, perhaps what Kynes says would work, they would just have to point the posts to the new location and that would be it.

R Tape loading error, 0:1

[Namiga]

In the end the topic is postponed a little... these clients who never decide

Which gives me time to try things out with virtual machines.. and in the process learn...

kynes: I'll look into what rsync is

Bm4n: Network mirror raid... without knowing much it sounds like a storage cabinet... that will be expensive...

Yorus: In principle it is not mandatory that it is a domain controller... The application would have clients that would connect via TS... that's all that's known so far...

I've seen something about a program called starwind. It seems to be a "storage cabinet" emulator...

I'll investigate that...

Thanks to all for the suggestions

[Bm4n]

Maybe just a two-disk NAS in RAID 0 that stores the program and data and a server that runs them remotely could work and would be cheap. If a disk in the NAS breaks, you just need to replace it and if the server breaks, another one can be turned on and access the same program and data from the NAS.

Of course, it depends on the workload, maybe they need something more professional.

From my Honor 6+ @Tapatalk

[faliqui]

I'm sorry for the delay, although I hope it's in time to offer you other solutions.

It always depends on the money and the criticality you have as requirements for the solution.

I propose what I would do:

- A lot of money and critical environment

Cabinet with fiber links at 8 Gbits/s over SAN network, all disks in RAID5

- Critical environment and not a lot of money

Set up GPFS on the machines and share local disks (requires license). It's cheaper than a cabinet but the performance is not the same.

- Critical environment and no money

Set up a NAS with iSCSI support (with a G8 microserver it's enough) and put the disks with the data there.

- Non-critical environment and no money

Set up something like "drdb + heartbeat" to synchronize the disks. The disk would be mounted only on one machine in r/w mode and if the service falls the other node detects it, mounts the disks in r/w and then starts the MySQL database (or whatever it is).

Best regards!!