Re: SV: Problem with Journaling
Hi Thanks for that, some product this TSM. I have an issue with journaling on our file server. Last Tuesday the file server backup started to take 16 hours to run. We have journaling setup on the server to prevent this. On investigation the server seems to be inspecting 1.2 million files and only backing up 5 to 6 thousand which would indicate some problem with journaling on one of the drives. How do I find what caused the journaling to end. 11/12/2009 15:52:46 ANE4952I (Session: 197714, Node: DSPRWC) Total number of objects inspected: 1,202,293 (SESSION: 197714) 11/12/2009 15:52:46 ANE4954I (Session: 197714, Node: DSPRWC) Total number of objects backed up:6,626 (SESSION: 197714) 11/12/2009 15:52:46 ANE4958I (Session: 197714, Node: DSPRWC) Total number of objects updated: 0 (SESSION: 197714) 11/12/2009 15:52:46 ANE4960I (Session: 197714, Node: DSPRWC) Total number of objects rebound: 0 (SESSION: 197714) 11/12/2009 15:52:46 ANE4957I (Session: 197714, Node: DSPRWC) Total number of objects deleted: 0 (SESSION: 197714) 11/12/2009 15:52:46 ANE4970I (Session: 197714, Node: DSPRWC) Total number of objects expired: 2,785 (SESSION: 197714) 11/12/2009 15:52:46 ANE4959I (Session: 197714, Node: DSPRWC) Total number of objects failed: 4 (SESSION: 197714) 11/12/2009 15:52:46 ANE4965I (Session: 197714, Node: DSPRWC) Total number of subfile objects: 0 (SESSION: 197714) more... (ENTER to continue, 'C' to cancel) 11/12/2009 15:52:46 ANE4961I (Session: 197714, Node: DSPRWC) Total number of bytes transferred: 25.34 GB (SESSION: 197714) 11/12/2009 15:52:46 ANE4963I (Session: 197714, Node: DSPRWC) Data transfer time: 617.46 sec (SESSION: 197714) 11/12/2009 15:52:46 ANE4966I (Session: 197714, Node: DSPRWC) Network data transfer rate:43,048.54 KB/sec (SESSION: 197714) 11/12/2009 15:52:46 ANE4967I (Session: 197714, Node: DSPRWC) Aggregate data transfer rate:372.28 KB/sec (SESSION: 197714) 11/12/2009 15:52:46 ANE4968I (Session: 197714, Node: DSPRWC) Objects compressed by:0% (SESSION: 197714) 11/12/2009 15:52:46 ANE4969I (Session: 197714, Node: DSPRWC) Subfile objects reduced by: 0% (SESSION: 197714) 11/12/2009 15:52:46 ANE4964I (Session: 197714, Node: DSPRWC) Elapsed processing time:19:49:59 (SESSION: 197714) Jimmy Furlong
Re: SV: Problem with Journaling
Check how long the Journal service has been up or how big the JDB is. We have a server that needs Journaling restarted about every other month, so we restart it on the weekend about once a month. I am guessing you know that journaling is not active until a backup completes after a restart. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Jimmy Furlong Sent: Friday, November 13, 2009 9:50 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] SV: Problem with Journaling Hi Thanks for that, some product this TSM. I have an issue with journaling on our file server. Last Tuesday the file server backup started to take 16 hours to run. We have journaling setup on the server to prevent this. On investigation the server seems to be inspecting 1.2 million files and only backing up 5 to 6 thousand which would indicate some problem with journaling on one of the drives. How do I find what caused the journaling to end. 11/12/2009 15:52:46 ANE4952I (Session: 197714, Node: DSPRWC) Total number of objects inspected: 1,202,293 (SESSION: 197714) 11/12/2009 15:52:46 ANE4954I (Session: 197714, Node: DSPRWC) Total number of objects backed up:6,626 (SESSION: 197714) 11/12/2009 15:52:46 ANE4958I (Session: 197714, Node: DSPRWC) Total number of objects updated: 0 (SESSION: 197714) 11/12/2009 15:52:46 ANE4960I (Session: 197714, Node: DSPRWC) Total number of objects rebound: 0 (SESSION: 197714) 11/12/2009 15:52:46 ANE4957I (Session: 197714, Node: DSPRWC) Total number of objects deleted: 0 (SESSION: 197714) 11/12/2009 15:52:46 ANE4970I (Session: 197714, Node: DSPRWC) Total number of objects expired: 2,785 (SESSION: 197714) 11/12/2009 15:52:46 ANE4959I (Session: 197714, Node: DSPRWC) Total number of objects failed: 4 (SESSION: 197714) 11/12/2009 15:52:46 ANE4965I (Session: 197714, Node: DSPRWC) Total number of subfile objects: 0 (SESSION: 197714) more... (ENTER to continue, 'C' to cancel) 11/12/2009 15:52:46 ANE4961I (Session: 197714, Node: DSPRWC) Total number of bytes transferred: 25.34 GB (SESSION: 197714) 11/12/2009 15:52:46 ANE4963I (Session: 197714, Node: DSPRWC) Data transfer time: 617.46 sec (SESSION: 197714) 11/12/2009 15:52:46 ANE4966I (Session: 197714, Node: DSPRWC) Network data transfer rate:43,048.54 KB/sec (SESSION: 197714) 11/12/2009 15:52:46 ANE4967I (Session: 197714, Node: DSPRWC) Aggregate data transfer rate:372.28 KB/sec (SESSION: 197714) 11/12/2009 15:52:46 ANE4968I (Session: 197714, Node: DSPRWC) Objects compressed by:0% (SESSION: 197714) 11/12/2009 15:52:46 ANE4969I (Session: 197714, Node: DSPRWC) Subfile objects reduced by: 0% (SESSION: 197714) 11/12/2009 15:52:46 ANE4964I (Session: 197714, Node: DSPRWC) Elapsed processing time:19:49:59 (SESSION: 197714) Jimmy Furlong This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: SV: Problem with Journaling
I had this same problem earlier this week. I restarted the journal service and it started journaling again. I'm still looking for the cause. Johnny Huebner,Andy,FORT WORTH,IT andy.hueb...@alconlabs.com 11/13/2009 11:29 AM Check how long the Journal service has been up or how big the JDB is. We have a server that needs Journaling restarted about every other month, so we restart it on the weekend about once a month. I am guessing you know that journaling is not active until a backup completes after a restart. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Jimmy Furlong Sent: Friday, November 13, 2009 9:50 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] SV: Problem with Journaling Hi Thanks for that, some product this TSM. I have an issue with journaling on our file server. Last Tuesday the file server backup started to take 16 hours to run. We have journaling setup on the server to prevent this. On investigation the server seems to be inspecting 1.2 million files and only backing up 5 to 6 thousand which would indicate some problem with journaling on one of the drives. How do I find what caused the journaling to end. 11/12/2009 15:52:46 ANE4952I (Session: 197714, Node: DSPRWC) Total number of objects inspected: 1,202,293 (SESSION: 197714) 11/12/2009 15:52:46 ANE4954I (Session: 197714, Node: DSPRWC) Total number of objects backed up:6,626 (SESSION: 197714) 11/12/2009 15:52:46 ANE4958I (Session: 197714, Node: DSPRWC) Total number of objects updated: 0 (SESSION: 197714) 11/12/2009 15:52:46 ANE4960I (Session: 197714, Node: DSPRWC) Total number of objects rebound: 0 (SESSION: 197714) 11/12/2009 15:52:46 ANE4957I (Session: 197714, Node: DSPRWC) Total number of objects deleted: 0 (SESSION: 197714) 11/12/2009 15:52:46 ANE4970I (Session: 197714, Node: DSPRWC) Total number of objects expired: 2,785 (SESSION: 197714) 11/12/2009 15:52:46 ANE4959I (Session: 197714, Node: DSPRWC) Total number of objects failed: 4 (SESSION: 197714) 11/12/2009 15:52:46 ANE4965I (Session: 197714, Node: DSPRWC) Total number of subfile objects: 0 (SESSION: 197714) more... (ENTER to continue, 'C' to cancel) 11/12/2009 15:52:46 ANE4961I (Session: 197714, Node: DSPRWC) Total number of bytes transferred: 25.34 GB (SESSION: 197714) 11/12/2009 15:52:46 ANE4963I (Session: 197714, Node: DSPRWC) Data transfer time: 617.46 sec (SESSION: 197714) 11/12/2009 15:52:46 ANE4966I (Session: 197714, Node: DSPRWC) Network data transfer rate:43,048.54 KB/sec (SESSION: 197714) 11/12/2009 15:52:46 ANE4967I (Session: 197714, Node: DSPRWC) Aggregate data transfer rate:372.28 KB/sec (SESSION: 197714) 11/12/2009 15:52:46 ANE4968I (Session: 197714, Node: DSPRWC) Objects compressed by:0% (SESSION: 197714) 11/12/2009 15:52:46 ANE4969I (Session: 197714, Node: DSPRWC) Subfile objects reduced by: 0% (SESSION: 197714) 11/12/2009 15:52:46 ANE4964I (Session: 197714, Node: DSPRWC) Elapsed processing time:19:49:59 (SESSION: 197714) Jimmy Furlong This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. Individuals who have received this information in error or are not authorized to receive it must promptly return or dispose of the information and notify the sender. Those individuals are hereby notified that they are strictly prohibited from reviewing, forwarding, printing, copying, distributing or using this information in any way.
Re: SV: Problem with Journaling
If it stopped due to an error, there will be entries in the jbberror.log file in the baclient subdirectory. W On Fri, Nov 13, 2009 at 12:29 PM, Huebner,Andy,FORT WORTH,IT andy.hueb...@alconlabs.com wrote: Check how long the Journal service has been up or how big the JDB is. We have a server that needs Journaling restarted about every other month, so we restart it on the weekend about once a month. I am guessing you know that journaling is not active until a backup completes after a restart. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Jimmy Furlong Sent: Friday, November 13, 2009 9:50 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] SV: Problem with Journaling Hi Thanks for that, some product this TSM. I have an issue with journaling on our file server. Last Tuesday the file server backup started to take 16 hours to run. We have journaling setup on the server to prevent this. On investigation the server seems to be inspecting 1.2 million files and only backing up 5 to 6 thousand which would indicate some problem with journaling on one of the drives. How do I find what caused the journaling to end. 11/12/2009 15:52:46 ANE4952I (Session: 197714, Node: DSPRWC) Total number of objects inspected: 1,202,293 (SESSION: 197714) 11/12/2009 15:52:46 ANE4954I (Session: 197714, Node: DSPRWC) Total number of objects backed up:6,626 (SESSION: 197714) 11/12/2009 15:52:46 ANE4958I (Session: 197714, Node: DSPRWC) Total number of objects updated: 0 (SESSION: 197714) 11/12/2009 15:52:46 ANE4960I (Session: 197714, Node: DSPRWC) Total number of objects rebound: 0 (SESSION: 197714) 11/12/2009 15:52:46 ANE4957I (Session: 197714, Node: DSPRWC) Total number of objects deleted: 0 (SESSION: 197714) 11/12/2009 15:52:46 ANE4970I (Session: 197714, Node: DSPRWC) Total number of objects expired: 2,785 (SESSION: 197714) 11/12/2009 15:52:46 ANE4959I (Session: 197714, Node: DSPRWC) Total number of objects failed: 4 (SESSION: 197714) 11/12/2009 15:52:46 ANE4965I (Session: 197714, Node: DSPRWC) Total number of subfile objects: 0 (SESSION: 197714) more... (ENTER to continue, 'C' to cancel) 11/12/2009 15:52:46 ANE4961I (Session: 197714, Node: DSPRWC) Total number of bytes transferred: 25.34 GB (SESSION: 197714) 11/12/2009 15:52:46 ANE4963I (Session: 197714, Node: DSPRWC) Data transfer time: 617.46 sec (SESSION: 197714) 11/12/2009 15:52:46 ANE4966I (Session: 197714, Node: DSPRWC) Network data transfer rate:43,048.54 KB/sec (SESSION: 197714) 11/12/2009 15:52:46 ANE4967I (Session: 197714, Node: DSPRWC) Aggregate data transfer rate:372.28 KB/sec (SESSION: 197714) 11/12/2009 15:52:46 ANE4968I (Session: 197714, Node: DSPRWC) Objects compressed by:0% (SESSION: 197714) 11/12/2009 15:52:46 ANE4969I (Session: 197714, Node: DSPRWC) Subfile objects reduced by: 0% (SESSION: 197714) 11/12/2009 15:52:46 ANE4964I (Session: 197714, Node: DSPRWC) Elapsed processing time:19:49:59 (SESSION: 197714) Jimmy Furlong This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
