yes, i have done the math as well and came to roughly the same conclusion so that makes me feel good. i scheduled the job to run as soon as they leave for the day, so literally like 5:15PM that job starts. funny thing, it has not hung since last week. the last successful notification i have 5/5/19... a good image and a successful purge from the media.. total file size for the image was 73 gigs.
maybe i should open a ticket with them and close if issue is moot by the time they get around to me? idk, but i would hate to say this is resolved and then i get to try for a successful job and get a hang again..

C drive is 80 gigs, the shared drive is 840 gigs.

this org is on an 100/100 circuit, gets about 75/75 during production hours, gets better after 5PM.

synthetic full is enabled, compression is enabled, no encryption or snowball enabled.

im going to update this again after the next backup job runs, but the last job actually did finish.. it ran from when i made the post till last night, so 7 days total and it finally finished.

i will see if this is going to continue to finish and update accordingly. still think that 7 days is far too long to wait for a full backup.

yeah, it wasnt ideal, but i wanted to let CBB do its thing. it has always finished in the past so i thought more time might help. i have a couple backup solutions in place since the failure (not failure, just lack of completion i suppose) started happening...

i have added the link to the page as requested. i have also updated the instance, it had been running the previous build.

thanks for the prompt reply!