timing multiple schedules instead of using reserve copy
Hi,
I have two backup targets (local disks and network share), and naively thought that the "reserve copy" would be an actual copy. Unfortunately the description is misleading as I now find in some older threads.
"Reserve Copy" is actually a full backup .... not a copy .... and not a copy that even applies the desired backup scheme or version controls.
Anyway.... I want a differential scheme on both targets so the "full" reserve "copy" made by Acronis every increment is unnacceptable for my needs.
I am now running 2 shedules - one for each target.
My system relies on waking required devices, performing backup and then a scripted shutdown.
Is there a way to tell one backup to run sequentially after another? I've made a time estimate of when the second task should begin but it would be more efficient to have one begin directly after the other.
Maybe their is a scripted command I can use to begin the second task? I could use the "post Commands" of the first backup to initiate the second?
If that is possible would I setup the second to not have a schedule and only be done on-demand? (wasn't sure if differential could be selected for a one off backup though).
Pat - that should work. I tested Grover's guide before. Add something like that to the post backup job script and it should automatically start that backup as soon as the first one is complete.
http://forum.acronis.com/forum/109820#comment-321040
Change the script number from my example to the script number for your users script number which created the backup task. When done, substitute your script # and paste the entire command into a desktop shortcut
"C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageLauncher.exe" /script:A08C9DCC-EA95-4EF7-A34B-722EA3E3C43E
Thanks guys.
I'm actually playing with this on a system with TI 2014 on it but will need it for my laptop/Ti 2016 setup as well.
I have a .cmd for the post backup shutdown and control of my NAS. I'll just make another small one to run this command post the first backup. With direct command line control a lack of shortcut facility should not be a problem.
Edit: Seems pretty simple in theory. Worked out the id for my second backup scheme and made "Backup to NAS.cmd" with the command in there.
Edited the backup scheme to have no schedule, but maintain the cleanup options I want.
Edit the first backup schedule to inlude the cmd file as a post command.
My setup now provides what I have been working toward without having to fudge timeframes or leave devices running when not required.
1. daily backup to a local HDD and NAS (Full with 6 differentials, max 2 full backup versions).
2. Access to the NAS backup share is through restricted credentials so my PC cannot be a viral/worm source and knock out my backups.
3. NAS powers on 2am, wakes PC. PC conducts backups then shuts down the NAS and itself (using batch files.... the Acronis shutdown kept creating errors).
Have another quick question now that I'm usign a script insead of acronis schedule....
Should a Differential backup, with version limits and cleanup work when it is set to "not scheduled" ?
I have my .cmd file calling a differential backup to store on my NAS as a post-command (in my local backup scheme)..... and it has simply been producing a "Full" backup each day... no differentials.
I deleted the entire backup scheme for the NAS and started one from scratch *just in case* it's a problem from editing and changing it (had that occur before), but wanted to check if it's just a fundamental issue with the way scheduling and backups work.
If it is, how can I have one backup complete, then call the next backup and have it function as a differential with cleanup rules?
I've got a feeling I may have discovered another Acronis oddity but wanted to check with more experienced hands :)
mrgobins, something has to start the intial job - if it is not scheduled, you would have to manually run it whenever you want. As long as the correct backup task is being called, as far as I know, cleanup and version chains should still apply since it's the task ID in your script that is being called on and would already be configured through Acronis. This can be accomplished either in the scheduled task in Acronis or as a scheduled task through Windows task scheduler to automate the process. However, itt sounds like you have it setup correctly with a batch script that I'm guessing is being initiated with Windows task scheduler.
Keep in mind that every time you edit a scheduled task and save it in Acronis, it will restart the version chain so you may just have to let it run once or twice to get it to start the diffs.
So, if I read your last response correctly, you have a single diff backup configured in Acronis, and you are running it via Windows task scheduler from another .bat file script, but are only getting fulls?
When I have time, I can try to replicate the setup using task scheduler as well and manually kick it off a few times to see if they are all fulls or result in diffs like they are supposed to.
Yes I have the appropriate scheduling in place to call scripts and control the hardware I need.
I will monitor the "non-scheduled" backup scheme being called by my scripting and see if it properly develops the full/differential backups it should as well as cleanup activity. It may have been a bug created by copying the other backup scheme or editing.
To clarify my setup if you do feel like testing:
I run 2 backup schemes of the same backup (but to 2 different targets - one a local HDD in my PC and the other a share on my NAS).
*Originally used "reserve copy" but it only does "full" backups and will not apply a version scheme.
1. NAS powers on per its set schedule and powers PC on via WOL.
2. Acronis runs scheduled local backup scheme to HDD.
3. On completion of local backup a "post-command" is triggered that calls the non-scheduled differential scheme to backup to the NAS target.
4. On completion both devices shut down.
Step 3 was producing only full backups for 7 days straight on the NAS. The backup scheme was set to do differentials (in fact was a copy of the local backup scheme and only had the target changed, and schedule disabled).
Keep in mind that every time you edit a scheduled task and save it in Acronis, it will restart the version chain so you may just have to let it run once or twice to get it to start the diffs.
It has been my experience, the most frequent cause of a task not workiing is the little tweaks the user keeps making to the original task. Sometimes the the task will recover as the quote indicates and other times it will not. Sometime the success/failure depends upon what is being changed. My recommendation in all instances has been if a change is needed, start a new task with he correct settings. A backup initiated via a post command should act no differently than one issued either via schedule or non-scheduled. The dif should run next after the first full.
If you have some spare time, this link is s small compilation of settings which I have found to work for me.
It hasn't been a case of editing settings and the scheme restarting. It was set and then monitored for 7 days.
I concur with your comment regarding reliability after some aspects are altered. I've had issues with shares being accessible (credentials), and backup method.
I simply deleted all backups and started from scratch.