Backup and restore

Question

Backup and restore

viswanath09

Mr or Mrs. 500

Points: 512
More actions
May 27, 2010 at 11:12 pm

#233145

Hi
which backup and restore strategy used for the database size above 2TB

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

homebrew01 SSC Guru Points: 55539 More actions · Answer 1

I have a 1.2 T database. We use BackupExec straight to tape because we don't have space to hold a native backup on disk. We tried using Redgate, but it would run for 24 hours without completing (tried various compression settings), although Redgate works fine on our smaller databases ( 200 G). I will try again with the latest version when we get more disk.

Steve Jones - SSC Editor SSC Guru Points: 734449 More actions · Answer 2

A few link:

http://sqlcat.com/whitepapers/archive/2009/08/13/a-technical-case-study-fast-and-reliable-backup-and-restore-of-a-vldb-over-the-network.aspx

What version of RG? A TB database isn't that big these days with TB drives.

homebrew01 SSC Guru Points: 55539 More actions · Answer 3

We're on RG 6.0 now, so I think it was 5.0 at the time (about a year ago). I couldn't determine if it was related to the large amount of image data in one table (almost 1 Tb) or the fact that backups were going to a Buffalo attached drive. I couldn't spend any more time troubleshooting and needed a solution, and since Backupexec worked, that's what we're using just for that database.

Steve Jones - SSC Editor SSC Guru Points: 734449 More actions · Answer 4

Interesting. I'd be curious if 6 worked better. If I remember, 5 was a big change, but if you want someone to help you dig through the issue, I can arrange it.

homebrew01 SSC Guru Points: 55539 More actions · Answer 5

Thanks, I might revisit when I get more space.

As to the OP, my strategy isn't any different for a big db than it is for a small one. Make sure my backups work and that I can recover to whatever point in time my business requires. Use a combination of Full and T-log backups (no room for a DIFF).