Unsolved
This post is more than 5 years old
3 Posts
0
658
Oracle Plug-In V5.0.106-28
Avamar Server V5.0.4 (3.3TB GEN3 Single Node)
Avamar Oracle Client on IBM AIX V6.1
Oracle 10g
My Avamar schedule is set to the following:
Backup Window - 2pm to 6am
Blackout Window - 6am to 9am
Maintenance Window - 9am-2pm
I started a backup at 15:00 today and this is what is reported in the avtar.log:
2011-06-13 15:41:18 avtar Info <5100>: Status 2011-06-13 15:41:18, 41.73 GB (8.212 GB, 19.68% new) 68MB 54% CPU EBSDEV_4gmepnkh_1_1
2011-06-13 15:56:17 avtar Info <5100>: Status 2011-06-13 15:56:17, 53.23 GB (10.03 GB, 18.84% new) 245MB 52% CPU EBSDEV_4fmepnkh_1_1
2011-06-13 15:56:17 avtar Info <5100>: Status 2011-06-13 15:56:17, 54.61 GB (10.85 GB, 19.86% new) 69MB 49% CPU EBSDEV_4gmepnkh_1_1
2011-06-13 15:56:18 avtar Info <5100>: Status 2011-06-13 15:56:18, 54.68 GB (10.59 GB, 19.36% new) 69MB 55% CPU EBSDEV_4hmepnkh_1_1
2011-06-13 16:11:18 avtar Info <5100>: Status 2011-06-13 16:11:18, 67.33 GB (12.61 GB, 18.74% new) 246MB 54% CPU EBSDEV_4fmepnkh_1_1
2011-06-13 16:11:18 avtar Info <5100>: Status 2011-06-13 16:11:18, 68.70 GB (13.32 GB, 19.39% new) 70MB 53% CPU EBSDEV_4hmepnkh_1_1
2011-06-13 16:11:18 avtar Info <5100>: Status 2011-06-13 16:11:18, 67.52 GB (13.47 GB, 19.94% new) 71MB 50% CPU EBSDEV_4gmepnkh_1_1
2011-06-13 16:26:17 avtar Info <5100>: Status 2011-06-13 16:26:17, 80.99 GB (15.13 GB, 18.67% new) 251MB 53% CPU EBSDEV_4fmepnkh_1_1
2011-06-13 16:26:17 avtar Info <5100>: Status 2011-06-13 16:26:17, 83.25 GB (16.11 GB, 19.35% new) 77MB 54% CPU EBSDEV_4hmepnkh_1_1
2011-06-13 16:26:17 avtar Info <5100>: Status 2011-06-13 16:26:17, 80.55 GB (16.11 GB, 20.00% new) 73MB 50% CPU EBSDEV_4gmepnkh_1_1
2011-06-13 16:41:17 avtar Info <5100>: Status 2011-06-13 16:41:17, 93.01 GB (18.67 GB, 20.07% new) 73MB 48% CPU EBSDEV_4gmepnkh_1_1
2011-06-13 16:41:18 avtar Info <5100>: Status 2011-06-13 16:41:18, 95.13 GB (17.70 GB, 18.61% new) 251MB 55% CPU EBSDEV_4fmepnkh_1_1
2011-06-13 16:41:18 avtar Info <5100>: Status 2011-06-13 16:41:18, 97.22 GB (18.88 GB, 19.42% new) 78MB 53% CPU EBSDEV_4hmepnkh_1_1
2011-06-13 16:56:17 avtar Info <5100>: Status 2011-06-13 16:56:17, 103.0 GB (19.24 GB, 18.68% new) 292MB 30% CPU READ-ONLY EBSDEV_4fmepnkh_1_1
2011-06-13 16:56:18 avtar Info <5100>: Status 2011-06-13 16:56:18, 100.2 GB (20.12 GB, 20.07% new) 121MB 28% CPU READ-ONLY EBSDEV_4gmepnkh_1_1
2011-06-13 16:56:18 avtar Info <5100>: Status 2011-06-13 16:56:18, 104.3 GB (20.33 GB, 19.50% new) 121MB 28% CPU READ-ONLY EBSDEV_4hmepnkh_1_1
2011-06-13 17:11:17 avtar Info <5100>: Status 2011-06-13 17:11:17, 117.2 GB (21.97 GB, 18.74% new) 292MB 54% CPU READ-ONLY EBSDEV_4fmepnkh_1_1
2011-06-13 17:11:18 avtar Info <5100>: Status 2011-06-13 17:11:18, 117.7 GB (22.90 GB, 19.45% new) 121MB 51% CPU READ-ONLY EBSDEV_4hmepnkh_1_1
2011-06-13 17:11:18 avtar Info <5100>: Status 2011-06-13 17:11:18, 114.1 GB (22.92 GB, 20.08% new) 121MB 53% CPU READ-ONLY EBSDEV_4gmepnkh_1_1
2011-06-13 17:26:17 avtar Info <5100>: Status 2011-06-13 17:26:17, 132.7 GB (24.90 GB, 18.77% new) 292MB 57% CPU READ-ONLY EBSDEV_4fmepnkh_1_1
2011-06-13 17:26:18 avtar Info <5100>: Status 2011-06-13 17:26:18, 128.9 GB (25.94 GB, 20.12% new) 121MB 56% CPU READ-ONLY EBSDEV_4gmepnkh_1_1
2011-06-13 17:26:18 avtar Info <5100>: Status 2011-06-13 17:26:18, 132.7 GB (25.76 GB, 19.42% new) 121MB 56% CPU READ-ONLY EBSDEV_4hmepnkh_1_1
2011-06-13 17:41:17 avtar Info <5100>: Status 2011-06-13 17:41:17, 147.6 GB (27.79 GB, 18.83% new) 292MB 55% CPU READ-ONLY EBSDEV_4fmepnkh_1_1
2011-06-13 17:41:18 avtar Info <5100>: Status 2011-06-13 17:41:18, 143.0 GB (28.83 GB, 20.16% new) 121MB 54% CPU READ-ONLY EBSDEV_4gmepnkh_1_1
2011-06-13 17:41:18 avtar Info <5100>: Status 2011-06-13 17:41:18, 147.6 GB (28.56 GB, 19.34% new) 121MB 55% CPU READ-ONLY EBSDEV_4hmepnkh_1_1
2011-06-13 17:56:17 avtar Info <5100>: Status 2011-06-13 17:56:17, 163.5 GB (31.55 GB, 19.29% new) 121MB 58% CPU READ-ONLY EBSDEV_4hmepnkh_1_1
2011-06-13 17:56:18 avtar Info <5100>: Status 2011-06-13 17:56:18, 162.6 GB (30.57 GB, 18.79% new) 292MB 63% CPU READ-ONLY EBSDEV_4fmepnkh_1_1
2011-06-13 17:56:18 avtar Info <5100>: Status 2011-06-13 17:56:18, 158.7 GB (31.83 GB, 20.06% new) 121MB 58% CPU READ-ONLY EBSDEV_4gmepnkh_1_1
2011-06-13 18:11:17 avtar Info <5100>: Status 2011-06-13 18:11:17, 177.6 GB (33.44 GB, 18.83% new) 292MB 57% CPU READ-ONLY EBSDEV_4fmepnkh_1_1
2011-06-13 18:11:18 avtar Info <5100>: Status 2011-06-13 18:11:18, 173.4 GB (34.72 GB, 20.02% new) 121MB 52% CPU READ-ONLY EBSDEV_4gmepnkh_1_1
2011-06-13 18:11:18 avtar Info <5100>: Status 2011-06-13 18:11:18, 179.9 GB (34.58 GB, 19.22% new) 121MB 57% CPU READ-ONLY EBSDEV_4hmepnkh_1_1
2011-06-13 18:26:17 avtar Info <5100>: Status 2011-06-13 18:26:17, 193.6 GB (36.43 GB, 18.82% new) 292MB 56% CPU READ-ONLY EBSDEV_4fmepnkh_1_1
2011-06-13 18:26:17 avtar Info <5100>: Status 2011-06-13 18:26:17, 196.1 GB (37.61 GB, 19.17% new) 121MB 56% CPU READ-ONLY EBSDEV_4hmepnkh_1_1
2011-06-13 18:26:18 avtar Info <5100>: Status 2011-06-13 18:26:18, 187.3 GB (37.59 GB, 20.07% new) 121MB 50% CPU READ-ONLY EBSDEV_4gmepnkh_1_1
Why is there READ-ONLY status in the avtar.log?
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
June 14th, 2011 08:00
This means the avamar server went readonly during the backup.
This was introduced in the later versions of Avamar 5.x
makwetu
3 Posts
0
June 14th, 2011 09:00
Tks for the reply
You right, the server started a checkpoint that took around 2 minutes and completed. Unfortunately the avtar.log does not update after the checkpoint completion. No impact though.