Unsolved
This post is more than 5 years old
29 Posts
0
1895
January 26th, 2015 13:00
Maintenance/Housekeeping
Running 7.1
Are there any maintenance tasks, housekeeping tasks that need/should be performed from time to time to keep Sourceone running smoothly and also to keep the disk space under control?
I am not talking about the archived messages, but the other areas.
There used to be such tasks in the old version of sourceone (or was it emailxtender), but could not find anything in the Administration guide.
Thanks
0 events found
No Events found!
BenCs
1 Rookie
•
114 Posts
1
January 27th, 2015 01:00
Hi Talgentra,
It could be usefull to setup a script that cleans all data older than XX days/months from the job log folder. You can apply the same for EMC SourceOne Logs (logs from the services).
In the Database Folder you can also find SQL Maintenance scripts for ES1Activity, ES1Archive and DiscoveryManager (optional). Make sure SourceOne is in Suspend for Backup state before you execute these scripts.
RKatwal
2 Intern
•
600 Posts
1
January 27th, 2015 15:00
Greetings,
Have you looked at "Maintaining EMC SourceOne" chapter in the SourceOne Admin guide ? That pretty much covers what a usual maintenance tasks should be.
Thanks,
Rajan
201001
29 Posts
0
January 27th, 2015 19:00
Thanks you both. Looks like most the maintenance itself is on the SQL server not on the Sourceone server, except for the 2 logs directories from what I understood.
Regards
RKatwal
2 Intern
•
600 Posts
0
January 27th, 2015 20:00
Yes, that is pretty much what it is.
In regards to job logs and SourceOne component logs following is what I personally like (everyone may have their own opinion)
1. Job logs I prefer to keep it as it is just in case in future there is something I need to investigate, job logs would come handy to see what happened to job that day. Still if they are occupying quite large space and you would need to make up free space that is a different story.
2. SourceOne component’s verbose logging is circular logging, due to which for each component logs cannot be more than 1 GB (10 files of 100 MB each). What you can do is make sure verbose logging levels are returned back to 0 or 1 level once support would have finished working on an issue with you. If you find any logging level left at 4 that you may want to change to 0 in registry keys. It is under HKLM\SOFTWARE\WOW6432node\EMC\SourceOne\TraceLogs\\Settings\
Thanks,
Rajan