Salta al contenuto principale

Starting a different backup on completion of a different one

Thread needs solution

Hi All

I am backing up my full server using full / inc / inc.. etc... Once the full or inc backup completes I want to start an exchange backup on a simple full backup each time.

I did have some success initially using the event logs option but that seems to have stopped working.

Does anyone have any better ideas?

Thanks

K

0 Users found this helpful

Please be clarify. What is wrong ?
Do you have the exchange license ?

Hello Kerry,

at the moment there is no special scheduling option to start backup after another backup task is completed but I'll register your request in our Customer Listening System and it will be considered by our development by working on next versions.

Thank you.

Hi Kerry,

From your message it is not quite clear what you mean, however I will try explaining what we have for now.

1) If you mean you use two separate Acronis products (Acronis Backup Advanced (to back up disks) + Acronis Backup Advanced for Exchange (to back up Exchange)) than it should work properly nowadays as well - the backup plan started by one product should block another from starting its backup plan. So, the second product's backup plan will start as soon as the first's will be completed.

2) If you mean you use one product for backup disks (Acronis Backup Advanced) and you back up two servers (one of them you call Exchange), than you right - if you schedule a backup plan to back both machines up, their backup plans will start simultaneously.

It causes issues with overloading storage (when many machines try saving their backups to the same storage) and in Acronis Backup 12 there will be an option to set up a limit for machines running their backup plans simultaneously.

For now to workaround #2 you can use "Distribute start time within the time window" option scheduling a centralized backup plan. For more details look at this KB article - http://www.acronis.com/en-us/support/documentation/ABR11.5/index.html#3… .

Hope, that helps.