Data Locations / Backup/Archive operations
Posted on 2011-03-14
Can anyone with experience of backing up databases let me know what I am after in the below which is about where data for a database driven application “could reside” dependant on setup and business operations/policy.
I basically want to identify every where data for a specific application “goes”. It is sensitive data so I really want control or at least some insight into everywhere this data essentially goes during backup/retention/archive/test procedures. So really I need to understand a typical backup/archive/retention workflow/process for a typical application based on a large database containing sensitive data. If anyone could provide such an example that would help?
Also, what kind of documentation would typically include this data “path/flow”? I.e. everywhere the data held within the database that drives this application does/could the data end up. Is this called a certain type of document by any chance that I could ask for? What infrastructure/architecture in a large application could this data reside on for backup/retention/archive/business continuity reasons. What is the archive/backup/retention workflow stages and where does the data go during these stages?
In my non expert backup mind, the data lives on the hard disc on the database server, i.e. the same server where the MSSQL service is running. But I assume for larger applications the data may well be spread across numerous servers/storage devices.
Any pointers welcome. As simple terminology as possible be greatly appreciated to show a non backup/DBA person the flow/process of where data from a database driven app goes/resides.