Oracle Analytics Cloud and Server

Products Banner

How to restore datasets/projects deleted from OAC?

Received Response
317
Views
16
Comments

Summary

How to restore datasets/projects deleted from OAC?

Content

Some of the datasets/projects that were rarely used were deleted from 'Dataset Management'->Storage->Delete All

Apparently, this needs to be restored back now, as it is required for some reasons.

Is there a way to restore back these deleted datasets/projects in OAC, as a Service Administrator?

Please let me know.

 

Thanks,

Chethana

Answers

  • Hello Chethana,

    You can restore your instance snapshot (Console -> Snapshots) which was created before this deletion, you will get all your content back (the instance will be the same as when the snapshot was taken).

    Hope this helps!

    Best Regards,

    Aman Jain

  • Thanks Aman. Unfortunately, I have'nt taken any snapshot of the instance before deleting the datasets and projects.

    This means I would not be able to restore, right?

    Regards,

    Chethana

  • Exactly. No backups mean that it's all gone.

    Be mindful that "cloud" doesn't mean you don't have to think about the usual management tasks like backups, snapshots etc.

  • Hi,

    Indeed we have to manage backups to be safe, but what is also needed is to restore one dataset and not the entire snapshot ...

    Moreover that functionnality is also relevant to promote a dataset from DEV to PRD.

    Does anyone have a solution for that need please ?

    Jean-Pierre

  • Michal Zima
    Michal Zima ✭✭✭✭✭

    @Jean-Pierre Hoedenaeken The only possibility (not very handy) is to backup individual data sets via DVA package (export of DV workbook) - this is meant for backup of DV workbook, but this backup (DVA binary file) - contains also all data sets, used by this DV workbook - their definitions, for file-based data sets also the files itself, for DB data sets also definitions of corresponding connections. So you can use this (as a kind of workaround) to backup data sets (you just need to create some "dummy" DV workbook, include corresponding data sets and then export to DVA package) - quite clumsy.....

    This "functionality" should be (my opinion) part (meaning export/backup of individual data sets, including also content of file-based data sets) of long-promised Rest API for DV (or OAC/OAS whatever it will be called), which is still just "on the roadmap" , but no specific information about availability of this API yet.. We are calling (we are OAS customer) for it for long time - hopefully this will become reality soon (at least in OAC) and will provide rich functionality for all governance tasks (usually automated or semi-automated).

  • Thanks Michal,

    I suppose that furthermore we have to create the datasource connection under the exact same name ?

    Jean-Pierre

  • Michal Zima
    Michal Zima ✭✭✭✭✭

    Do you mean on "target" environment, where you are about to import/restore DVA package ? If this is what you mean by your question, than no - import of DVA package also "restores" the definition of corresponding connection (used by data sets in DVA package).

  • Indeed, both the connection definition and the dataset is imported inthe target environment.

    So this workarround does the job.

    Thanks again Michal.

  • I see that the "Export" functionnality is also available on a "Folder" ...

    Does that mean that all the content of the folder could be exported and the imported in the target environment, even "Classics" artifacts like Dashboards, Prompts, Requests, Agents, .... ?

  • The "Export" seems to be a hybrid between DV export and catalog archive. If you do export from Catalog in DV you get a file containing a catalog archive (the same good old archive that exist for more than 10 years) for everything that is just part of the catalog (folders, DV workbooks, analysis, dashboards, agents etc.) and the DV pieces like datasets, connections etc.

    The catalog archive is really just that, you can even import it with Catalog Manager (the client) or in Catalog Manager in "classic" Answers if you want.

  • Indeed importing in the target environment the dva file of a folder brings both the DV pieces and the classic artifacts.

    The last trouble is that the folder is restored in "My folder" instead of "Shared folders".

    I could move it but then the path to the artifacts in the dashboard page are wrong and I have to replace them from the new shared folders path.

    Do we have a trick to avoid that the folder is restored in "My folder" ?

  • Michal Zima
    Michal Zima ✭✭✭✭✭

    @Jean-Pierre Hoedenaeken I guess you need to be "located", when making import, (in BI catalog structure) in folder, where you want to import this DVA archive (containing whole folder) and it should work.

    Just to maje it clear: DVA package/archive created from BI catalog folder contains only those DV objects (data sets, connections),which are related to workbook, located in this folder (DV objects, except workbooks, are not stored in BI catalog folder structure).

  • I would agree with what Michal said: the catalog archive does not contain any information about absolute paths, you can restore it where you want but you need to execute the import where you want it. I highly doubt they did change the behavior of that 10+ years old piece of logic just for this (even if the DVA does contain a text file with the absolute path of what has been exported, but this can't be understood from the unarchive logic and it would even be wrong to force you to restore an export only in the same exact absolute path it does come from).

    A DVA export from the catalog is really a weird file because it mix things that are from different sources (as Michal said only workbooks are in the catalog, all other DV objects are in the database directly and don't have a catalog presence) and work in different way.

    Personally I find it a really poorly defined feature working heavily as a black box. It sounds more as something developed to tick something off a list than with real lifecycle management in mind. The same lifecycle management that has badly missing features in DV, like that famous API that still doesn't exist and other elements that are not fully developed. (Do you want to work offline on a OAS or OAC catalog? Officially you can't, practically you can but they will not like how you do it and will fallback to a "but you don't really need this feature" kind of reply, or just no reply at all to emails ?).

  • Michal Zima
    Michal Zima ✭✭✭✭✭

    There is no choice but to agree with everything, what Gianni summarized in previous entry - data governance/administration of DV objects is still very limited/clumsy and it is one of the biggest weakness of DV (as part of OAC/OAS suite) as such (although product as such is developing quite heavily and many improvements are really very good) . Hopefully our laments will be heard by responsible people from Product Management/Development.

  • I've done some further testing and could manage the following use case : promoting from one environment to another a shared folder that contains visualizations and classic artifacts, with the Dataset(s) and the Connection(s) used by the visualizations.

    The process that fully works is :

    • archive the folder located in "Shared Folders" from the source environment;
    • unarchive it in "Shared Folders" in the destination environment;
    • export the visualization(s) (options : Data and Connection Credentials) in a DVA file;
    • import the DVA file in the folder archived & unarchived in first and second step.

    Thanks for your help Michal ang Gianni and feel free to share the info on your blog if you want.

    Regards.

    Jean-Pierre

  • Well, keeping Snapshot backups become easier than ever. You can use the Rest API to do the Job automatically.

    Snapshot APIs