Hi all,
Somebody can help me to find information about LOGASIO? (Controls transaction logging); i don’t know how works, i think that it’s running cause we are using DECS, but i see many files like this:
.temp, accessxxx.log, agentxxx.log, cgi_errorxxx.log, idxxx.dtf, lptvpn.xxx, referxxx.log
Can i delete them? or if is it possible disable Controls transaction logging.
Thanks in advanced!
Subject: Where can i find information about it?
Actually those files you listed are pure Web Server logs (except the .temp), and have nothing to do with Transactional Logging (which is like a different approach to keep database documents and indexes maintained, usually slower than normal databases anyway, so it’s kinda pointless).
Subject: Transaction logging is far from pointless
Transaction logging
can, with the proper backup s/w, make backup tapes behave like they’re continuously up-to-date, for perfect restores.
reduces the likelihood of data corruption.
makes databases available more quickly after server crashes (by replacing consistency checks).
fixes most database corruptions resulting from server crashes, reducing the need for running fixup.
can be set to automatically invoke fixup on databases it can’t repair on reboot.
can be implemented so as to improve disk I/O by O(10 %).
I’d characterise a tool like that as being closer to a godsend than pointless, but your opinion may vary.
Subject: RE: Transaction logging is far from pointless
We could have used this on our server just this week - some pretty strange design corruption ended up causing one our users to delete a whole bunch of documents in a heavily used database. The backup wasn’t really an option since it was 2 days old and we’d had too many edits since then. Our sysadmin thinks transaction logs might have saved me the day of writing scripts to custom-restore the missing documents back to the live db.
It’s definitely not for everyone, but don’t discount it if data safety is paramount.
Subject: RE: Transaction logging is far from pointless
Transactional logging is indeed good for servers which crash nonstop, so they can rebuild the indexes faster, and restore databases from backup much quicker.
But for pure document create/update/delete performance, it’s faster without Transactional Logging. I tried to make an agent which created and deleted 300000 documents, and the agent ran much faster when TL was disabled. Restoring databases from backup wouldn’t work for me either, because I replicate all databases accross different servers in less than 15 min interval, so the most up-to-date data would be found in a replica of the database and not on a backup tape.
Subject: RE: Transaction logging is far from pointless
“Transactional logging is indeed good for servers which crash nonstop, so they can rebuild the indexes faster, and restore databases from backup much quicker.”
I don’t understand. The (new to R6) View Logging feature could, I suppose, be described as allowing servers to rebuild indexes faster – but not only is it not the essense of TL, but for all but the most inefficiently-designed views, I think it would take longer to restore the index from TL backup than to rebuild the index normally. So I doubt that you were referring to that, and so I’m not sure what you meant by that statement.
I have no problem believing that an agent which creates/deletes 300k documents in one run would bog down TL, but that hardly describes routine database activity. Citing that extreme, non-representative scenario as a reason to not use TL isn’t realistic. (And besides, disabling TL for that one db, running the agent, re-enabling TL, and then backing up the db would be a perfect way to accommodate TL and the agent, especially if such an agent ran regularly.)
“so the most up-to-date data would be found in a replica of the database and not on a backup tape.”
Er, you are presenting a perfect case for what TL is designed to do – acting like a continuous/instantaneous backup – as a case for not using it. That’s the whole point; that your backup software can restore edits not yet on any tape, and not yet replicated to another server.
Subject: RE: Transaction logging is far from pointless
Thanks for your answers, if i have backup software online, i don’t need transactional logging don’t u think?
Subject: Again, the whole point of TL is that it gives supporting backup software the ability to restore edits that haven’t been backed up yet, so yes, you still need it.
Subject: RE: Transaction logging is far from pointless
If I had transaction logging on a database nsf (mail) that for any reason is now corrupted, can I restore it from an old full backup made by TSM (tivoli product) and obtaining a ‘corrected’ and up-to-date database by means of Transaction logging?Thanks.