Direkt zum Inhalt

Simultanous Backup & Resize local Storage

Thread needs solution

Hello,

currently we are using the most current vmProtect Appliance for VMware 5.0 & 5.1 Backup.
We have one Backup Task with round about 70 Machines, which needs a long time.
The Task only backups one Machine after another, which takes very long but vmProtect also supports Simultanous Backup. How can i activate this feature? i cant find any options.

We also have a 1TB Local Disc attached to the Appliance for LAN-Free Backup. Is it possible to extend it on the fly through VMware, and does vmProtect recognize the new size, or do i have to reformat the partition?

And last but not least, is it possible due to a ram and cpu upgrade to improve the performance of the appliance? e.g. browsing and deleting recoverypoints takes a very long time.

Thanks a lot in advance

Cheers

Peter

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 22
Kommentare: 3800

Hi Peter,

1) Within the backup task the VMs are backed up one by one. The simultaneousity of the VMs processing can be achieved by creating multiple tasks which are running at the same time. By default the limit is 5 tasks to be running at the same time, which means that you can back up 5 VMs at one time simultaneously. NOTE: the archives must be different ones for these tasks, i.e. you cannot update the same archive by 2 tasks running into it.
2) Simply extending the disk from VMware will just add unallocated space to the already attached disk, but the ext3 1TB volume created on that disk will not be increased automatically. You may notice similar behavior in Windows VMs if you extend their dissk on fly, the logical volumes are not resized automatically. The workaround is either to reformat the drive, or boot the virtual appliance from some disk partitioning software media (for example Acronis Disk Director 11) and resize the 1TB ext3 volume via adding the new unallocated space into it.
3) Yes, the RAM and CPU can be increased on the virtual appliance side. Since appliance is based on 32bit Linux it makes sense to add max. 4GB of RAM into it (all capacity beyond this limit won't be used in any case). RAM is important for recovery points processing and simultaneous backup tasks run. CPU is important when you use high level of compression for backups.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hello Vasily,

thanks for your reply.

1) Then i just have to split my Backup Job of 50 Machines into 5 Jobs a 10 Machines with Different Archives. I will give it try.
2) Then i will create a new 2 TB Storage and leave the old one as it is.
3) are there any best practises default values, in which situation you have to use which amount of ram and cpu ?

Thanks

Peter

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 22
Kommentare: 3800

Hi Peter,

Increasing the RAM on appliance makes sense when you have more than ~400 recovery points (in total from all VMs) stored inside one backup location - in this case increasing RAM helps significantly (2GB will be sufficient in most cases). The main factor here is not the size, but the amount of recovery points since each of them needs to be analyzed which impacts the performance of the GUI. It's better to avoid the growth of the recovery points beyond 3000 theoretical limit (we've tested the performance up to this point) by using proper retention rules in backup task settings.

The CPU will help for parallel processing of multiple jobs into separate archvies when any level of compression or encryption is used. For 5 default parallel tasks 1 CPU should be sufficient (CPU is not the bottleneck here).

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager