Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 535.7K On-Premises Infrastructure
- 138.1K Analytics Software
- 38.6K Application Development Software
- 5.6K Cloud Platform
- 109.3K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71K Infrastructure Software
- 105.2K Integration
- 41.5K Security Software
Paralel backup vs normal backup

Hello im learning Rman i have question which one is better paralel backup or Normal backup(only use 1 channel)
what are the advantage of paralel backup ? is it because there is a lot of channel the backup process become faster?
and also does rman read all of the separated backup sets created by paralel backup?
in my opinion normal backup is simple because we have to manage 1 file only while paralel backup create mutiple file which make it harder to mantain.
Best Answers
-
so what you mean is using more channel is better even at situation?
Even at what situation?
What I'm saying is
1) using more channels (up to a point) will yeild faster performance
2) using more channels does not impose any more admin burden on the DBA.
-
can i have some clarification about this please?
Perhaps this will help: https://stackoverflow.com/questions/40163095/what-is-socket-core-threads-cpu
Answers
-
Parallel backup is faster for the same reason any other parallel operation is faster than the single thread/channel/path version of the same operation. For the exact same reason that a 6-lane highway can move a given traffic load faster than a 2-lane highway.
in my opinion normal backup is simple because we have to manage 1 file only while paralel backup create mutiple file which make it harder to mantain
Even a single-channel backup can create multiple files, depening on MAXSETSIZE and CONTROLFILE AUTOBACKUP. In any event, it's rman that maintains them, no you, so it is no more difficult to maintain the backups from multi-channel, parallel backups than for single-channel backups.
-
so what you mean is using more channel is better even at situation?
-
In terms of results, running RMAN in parallel or not makes no difference: what is backed up, in how many backupsets , the output volume etc. will not change. With a DEGREE OF PARALLELISM of 8 for instance, 8 CPUs will be involved in your backup, instead of one if you do not run RMAN in parallel (DOP=1), so it should run faster, which should be taken into consideration when backing up high volumes.
Also note that to use PARALLELISM, you must have the Enterprise Edition of the Oracle database -- it's not available with the Standard Edition.
-
so what you mean is using more channel is better even at situation?
Even at what situation?
What I'm saying is
1) using more channels (up to a point) will yeild faster performance
2) using more channels does not impose any more admin burden on the DBA.
-
Even at what any situation?*
sorry forgot to update that. also i have question about the cpu. how do i get information of number of cpu in hardware.
thanks
-
also i have question about the cpu. how do i get information of number of cpu in hardware.
That would be an OS question. And you haven't stated your OS.
So, what did you discover when you googled "how many cpus does my computer have?"
-
my OS is windows
and my hardware have 1 CPU 4 Cores and 8 logical process
from what i know all hardware usually have 1 cpu. but when i googled it there is a hardware that have mutiple cpu.but my question is when we talking about "CPU" are we referencing the core or actual cpu?this makes me confuse because i read from a blog that an optimal parallelism is based on your hardware cpu.
does that means the optimal parallelism is either 1(CPU) or 4(based on core) and from what i know production database usually run 2 or more degree of paralellism so i assume we talk about the cores of the cpu instead of the actual cpu
can i have some clarification about this please? thanks
-
can i have some clarification about this please?
Perhaps this will help: https://stackoverflow.com/questions/40163095/what-is-socket-core-threads-cpu