On Sat, 18 Oct 2014 10:56:18 AM Dietmar Maurer wrote:
> > Maybe a setting in the backup gui when checked prevents running parallel
> > backups could solve this issue?
>
> It is quite easy to setup a separate job for each node.
Not if you need to exclude some vm's, but migrate them regularly for
Oh Dear! Qnap! Pity of you! Qnap has only 128 MB of memory and low
hardware...
Here, I do backup locally, in an External HDD USB
To one server, I saw here around 15-18 MB/s, but there's some ocasion that
I saw less than 10 MB/s
Compare to other server, I saw 60-80 MB/s...
2014-10-18 13
On Sat, 18 Oct 2014 13:03:57 -0300
Gilberto Nunes wrote:
> Well...
>
> I have just one node here, because the other server doesn't arrive yet, but
> I already create the cluster...
> And my backup task are extremaly slow!
> It a file about 23 GB, that take almost 5 hours.
> Ok! I ran backup over
Well...
I have just one node here, because the other server doesn't arrive yet, but
I already create the cluster...
And my backup task are extremaly slow!
It a file about 23 GB, that take almost 5 hours.
Ok! I ran backup over LVM-on-top-iSCSI
VMIDNAMESTATUSTIMESIZEFILENAME 103Windows2012OK04:53:4
> > It is quite easy to setup a separate job for each node.
> >
> I know, but maybe users are not aware of this complication.
> If it can remove a
> lot of "noise" on the forum from people with failing backups I think it is
> worth
> implementing.
1.) I don't think this is the reason for the pr
On Sat, 18 Oct 2014 10:56:18 +
Dietmar Maurer wrote:
>
> It is quite easy to setup a separate job for each node.
>
I know, but maybe users are not aware of this complication. If it can
remove a lot of "noise" on the forum from people with failing backups I
think it is worth implementing.
-
> I just discovered that when Proxmox initiates the configured automatic backup
> it
> runs backups from each node in the cluster in parallel. I wonder whether this
> could be the cause for users now and then see some of the backups fails given
> the backup storage is to slow storage?
>
> Maybe
Hi all,
I just discovered that when Proxmox initiates the configured automatic
backup it runs backups from each node in the cluster in parallel. I
wonder whether this could be the cause for users now and then see some
of the backups fails given the backup storage is to slow storage?
Maybe a setti
> >>We read 64K blocks, so
>
> Don't for for backup, but drive-mirror have a "granulary" option to change the
> block size:
>
> # @granularity: #optional granularity of the dirty bitmap, default is 64K.
> # Must be a power of 2 between 512 and 64M.
Although it would be much easie