Well, it's saying it cannot write this file, so starting there,
C:\\Users\\tbott\\AppData\\Local\\ESRI\\conda\\envs\\arcgispro-py3-clone.tar.bz2
The first thing I would do is make sure there is not already a file there by that name and if there is, delete it. If you can't delete it, try to rename it. Make sure you can write into that folder too (e.g. create a doc and delete it)
The proup tool does a tar backup of an existing env, gets a list of packages installed in it, nukes the existing env and then builds a new one with the same name and adds your packages into it.
I am not comfortable letting Esri's closed source tool nuke environments that I built. It's slow, and I can't see what it's doing (except when it makes a mistake and crashes.) (Too bad they took away the open source version.) (Is there a "prodown" tool to run if the proup tool leaves you with no working env??)
My thought is you can very easily build a new clean environment, test it, and if it works, and you need space, then nuke the old one once you are sure the new one works and you don't need the old one any more.
conda create -c esri -c forge -n pro32 python=3.9 arcpy arcgis
conda activate pro32
Add more tools, for example
conda install geopandas
Of course if there are other packages you installed yourself such as geopandas so you'd need to do that. I keep conda environments with each of the projects I use them with and document what packages I need to add.