npdodge
asked on
deleting transactions logs generated from public folder migration
Currently in the process of a public folder migration from 2007 to 2013. We have over 74,000 folders and about 8 million emails stored in our PF. So far about 2 million items have been copied over but I've generated a lot of transaction logs that will fill up my disk soon. Can I delete these transaction logs for the 2013 server? Or should I be backing up the 2013 database that contains the public folder mailboxes (no user mailboxes in the database with the pf mailboxes) during the migration? I'm sure this would get rid of the log files too. I'm still backing up the 2007 public folder database since it's still in production during this migration, which is why I'm wondering if I can just manually delete the log files for the database containing the 2013 pf mailboxes. Again, there are no other mailboxes in the 2013 database other than pf mailboxes.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Please Enable Circular Logging till the migration complete (Enabling circular logging will not generate any logs).
In your situation best possible ways are discussed below.
1. Go for Online backup: - You can go for either full or incremental backup. Doing any of this will help you to manage the backup and provide you with extra disk space. But this solution come with its known pros and cons.
Pros: - The main pros which comes with this method is that your backup is maintained and disk space is free. And later due to any problem if your machine crashed, your backup will be saved from loss.
Cons: - The method comes along with many cons; For example: This process is time consuming and also if the files (log) is not trimmed at right time as before the machine leads to run out of disk space, may be your storage dismount.
2. Circular logging: - Starting or enabling this option will snip your log data which will still mounted on your disk space.
Pros: - This solution or method is very less time consuming.
Cons: - The con related to this situation is the aptitude of system restoration will not be abled after this feature.
There is one more solution of deleting the log files manually, but for this thing you have to analyze the file. It should not contain any data used by any stores (uncommitted data). Now the question might arise in your mind as how would you locate such data. So for that two methods can be followed.
1. See For checkpoint file:- Check point files are the option which will show you that till what edge the data is committed. You can have this information by using ESEUTIL tool. The command used is “eseutil/mk<path location of your check point file>”.
2. You Can Also Go For database File:- For this method also eseutil tool is used but the command used will changed .There is a slight change only, you have to give the path of your database file to extract this information. The state and log required are the options we want to access.
I hope the answer is useful and please feel free to ask.
Thanks & Regards