SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Read-only Data


Read-only Data

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)

Group: Administrators
Points: 61391 Visits: 19097
Comments posted to this topic are about the item Read-only Data

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Revenant
Revenant
SSCertifiable
SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)

Group: General Forum Members
Points: 7266 Visits: 4857
Daily, like all other databases.

With 4 TB 10,500 rpm drives going for about $220, I could back up all databases twice a day.
rf44
rf44
SSC-Enthusiastic
SSC-Enthusiastic (135 reputation)SSC-Enthusiastic (135 reputation)SSC-Enthusiastic (135 reputation)SSC-Enthusiastic (135 reputation)SSC-Enthusiastic (135 reputation)SSC-Enthusiastic (135 reputation)SSC-Enthusiastic (135 reputation)SSC-Enthusiastic (135 reputation)

Group: General Forum Members
Points: 135 Visits: 1093
In the company where I work, the ultimate archive stage consists in exporting the data in a flat model (csv files) that are stored on CDs or DVDs (always in pairs, each member of a pair being stored in a different location).
S Hodkinson
S Hodkinson
Right there with Babe
Right there with Babe (730 reputation)Right there with Babe (730 reputation)Right there with Babe (730 reputation)Right there with Babe (730 reputation)Right there with Babe (730 reputation)Right there with Babe (730 reputation)Right there with Babe (730 reputation)Right there with Babe (730 reputation)

Group: General Forum Members
Points: 730 Visits: 1022
I'm with Revenant. I backed up daily ('belt and braces'). You only have to rebuild a server once to know that you never want to do it ever again.

Madame Artois
scunningham 38251
scunningham 38251
SSC-Enthusiastic
SSC-Enthusiastic (161 reputation)SSC-Enthusiastic (161 reputation)SSC-Enthusiastic (161 reputation)SSC-Enthusiastic (161 reputation)SSC-Enthusiastic (161 reputation)SSC-Enthusiastic (161 reputation)SSC-Enthusiastic (161 reputation)SSC-Enthusiastic (161 reputation)

Group: General Forum Members
Points: 161 Visits: 633
Here's a third vote for 'daily'.

The archive system I came up with requires management approval to move old stuff off so it only actually changes every few months. So really, just backing up after every archive operation would be enough.

But our backups run overnight, there's no load or user interaction to speak of then, and so slowdowns and such don't matter. So, I do do everything all in one shot, every night.

If it ever gets to be a problem I'll reduce frequency but so far nothing bad has come of it.
Mike Palecek
Mike Palecek
SSC Eights!
SSC Eights! (888 reputation)SSC Eights! (888 reputation)SSC Eights! (888 reputation)SSC Eights! (888 reputation)SSC Eights! (888 reputation)SSC Eights! (888 reputation)SSC Eights! (888 reputation)SSC Eights! (888 reputation)

Group: General Forum Members
Points: 888 Visits: 823
Here is another vote for daily.

When we run out of backup space on our dailies I will consider alternatives, but for now the convienece of having a single backup with everything in it is great.
Ira L Grollman
Ira L Grollman
Grasshopper
Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)

Group: General Forum Members
Points: 14 Visits: 31
I use a disaster recovery plan for each client based on their ability to "know" where the archives are and their permitted recovery time. The issue of knowing where a backup is and its validity is a business process issue. It is one of those holy grail issues that are covered by corporate compliance and verified by the audit team. I recommend an internal replicated SharePoint site for those memory joggers with hardcopy (yes, paper) of critical pointers stored off-site in the organization's bank safe deposit box.

Usually, the required "back on the air time" dictates how "near real time" the archive backups are. In general the archives are read verified, if stored on-site, at a low priority as part of other regulatory compliance processes (SOX, ISO 9000, etc.). If the archive backup is off-site, then a new archive backup is created to the same schedule as the organization's fiscal reporting, usually monthly, or at a minimum annually.

FWIW, the disaster recovery plan (or business continuity if you prefer) is usually required for the organization's Errors and Omission insurance and sometimes its liability insurance.

Regards, Ira
lionfan91
lionfan91
SSCarpal Tunnel
SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)

Group: General Forum Members
Points: 4757 Visits: 429
One of our databases is populated on a monthly basis when we get a DVD from an outside agency. This data is converted from the DVD format and stored in a SIMPLE recovery model database. Once it's written that one time, it's read-only thereafter. So after we import the data, we make a backup, and don't backup until we repeat the cycle the following month.



george sibbald
george sibbald
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10224 Visits: 13687
just to be different, if the data is not changing, I would probably go for weekly. Why waste the resources (including tape) if the data is not changing?

---------------------------------------------------------------------
TravisDBA
TravisDBA
SSCommitted
SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)

Group: General Forum Members
Points: 1946 Visits: 3069
I have worked with read only data, particularly read only databases all the time and my concerns are not so much from the backup side of things, but more from what I can't do once I make that data Read Only. So, you need to make you sure complete these things before you set the database to READ ONLY mode, because once you set it, then:


•Statistics will not be automatically updated (nor required) and you would not be able to update statistics of a READ ONLY database
•READ ONLY databases will not shrink automatically or manually
•You will not be able to create indexes
•You will not be able to defragment indexes of a READ ONLY database
•READ ONLY databases will not allow you to add any extended properties on any of its objects
•Permissions may not be edited and users may not be added or removed from a READ ONLY database.

Backing up read only data is only a small part of a much bigger picture. :-D

"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...:-D"
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search