Clarification on Sessions
Posted: Tue Apr 19, 2005 1:29 pm
Hi,
I'd just like to clarify my understanding of Sessions. For example...
Assume I execute a given Job (A) for what becomes Session 10 i.e I started with full back up and this is my 9th incremental backup; then after the Job has finished, I delete Sessions 1 to 9. If I now restore A, would my database be restored to the same state that it was prior to running Session 10? Will the backup contain ALL my data e.g. as it would have done had I performed the Job as a full backup? I appreciate there would be a physical difference, but I'm talking "logically" here of course.
Essentially, I'm seeking to understand exactly what I may safely delete, assuming that I only want to cater for disasters and be able to recover back to the state my database was in immediately before the last back up. For this exercise assume I don't need access to the prior state of any data i.e files pre-the latest changes or data that was deleted.
In a similar vein, as you've probably addressed this before, can you point me to further information on "pruning" (I have read the manual/help), but I'm still not clear. Again, following on from the above, assume I DO want to hang on to some old versions of just some files, I want to get clear exactly how do I do that?
A brief document on backup scenarios/strategies would be really handy. I really like AIS and except for a few queries, got the hang of it pretty quickly. I appreciate that backup strategies are a big topic, but I'm thinking here of making better use of the way AIS works, specifically working with incremental backups. With a few examples, Users could easily mix and match methods to suit their needs.
Thanks
Patrick
I'd just like to clarify my understanding of Sessions. For example...
Assume I execute a given Job (A) for what becomes Session 10 i.e I started with full back up and this is my 9th incremental backup; then after the Job has finished, I delete Sessions 1 to 9. If I now restore A, would my database be restored to the same state that it was prior to running Session 10? Will the backup contain ALL my data e.g. as it would have done had I performed the Job as a full backup? I appreciate there would be a physical difference, but I'm talking "logically" here of course.
Essentially, I'm seeking to understand exactly what I may safely delete, assuming that I only want to cater for disasters and be able to recover back to the state my database was in immediately before the last back up. For this exercise assume I don't need access to the prior state of any data i.e files pre-the latest changes or data that was deleted.
In a similar vein, as you've probably addressed this before, can you point me to further information on "pruning" (I have read the manual/help), but I'm still not clear. Again, following on from the above, assume I DO want to hang on to some old versions of just some files, I want to get clear exactly how do I do that?
A brief document on backup scenarios/strategies would be really handy. I really like AIS and except for a few queries, got the hang of it pretty quickly. I appreciate that backup strategies are a big topic, but I'm thinking here of making better use of the way AIS works, specifically working with incremental backups. With a few examples, Users could easily mix and match methods to suit their needs.
Thanks
Patrick