vmniels wrote:Just wondering a few things to help here. Could you tell us how big the server is you are trying to backup (or give the output from df -h). I am guessing the digital signing of files by Windows could be causing an issue. Is this server part of a domain or is this a solo setup?
~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 1.9G 0 1.9G 0% /dev
tmpfs 382M 5.6M 377M 2% /run
/dev/mapper/nvidia_fbcfiaca1 226G 58G 157G 27% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 382M 0 382M 0% /run/user/0
vmniels wrote:So if I understand it correct, the Linux VM is running in owncloud and the Windows server as well? The Windows server is isolated from a domain as well so it is a standalone install?
vmniels wrote:Could you try the following on the domain controller:
- Run GPMC.MSC
- Right click on the default domain policy and select edit
- Navigate through the Group Policy Management Editor to Computer Configuration | Policies | Windows Settings | Security Settings | Local Policies | Security Options
- Once there disable the Microsoft Network Server: Digitally Sign Communications (Always) policy. You will also need to disable the Domain Member: Digitally Encrypt or Sign Secure Channel Data (Always) policy.
Then save and close everything and try to run the backup again and see if it improves.
AFAIR you had a bulit-in RAID configured on at least one of them. Do you have a built-in RAID enabled on this machine too?/dev/mapper/nvidia_fbcfiaca1 226G 58G 157G 27% /
<...>I use two HP Microserver, both are physical installations<...>
PTide wrote:AFAIR you had a bulit-in RAID configured on at least one of them. Do you have a built-in RAID enabled on this machine too?
vmniels wrote:I have been checking your logs and I notice a few things. How much memory does this Linux VM have? Also does it have any swap memory? If you can give us the output of 'free -m' we can try to simulate it as well to see what the minimum treshold would be.
I am seeing kills happening on the veeamagent since you are running out of memory so this seems to be the major issue.
# free -m
total used free shared buff/cache available
Mem: 3818 160 3092 16 565 3593
Swap: 3958 115 3843
Users browsing this forum: No registered users and 4 guests