Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
lotd90518dCompressing the dbs into gzip tar balls, if not already might yield a tiny bit space.
You can't fix it without giving him free upgrade or deleting stuff
Oh hey my every day life!
buy a wd essential harddsisk for $90 move the old backups on to it. Delete it on the server. Store the disk next to the server.
Root305358dYou are a professional in your field.
They are not.
Clearly they're not aware of this.
Perhaps a reminder is in order?
Maybe you need to say to your client with analogy, like a nuts in the basket that over of capacity.. 😏
Even if this not work, you can fade your client down in the deeeep blue sea.... 😄😂😂😂
Remove those 1+ year old database backups, silently.
Than say. Tadaaaaaa. Now you having enough space for several months.
Trust me. I'm an expert!
The invoice position shall be labeled
"Retrieved diskspace from magic land of wonders"
Unmount that partition.
C: What did you do?
C: What. Did. You. DO?
You: fixed it.
If on Linux, delete the originals, Symlink them to the offsite backup (using SSHfs if possible to mount the remote system).
Of course, assuming that the server can see the backup and the user had rw on it.
Lmao, you guys are giving me the best entertainment possible for this situation. Truth be told, I've imagined most of these things, so that tells me I'm on the same page atleast 😉
Dump - - > make tar ball and send to s3 (as a backup of the backup) - - > truncate *walks away whistling because technically the DB's are still there, just empty*
mk3d24852d“Just fix it” = Do what you want :p
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job