Backup Job setup

[SuperStrike]

I have been reading a lot and watched some tutorials on YouTube, now I have made some backup using Veeam Backup & Replication

Just two questions I am not clear.

1) One of the Linux VM - I would like to run a 'Backup Job' every hour during business hours (9AM to 8PM) on Monday to Friday. Synthetic Full Backup every 2 weeks on Saturday. I am confused how this should be setup.

On the Backup Job setting:
- on the storage tab: restore point to keep on disk: ???
- on the storage tab: Advanced -> Incremental
- on the storage tab: Advanced -> Create synthetic full backups periodontally on Saturday
- on the schedule tab: periodontally every: 1 hour with time/day setup.

2) Recently I have bought Veeam Backup & Replication licence but I have been running Veeam Endpoint Backup for many months. Veeam Endpoint is set to backup Drive E:\ daily on Windows Server 2012 VM using "Volume Level Backup" option. On Drive E:\ it is mainly shared folders and users profile. Now I have ability to backup Windows Server 2012 VM using Veeam Backup & Replication, does that mean it is no longer need Veeam Endpoint? Veeam Endpoint has been useful for where I can restore some files which also include files/folders permissions.

The settings/AD/GOP on Windows Server very rarely get updated. Only shared folders on Drive E get updated a lot.

In the Backup Job, it will have Windows Server DC1 and Windows Server DC2

Only Windows Server DC2 will have Drive E

I like to to make full backup of Windows Server 2012 VM every month but backup Drive E:\ daily. Is this good way to do it or what is your suggestion?

[nielsengelen]

1) Restore points on disk is how many points/files you want to keep (full & incremental). For example if you define 7 restore points and backup every 1 hour you will have 7 hours of backups. If you make a backup every day it means 7 days.

2) You can use Veeam Backup & Replication for this VM as it offers the same File Level Restore option as Veeam Endpoint Backup.

