July 29, 2003 at 6:49 am
The database in question is composed of aerial photos, so it is not going to grow or change. The database size is about 62GB. I would like to create a backup plan for it.
What type of backup should I use, recovery model,etc..
How much space I would need for backing it up? I currently use my E drive on the same server for backups is that safe? Oh my E drive only has about 11GB of free space.
Any advice is greatly appreciated.
July 29, 2003 at 6:58 am
Hi els,
quote:
The database in question is composed of aerial photos, so it is not going to grow or change. The database size is about 62GB. I would like to create a backup plan for it.
I'm no backup specialist. But why do you want to create a backup plan for a db that does not change?
Wouldn't a single backup, once it is in production be enough?
quote:
How much space I would need for backing it up? I currently use my E drive on the same server for backups is that safe? Oh my E drive only has about 11GB of free space.
If you do not use any compression tool like the one in the ad above, the db will have the same size as the original.
And, well, if your E: drive is a separate it's even better than using the same harddisk. But what when your server gets flooded, like happened to me a year ago ? You should keep at least one copy or backup on a separate medium like tape or something.
HTH
Cheers,
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
July 29, 2003 at 7:13 am
Your E drive only has 11 GB of free space? Well, you aren't going to be able to backup a 62 GB database to that drive.
Since this database isn't going to grow or change, I suggest detaching the database and copying the .mdf and .ldf files to another location or tape. (Then reattach the database).
Why? Having the actual .mdf and .ldf file lets you restore the database quicker. All you need to do is move the files back to their original location and attach them.
I suggest having at least one copy on tape or removable hard drive and storing it in a secure location (or having a procedure that in case of fire, etc, someone grab that tape/hard drive and take it with them).
You really don't need a backup plan, since it only needs backed up one time. I would also change the database recovery mode to SIMPLE.
-SQLBill
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply