There is a blcli command for this – delete cleanupAgent.
Yes, understood. But my question is, do we really need those folders or are they strictly just for logging purposes? Thanks, Bill.
They are there for rollback and the logs.
What if blcli command does not do the job? Can I clean up the folder manually? Like if there is over 1GB stuff and if the target server is behind of slow connections? blcli command just stops and do nothing.
1 of 1 people found this helpful
Yes, you can clean up the folder manually. I recently had a ticket with similar question, so pasting here the answer I gave the other user (slightly formatted):
The large Transactions fodler is due to Windows patching deploy jobs leaving the files behind in the directory for rollback.
There are two options to minimize this impact:
1. In your Deploy Job options uncheck "Allow rollback - Leave rollback files on target for later use".
This way you will not be able to perform rollback, though I have a feeling that the patch deploy jobs are not rolled back too often.
2. If you maintain some sort of cleanup procedure, you could add one more task to clean up agents:
blcli_execute Delete cleanupAgent $ServerName $RetentionTime
This command will clean up from staging and transactions directories everything older than <RetentionTime>. BLCLI Help has more information.
3. (added for DarkMan) If blcli does not work, then Yes - you can delete the entire folder manually
I think we have issue open on this so I have to wait until your boys can check out the logs and stuff. But if nothing else help, we now know that it can de done manually too.
Also there is this Trace.txt file on every windows servers holding more than a couple of hundred MB's in C drive.
Can we delete that too as a part of Agent cleanup task?
Is there any known issue with patching post deleting the Trace.txt?
The trace.txt file is only needed for troubleshooting purposes so can safely be deleted.
I'm not sure why yours is so large though - a typical trace.txt file is only a few MB
Trace.txt fiel was never deleted over this 3 years, in the environment. May be thats the reason it is so huge..
I'm guessing you are using an older version of BSA - in current versions the fie is overwritten, not appended.
I am using BL8.2 SP4.
So am I understanding correctly that the Transactions directory itself, as well as the contents, can be deleted?
The reason I ask is because we will exclude the entire directory from our server backups if it won't affect a bare metal restore. In other words, if there's nothing there that the RSCD Client needs to function, it won't affect a bare metal restore to exclude the whole thing.
The transactions directory stores logs from deploy jobs (logs) (typically more detailed than what shows in the gui) as well as rollback/undo information for deploy jobs. there are some other sub dirs. in there that keep other information like what blpackages have been deployed to the system (Database). so generally – yes, you don’t need to keep the contents of that directory (for long). some of the dirs. in there are used during deploy like ‘events’, ‘locks’ so those should not be deleted.