In regards to making a full backup every month, this will make a full backup of the whole server (as you can't exclude a disk specific for the full backup job without changing it manually). This is however a matter of choice/personal favor.

[SuperStrike]

Thank you!

Is there anything I can do to improve the Process Rate?

Initial Full backup: 45-50MB/s Process Rate on most VM's.
Incremental Backup: 16-24MB/s Process Rate

Currently have 1 ESXi host with local storage in Raid 1 (raid hardware).
It get backup to QNAP (single HHD at the moment) with 1Gbit connection, using CIFS to transfer backup.

Veeam Backup & Replication is installed on same the ESXi host, 5GB Ram and 3 CPU cores.


Initial Full backup:

Code: Select all

25/01/2016 11:48:38 :: Queued for processing at 25/01/2016 11:48:38 
25/01/2016 11:48:38 :: Required backup infrastructure resources have been assigned 
25/01/2016 11:48:44 :: VM processing started at 25/01/2016 11:48:44 
25/01/2016 11:48:44 :: VM size: 45.0 GB (44.9 GB used) 
25/01/2016 11:49:25 :: Getting VM info from vSphere 
25/01/2016 11:49:56 :: VMware Tools are not up to date, some functionality may be affected 
25/01/2016 11:50:01 :: Using guest interaction proxy 3DBackup (Same subnet) 
25/01/2016 11:50:03 :: Inventorying guest system 
25/01/2016 11:50:05 :: Preparing guest for hot backup 
25/01/2016 11:50:09 :: Creating snapshot 
25/01/2016 11:50:16 :: Releasing guest 
25/01/2016 11:50:16 :: Getting list of guest file system local users 
25/01/2016 11:50:21 :: Saving [OS] Windows Server 2012 DC1/Windows Server 2012 DC1.vmx 
25/01/2016 11:50:21 :: Saving [OS] Windows Server 2012 DC1/Windows Server 2012 DC1.vmxf 
25/01/2016 11:50:22 :: Saving [OS] Windows Server 2012 DC1/Windows Server 2012 DC1.nvram 
25/01/2016 11:50:24 :: Using backup proxy VMware Backup Proxy for disk Hard disk 1 [hotadd] 
25/01/2016 11:51:02 :: Hard disk 1 (45.0 GB) 29.3 GB read at 69 MB/s [CBT]
25/01/2016 11:59:28 :: Removing VM snapshot 
25/01/2016 11:59:56 :: Saving GuestMembers.xml 
25/01/2016 12:00:40 :: Finalizing 
25/01/2016 12:00:42 :: Truncating transaction logs 
25/01/2016 12:00:47 :: Swap file blocks skipped: 892.0 MB 
25/01/2016 12:00:49 :: Busy: Source 28% > Proxy 31% > Network 15% > Target 84% 
25/01/2016 12:00:50 :: Primary bottleneck: Target 
25/01/2016 12:00:50 :: Network traffic verification detected no corrupted blocks 
25/01/2016 12:00:50 :: Processing finished at 25/01/2016 12:00:50  

Incremental Backup:

Code: Select all

25/01/2016 13:37:11 :: Queued for processing at 25/01/2016 13:37:11 
25/01/2016 13:37:11 :: Required backup infrastructure resources have been assigned 
25/01/2016 13:37:16 :: VM processing started at 25/01/2016 13:37:16 
25/01/2016 13:37:16 :: VM size: 45.0 GB (44.9 GB used) 
25/01/2016 13:37:59 :: Getting VM info from vSphere 
25/01/2016 13:38:01 :: VMware Tools are not up to date, some functionality may be affected 
25/01/2016 13:38:06 :: Using guest interaction proxy 3DBackup (Same subnet) 
25/01/2016 13:38:08 :: Inventorying guest system 
25/01/2016 13:38:10 :: Preparing guest for hot backup 
25/01/2016 13:38:13 :: Creating snapshot 
25/01/2016 13:38:19 :: Releasing guest 
25/01/2016 13:38:20 :: Getting list of guest file system local users 
25/01/2016 13:38:24 :: Saving [OS] Windows Server 2012 DC1/Windows Server 2012 DC1.vmx 
25/01/2016 13:38:24 :: Saving [OS] Windows Server 2012 DC1/Windows Server 2012 DC1.vmxf 
25/01/2016 13:38:25 :: Saving [OS] Windows Server 2012 DC1/Windows Server 2012 DC1.nvram 
25/01/2016 13:38:27 :: Using backup proxy VMware Backup Proxy for disk Hard disk 1 [hotadd] 
25/01/2016 13:39:10 :: Hard disk 1 (45.0 GB) 809.0 MB read at 12 MB/s [CBT]
25/01/2016 13:40:42 :: Removing VM snapshot 
25/01/2016 13:41:01 :: Saving GuestMembers.xml 
25/01/2016 13:41:04 :: Finalizing 
25/01/2016 13:41:04 :: Truncating transaction logs 
25/01/2016 13:41:11 :: Busy: Source 98% > Proxy 64% > Network 1% > Target 0% 
25/01/2016 13:41:11 :: Primary bottleneck: Source 
25/01/2016 13:41:11 :: Network traffic verification detected no corrupted blocks 
25/01/2016 13:41:11 :: Processing finished at 25/01/2016 13:41:11

[foggy]

Any chance the source storage was busy with some other tasks at the moment of incremental backup? According to bottleneck stats, it just was not able to provide data faster.

[SuperStrike]

There was no other tasks during incremental backup.

Other Incremental few minutes ago, different VM

Code: Select all

25/01/2016 16:00:29 :: Queued for processing at 25/01/2016 16:00:29 
25/01/2016 16:00:29 :: Required backup infrastructure resources have been assigned 
25/01/2016 16:00:34 :: VM processing started at 25/01/2016 16:00:34 
25/01/2016 16:00:34 :: VM size: 86.0 GB (83.6 GB used) 
25/01/2016 16:01:19 :: Getting VM info from vSphere 
25/01/2016 16:01:20 :: Creating VM snapshot 
25/01/2016 16:01:32 :: Saving [OS] Sales Manager/Sales Manager.vmx 
25/01/2016 16:01:33 :: Saving [OS] Sales Manager/Sales Manager.vmxf 
25/01/2016 16:01:33 :: Saving [OS] Sales Manager/Sales Manager.nvram 
25/01/2016 16:01:34 :: Using backup proxy VMware Backup Proxy for disk Hard disk 1 [hotadd] 
25/01/2016 16:01:34 :: Using backup proxy VMware Backup Proxy for disk Hard disk 2 [hotadd] 
25/01/2016 16:02:07 :: Hard disk 1 (36.0 GB) 244.0 MB read at 49 MB/s [CBT]
25/01/2016 16:02:34 :: Hard disk 2 (50.0 GB) 0.0 KB read at 0 KB/s [CBT]
25/01/2016 16:03:08 :: Removing VM snapshot 
25/01/2016 16:03:35 :: Finalizing 
25/01/2016 16:03:37 :: Busy: Source 91% > Proxy 38% > Network 0% > Target 19% 
25/01/2016 16:03:37 :: Primary bottleneck: Source 
25/01/2016 16:03:37 :: Network traffic verification detected no corrupted blocks 
25/01/2016 16:03:37 :: Processing finished at 25/01/2016 16:03:37