# Configure drbd on proxmox

**URL:** <https://forums.linbit.com/t/configure-drbd-on-proxmox/286>\
**Category:** Proxmox VE\
**Created:** [September 7, 2024, 9:00am UTC](https://forums.linbit.com/t/configure-drbd-on-proxmox/286 "2024-09-07T09:00:47Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kermat](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/kermat/32/21_2.png) [@kermat](https://forums.linbit.com/u/kermat)\
**Post date:** [September 11, 2024, 2:13pm UTC](https://forums.linbit.com/t/configure-drbd-on-proxmox/286/2 "2024-09-11T14:13:28Z")

</div>

> [@youzersef](#):
>
> 1- when the pve01 goes down. the drbd storage is not anymore reachable. Should i configure keepalived on 2 servers with virtual ip? Or is there better way that i can learn it?

If you followed the [LINSTOR user’s guide section](https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-linstor_ha) that uses DRBD Reactor to make the LINSTOR controller highly available, you need at least three nodes in your cluster. This is because DRBD Reactor uses DRBD’s quorum status to promote resources.

Keepalived or Pacemaker could be used instead when you only have two nodes.

> [@youzersef](#):
>
> a client tried to write a data on the drbd storage. then Power failure happened. How many Data we lost? To answer on this quotation i wrote the following script on a test-vm.
> 
> ```auto
> #!/bin/bash
> 
> duartion=300
> 
> for((i0; i<$duartion; i++)) do
> current_time=$(date +"%Y-%m-%d %H:%M:%S")
> echo $current_time >> foo.txt
> echo $current_time
> sleep 1
> done
> 
> ```

You shouldn’t lose any data. Perhaps the writes are stuck in buffers somewhere. Try adding a `sync` to your script to test this:

```shell
#!/bin/bash

duartion=300

for((i0; i<$duartion; i++)) do
  current_time=$(date +"%Y-%m-%d %H:%M:%S")
  echo $current_time >> foo.txt; sync
  echo $current_time
  sleep 1
done

```

---

_[View the full topic](https://forums.linbit.com/t/configure-drbd-on-proxmox/286)._