rpandey
ADSM.ORG Member
I got a quick question to ask about the Monthly full backup using SP4VE for VMware ESX VMs.
We have daily data mover and daily datacenter nodes configured for Incremental Forever-Incremental backups, and we also have monthly data mover and monthly datacenter nodes configured for monthly backups using IF-Full mode, both are using SP4VE
The monthly SP4VE backup is scheduled to start on the first Saturday of each month at 10:00am, daily SP4VE backup is scheduled to start at 10:00pm each night.
Out problem is that some of the VM's monthly full SP4VE backup overran past 10:00pm on Saturday, when the daily incremental SP4VE backup started for the same VM at 10:00pm, the daily incremental backup job deleted the VM snapshot which was created by the monthly backup job for the same VM and then created a new snapshot for daily incremental backup, it caused the monthly backup for that VM failed.
Is there any way to stop one SP4VE backup job deleting the snapshot of the same VM which was created by different backup job from different data mover?
Or, has anyone encountered the same problem and what is the resolution?
We have daily data mover and daily datacenter nodes configured for Incremental Forever-Incremental backups, and we also have monthly data mover and monthly datacenter nodes configured for monthly backups using IF-Full mode, both are using SP4VE
The monthly SP4VE backup is scheduled to start on the first Saturday of each month at 10:00am, daily SP4VE backup is scheduled to start at 10:00pm each night.
Out problem is that some of the VM's monthly full SP4VE backup overran past 10:00pm on Saturday, when the daily incremental SP4VE backup started for the same VM at 10:00pm, the daily incremental backup job deleted the VM snapshot which was created by the monthly backup job for the same VM and then created a new snapshot for daily incremental backup, it caused the monthly backup for that VM failed.
Is there any way to stop one SP4VE backup job deleting the snapshot of the same VM which was created by different backup job from different data mover?
Or, has anyone encountered the same problem and what is the resolution?