2 backup tasks for same server???
(Preface: I know VMware backup and Recovery would do this. That is outside the scope of what I am trying to accomplish)
Using VMProtect: Can I have 2 tasks running at different times \ days that will backup to 2 different locations?
ie: Backup 1: Backup SERVER1 to Local SAN storage Monday - Friday
ie: Backup 2: Backup SERVER1 to remote SFTP Saturday
Will this cause any issues?
I think you can. Acronis said it can do up to 5 concurrent jobs at a time.
Thanks KJ... But that does not answer my question. I know I can do 5 tasks... But can I do 2 tasks to different locations for one server being backed up? (Not at the same time)
We run multiple backup jobs daily, including backing up single VMs to different locations, haven't experienced any problems so far. As long as the tasks don't overlap, I can't see why there would be a problem.
dear all i had the same questions.
as it works as explained by a.p. on the vmware communities.
http://communities.vmware.com/thread/338752
1. Dec 5, 2011 12:21 PM in response to: MCCS201110141
Re: Changed Block Tracking (CBT) with multiple backups destinations and software types
First you need to understand that CBT is a function of the VMkernel (ESXi) and not the backup software. From how I understand this, ESXi maintains a mapping table (the ctk files) which covers each data block of the virtual disk (the .vmdk file). Once a data block is modified, the time stamp of the modification is written to the according location in the ctk's mapping table. At the time a backup application runs, it requests the list of data blocks with a higher time stamp than the one of the last backup.André
but i still want to actually see it only taking the block difference from the actual backup job
so this calls for testing. as i also finaly only withy vmprotect 7 have it correctly running
Here's a different way to ask the same question. I have a need to replicate locally from server A to server B, but also want to take backups offsite every 4 hours. I don't think CBT will allow for multiple jobs, but it'll be fun! I've got the replication job running, and I'll get the SFTP server setup to upload to.
It may need to be setup with a 'job 1' replicate from A to B, then 'job 2' to backup from B to SFTP - but this would require a second CPU license.
Here's a different way to ask the same question. I have a need to replicate locally from server A to server B, but also want to take backups offsite every 4 hours. I don't think CBT will allow for multiple jobs, but it'll be fun! I've got the replication job running, and I'll get the SFTP server setup to upload to.
It may need to be setup with a 'job 1' replicate from A to B, then 'job 2' to backup from B to SFTP - but this would require a second CPU license.
as you read here
http://communities.vmware.com/thread/338752
a second or third backup job will request all the blocks of a certain timestamp in the ctk files , the ctk files contain an indexes with timestamps of modification of each data block of the virtual disks. and when a backup collects the blocks it requests a list of blocks with a higher timestamp than that of the last backup.
Seems to work - will be doing a test restore soon. Since each job knows it's last time, it goes to the CBT log and asks for all blocks that have changed since time xx:yy:zz you can have multiple jobs backing up the same VM, each one getting correct data.
Also nice to see that the target datastore on a second ESXi host isn't costing a CPU license (only costs on the host) when replicating.