Lines Matching full:2012

143 …peration actually started in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
148 …is operation was enqueued in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
159 …e this operation finished in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
181 …uring which this the backup was attempted in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
182 …time the run was enqueued in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
184 …peration actually started in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
190 …ackup operation completed in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
211 …uring which this the backup was attempted in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
212 …time the run was enqueued in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
214 …peration actually started in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
220 …ackup operation completed in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
268 …peration actually started in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
273 …is operation was enqueued in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
284 …e this operation finished in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
310 …uring which this the backup was attempted in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
311 …time the run was enqueued in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
313 …peration actually started in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.
319 …ackup operation completed in UTC timezone in RFC 3339 format, for example 2012-11-15T16:19:00.094Z.