ABR 11.5 Advanced Workstation - Backup Plan Time

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 7
Comments: 13

Hi there,

*I'm making only local backups on my PC clients and because I have Clients from different time zones (mixed together in the same plans), I have noticed something:

My 1st backup plan is triggered once a day 8.00h (volume backups)
My 2nd backup plan is triggered every hour (file based)

The plans and logs for my clients, with the same time zone as my AMS, look fine (they just have all the same timestamp as the AMS).

But as I mentioned, I have also clients in other time zones (+1h).
So in the AMS i see my 1st back up triggered for 7.00h and all logs say the same. And also it is done with the local time at 7.00. That is 1 hour too early.
But my 2nd backup (file based, hourly) has the same timestamp as my AMS.

Volume backups, triggered once a day, show logs/plans with the timestamp, from the Client PC's. The file based hourly backups, show the same time as the AMS. I have created even new jobs (clones), but it stays that way.

Where does this difference come from?
Are the backups always made by the AMS time? And because the hourly Backups are cyclic, is it just coincidence, that they look fine?

Wed, 11/13/2013 - 15:55
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 0
Comments: 1379

>And because the hourly Backups are cyclic, is it just coincidence, that they look fine?
Definitely yes.

> Are the backups always made by the AMS time?
IIRC, at least regularly scheduled backups are scheduled at the local time for the agent that will actually execute the backup. So if you schedule backup 'at 7:00' - they will be executed on each agent at 7:00 its local time.
Information in logs is stored in UTC time and in most cases converted to string in the console, in the timezone and locale format of the machine where console is running, that's why you can see them 1 hour early.

Wed, 11/13/2013 - 17:29