I recently wrote a blog post about Self-Service configuration options and after reading this thread I've added an update to explain the behaviour you've observed Mayank.
asking how people create their SS configurations.
Original Message:
Sent: 07-25-2019 05:30:07 AM
From: Marcin Kwasninski
Subject: Self-Service
HI Mayank,
No problem, it was nice to help you.
Regards
Marcin
------------------------------
Marcin Kwasninski
Technical Principal
Spica Solutions
Original Message:
Sent: 07-25-2019 05:16:00 AM
From: Mayank Ahluwalia
Subject: Self-Service
Update :
Took a new snapshot -- 35 minutes
Refresh the container -- 12 minutes
So it was indeed taking long due to large number of logs.
Thanks Marcin
Original Message:
Sent: 07-24-2019 10:49:55 AM
From: Mayank Ahluwalia
Subject: Self-Service
Yep, I will try that out once the current process completes.
I will post the observations here, thanks a lot Marcin :)
Regards,
Mayank
------------------------------
Mayank Ahluwalia
Community Member
Higher Logic Community Members
Original Message:
Sent: 07-24-2019 10:06:09 AM
From: Marcin Kwasninski
Subject: Self-Service
HI Mayank,
So the large number archivelogs are causing long refresh(in fact VDB recovery) process.
Take SnapSync's of dSource recently, it improves VDB refresh process.
Regards
Marcin
------------------------------
Marcin Kwasninski
Technical Principal
Spica Solutions
Original Message:
Sent: 07-24-2019 09:58:44 AM
From: Mayank Ahluwalia
Subject: Self-Service
Thank you Marcin.
The dSource has the latest snapshot from 19th July and then lots of logs after that until today, so perhaps that is the reason. Once this completes, I will take a new snapshot for the dSource and then retry the refresh to confirm the observation.
As for the network performance :
Delphix --> Target -- bandwidth is 8 Gbps, latency is in micro secs :)
------------------------------
Mayank Ahluwalia
Community Member
Higher Logic Community Members
Original Message:
Sent: 07-24-2019 09:03:48 AM
From: Marcin Kwasninski
Subject: Self-Service
HI Mayank,
ad 1 We had the same behavior in a low bandwidth or large latency network - check your network to Target
ad 2 I run refresh operation on VDB in JS container on my lab and I have the same situation - see attached screen.
If your database is Oracle, please check how recent SnapSync(dSource) you have, and how many archivelogs are generated after last SnapSync on Source.
Maybe archivelog files causes long recovery operation on your VDB.
Regards
Marcin
------------------------------
Marcin Kwasninski
Technical Principal
Spica Solutions
Original Message:
Sent: 07-24-2019 08:32:57 AM
From: Mayank Ahluwalia
Subject: Self-Service
Thank you Marcin.
I had the same understanding, but why I am getting confused is because :
1. The refresh operation is ongoing for about 45 minutes now for the vDB (Container)
2. In the management app, under Actions - i see a job whose description says "Update Self-Service Source" and it refers to my dSource by name. Wat would this job be doing then ?
Regards,
Mayank
------------------------------
Mayank Ahluwalia
Community Member
Higher Logic Community Members
Original Message:
Sent: 07-24-2019 08:26:54 AM
From: Marcin Kwasninski
Subject: Self-Service
HI Mayank,
If you click REFRESH button in SelfService GUI, your Container VDB(s) will be refreshed to the state in which actually is dSource.
During this operation ONLY container VDB is refreshed to point in time that is your dSource.
In fact there is no REFRESH option for dSource. dSource for eg. can do another SnapSync operation which will get latest changes from you Source DB.
The same situation we have in VBD(parent)->VDB(child) configuration, if you click REFRESH in your JS Container, only child VDB will be refreshed to actual parent VDB state.
Regards
Marcin
------------------------------
Marcin Kwasninski
Technical Principal
Spica Solutions
Original Message:
Sent: 07-24-2019 06:53:49 AM
From: Mayank Ahluwalia
Subject: Self-Service
#self_service #self-service #virtualization
Hi Team,
I have a very basic question.
If i add a dSource as a source in Data Template, and then add a vDB provisioned from that source as a Container in the created Template, then :
1. When i refresh the container through Self-Service, does it only refresh the vDB from the source which is the dSource, OR,
2. It first refreshes the dSource from the real source and then refreshes the vDB to the latest copy ?, OR,
3. The behavior is configurable to have both options ?
Regards,
Mayank