Hello,
I try to test oracle restoration for the first time and I would like to know if it's normal to have around 30 min to restore an empty database while it's not more than 5 for SQL.
I create a VM, install oracle 19c , create an empty database, swap to ARCHIVELOG mode, create 1 table and only 1 data test (arround 50 character only).
I create Veeam backup job and enable log backup
I remove the data test
I select the same server as stagging than the one to restore my data
I restore point in time the database.
It works fine, but it's really slow, I just would like to know if it's something expected with oracle or not
Hard to think it's normal because here it's an "empty" database... I don't want to imagine what it could be on several TB
Thanks
-
- Veeam Legend
- Posts: 725
- Liked: 118 times
- Joined: May 11, 2018 8:42 am
- Contact:
-
- Product Manager
- Posts: 8735
- Liked: 2296 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: slow restore oracle
Hello Matteu
Performance issues can not be troubleshooted over the forum.
Please open a case with our customer support team and upload a debug log package.
Our support engineer will find out possible bottlenecks from the log files.
Best,
Fabian
Performance issues can not be troubleshooted over the forum.
Please open a case with our customer support team and upload a debug log package.
Our support engineer will find out possible bottlenecks from the log files.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- VP, Product Management
- Posts: 6749
- Liked: 1408 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: slow restore oracle
How did you messured the speed?
1) There is some processing overhead that is small on large data sets but high on small data sets.
2) To process just a GB or so on data might not be that fast but total time is low. This is the same for VM processing because you process not really data. Try with hundred GB of data.
1) There is some processing overhead that is small on large data sets but high on small data sets.
2) To process just a GB or so on data might not be that fast but total time is low. This is the same for VM processing because you process not really data. Try with hundred GB of data.
Who is online
Users browsing this forum: No registered users and 118 guests