Run this and LET IT FINISH
DBCC CHECKDB(DbName) WITH NO_INFOMSGS, ALL_ERRORMSGS
Did you try to restore that backup on a test server to see if it works and what data it contains?
Any way you can take a backup of the current <corrupt> db?
Any reason (after last time), that you couldn't setup backups on all servers and that you didn't cehck if the backups were usable (we need to know of your current limits)?
the backup is really not a backup, i believe it was created several years ago and when the owner found it's growing too fast then he decided to create another data file and start growing there and reaches 800g now and crashed.
that "backup" is working fine now.
i spoke to the guy who is responsible for it, he said due to the db size too big, no backup have been made in the past but he is considering a bk solution but unfortunately it crashed b4 it is implemented.
due to the fact that moving the damaged db files to another server is not applicable now, i will have to do everything on site.
pls consider a relatively safer suggestion.