Backup failing as logs cannot be rotated as the server is too busy.
"We try to rotate our server log files daily and several of our depot instances are super busy and when we try to do the log, it fails with the below error:
rename-item -path shootercommit.log shootercommit.log.44.20190418-220109
rename-item : The process cannot access the file because it is being used by another process.
This is the first step of our backup process and if the log doesn't rotate, the backup doesn't complete. Can you help us understand what we can do to consistently rotate our logs without these errors?
I notified them of open job053474 to have ‘p4 logrotate’ rotate the standard log.
Request: Will this SIR also make it way back into SDP code for windows so that the daily-backup process will take advantage of it?
Is there a workaround that I can implement in the meantime until it gets fixed? Logging into each my of p4 servers every day to rename the logs manually isn't really an option.