Below that key, there is each SourceOne component. Expand the SourceOne component, and click on Settings, under TraceVerbosity, you can change it from 0 (minimal logging) to 4 (verbose).
If you want to disable logging all together for the SourceOne component, go to this section:
Wouldn't that be more for troubleshooting? Depending on what level of detail you need to troubleshoot an issue? In my environment, I do not have logging turned on for journaling but I do have it turned on for our archive and shortcutting activities that run weekling. These logs are more or less used for troubleshooting and seeing what mailboxes/messages got archived/shortcutted. If you do not need the logs, my guess is you will need to go in there can clean up. I do not see any other reason to keep the logs around.
Yes, the trace verbosity is more for troubleshooting. But you can disable the log files altogether by disabling the listeners for each SourceOne component.
If you want to disable logging all together for the SourceOne component, go to this section:
If I am not wrong I believe bndunlap was reffering to Exchange logs as opposed to SourceOne logs. He might have seen a big jump in them all of sudden because most of the exchange admins has tools monitoring the threands of the exchange logs. Huge jump is also going to increase the time for that night's backup job because logs would have changed due to all the changes to the messages in users mailboxes on exchange DBs.
If that is the case then it might be expected change because now messages in users mailboxes would have changed due to very large jobs that would have run. This might be once a time change on because once messages are shortcutted those are not going to be restored back to exchange unless someone runs restore jobs from SourceOne. Retrieval of shortcuts through SourceOne offline Access do not cause messages to restore back to Exchange server as it was the case with EmailXtender shortcut addins. Next time a workaround could be to archive and shortcut mailboxes in smaller chunks that way you can control the growth.
Now coming to query from emc4me4life , I believe you were reffering to Job logs instead of verbisity logs that Brad was reggering to. It is usually a good idea to enable the job logs to see how you job went. This logging is on the logs share that was provided on the time of installing the product.
What Brad was reffring to is something that is needed on the time of troubleshooting an issue, we need to keep in mind that having verbosity of a component set to 4 or above has its own implication on the performance. I would suggest keeping that turned off in normal operations and only turn it on when support will suggest or when you want to dig deep into some issue.
Thanks Rajan, you are right on what I was referring to. And, when the backup is slow or even fails then transaction logs continue to grow and add to the problem over all. I think as you referred to, this was not the norm, I think our archive job last month was much larger than usual and all these things led to Exchange transaction logs filling up the drive and dismounting the dbs. Mostly, my users archive email by copying or moving items to a container folder but i do have an archive job, then a shortcut job that runs once a month. Maybe I should do this 2 times a month to prevent this big hit in the future.
IT_Warlock
48 Posts
0
November 30th, 2011 11:00
Hello Bndunlap,
SourceOne has a section of the registry dedicated to trace logs.
You can increase/decrease the trace log verbosity in this section:
HKEY_LOCAL_MACHINE\SOFTWARE\EMC\SourceOne\TraceLogs
Below that key, there is each SourceOne component. Expand the SourceOne component, and click on Settings, under TraceVerbosity, you can change it from 0 (minimal logging) to 4 (verbose).
If you want to disable logging all together for the SourceOne component, go to this section:
HKEY_LOCAL_MACHINE\SOFTWARE\EMC\SourceOne\TraceLogs\"SourceOne Component"\Settings\Listeners\File
Enabled = 1 (default), if you change it to = 0 it will be disabled. You may need to restart the SourceOne services, if changes do not take affect.
Cheers,
Brad
emc4me4life
6 Posts
0
December 8th, 2011 11:00
Brad,
Wouldn't that be more for troubleshooting? Depending on what level of detail you need to troubleshoot an issue? In my environment, I do not have logging turned on for journaling but I do have it turned on for our archive and shortcutting activities that run weekling. These logs are more or less used for troubleshooting and seeing what mailboxes/messages got archived/shortcutted. If you do not need the logs, my guess is you will need to go in there can clean up. I do not see any other reason to keep the logs around.
IT_Warlock
48 Posts
0
December 8th, 2011 13:00
Hello emc4me4life,
Yes, the trace verbosity is more for troubleshooting. But you can disable the log files altogether by disabling the listeners for each SourceOne component.
If you want to disable logging all together for the SourceOne component, go to this section:
HKEY_LOCAL_MACHINE\SOFTWARE\EMC\SourceOne\TraceLogs\"SourceOne Component"\Settings\Listeners\File
Enabled = 1 (default), if you change it to = 0 it will be disabled. You may need to restart the SourceOne services, if changes do not take affect.
It also helps the performance of the SourceOne server, to keep the logging level to a minimum when there are no issues present.
Cheers,
Brad
RKatwal
2 Intern
•
600 Posts
1
December 8th, 2011 15:00
Greetings,
If I am not wrong I believe bndunlap was reffering to Exchange logs as opposed to SourceOne logs. He might have seen a big jump in them all of sudden because most of the exchange admins has tools monitoring the threands of the exchange logs. Huge jump is also going to increase the time for that night's backup job because logs would have changed due to all the changes to the messages in users mailboxes on exchange DBs.
If that is the case then it might be expected change because now messages in users mailboxes would have changed due to very large jobs that would have run. This might be once a time change on because once messages are shortcutted those are not going to be restored back to exchange unless someone runs restore jobs from SourceOne. Retrieval of shortcuts through SourceOne offline Access do not cause messages to restore back to Exchange server as it was the case with EmailXtender shortcut addins. Next time a workaround could be to archive and shortcut mailboxes in smaller chunks that way you can control the growth.
Now coming to query from emc4me4life , I believe you were reffering to Job logs instead of verbisity logs that Brad was reggering to. It is usually a good idea to enable the job logs to see how you job went. This logging is on the logs share that was provided on the time of installing the product.
What Brad was reffring to is something that is needed on the time of troubleshooting an issue, we need to keep in mind that having verbosity of a component set to 4 or above has its own implication on the performance. I would suggest keeping that turned off in normal operations and only turn it on when support will suggest or when you want to dig deep into some issue.
I hope this helps.
Regards,
Rajan
bndunlap
1 Rookie
•
7 Posts
0
December 9th, 2011 05:00
Thanks Rajan, you are right on what I was referring to. And, when the backup is slow or even fails then transaction logs continue to grow and add to the problem over all. I think as you referred to, this was not the norm, I think our archive job last month was much larger than usual and all these things led to Exchange transaction logs filling up the drive and dismounting the dbs. Mostly, my users archive email by copying or moving items to a container folder but i do have an archive job, then a shortcut job that runs once a month. Maybe I should do this 2 times a month to prevent this big hit in the future.
Thanks