- Flexera Community
- FlexNet Manager
- FlexNet Manager Forum
- steps to predict/estimate disk space required for FNMSCompliance Transaction log
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Printer Friendly Page
steps to predict/estimate disk space required for FNMSCompliance Transaction log
Could you please help if there is a possibility from the application end to predict/forecast the transaction log file size for the daily scheduled tasks and what parameters to be considered apart from maintaining sufficient Disk space where the files are stored and need all the inputs in understanding this and the best practices.
This thread has been automatically locked due to inactivity.
To continue the discussion, please start a new thread.
I would consider this too complex to make more than the rough estimation that Flexera gibves in the hardware requirements document:
Remember that logs grow until the next backup is done. This means, you can reduce log sizes by running backups more frequently.
thanks for the inputs and can you clarify if you are referring to the compliance DB backup or the transaction logs backup itself? where you mentioned the more frequent backups decrease the log file size.
@winvarma - You can also reduce the size of the LOG files by updating the Properties of the database. Go to the Options and set the Recovery Mode to "Simple" rather than "Full".
We have already set the recovery mode to simple.
Thanks for the suggestion
For every database there should be a data file and a log file. The log file does log the changes made to your database during normal operation. In case of an issue, the combination of your last backup and the logfile enable you to restore data beyond the beackup alone, sometimes exactly up to the point where the problem occurred.
When a backup of the database is made, the log file content is truncated. The log file will usually keep its last size, until you shrink the files. The log file is then gradually filled as normal operation takes place. If more space is needed, it will even grow larger (depending on file settings). Until the next database backup truncates it again. For example: If you do weekly database backups, the log will have to hold all the changes for a week, if you do daily backups, the log will only have to hold a day of changes.
And regarding Kirk's comment: The change from Full to Simple will only take effect with the next backup. And also: The Simple recovery model may limit your options in case of a restore. Still, best practice is using the Simple model.
thanks for clarifying on the DB backup.