Banner: Request a Data Clone from Production to a Development Instance

Question

How do I request a data clone?

Answer

A clone request is a request to copy production data to a specific development instance. Clone requests are submitted by YSU data custodians or IT Application Services staff members.      

  1. Receive confirmation from all data custodians. 
    • The requestor will send an email to the functional user group (ebot@lists.ysu.edu) informing everyone of a clone request for a specific development instance.   
    • After all data custodians reply with their approval of a clone request for the specific development instance, the request can be created. 
  2. Create the clone request using the TDX Banner Change Request service. 
  3. Assign the clone request to the DBA group.
    • The IT Applications Services manager/director will assign the request to the DBA group and add the six (6) data custodians to the request.
    • The IT Applications Services manager/director will then coordinate with the DBAs and the requestor to identify a clone date/time and communicate this date/time to the functional user group (ebot@lists.ysu.edu).
      • Clones are normally performed during our regular maintenance window Monday – Friday from 5:00 – 7:00 a.m. so that the development instance is not down for an extended time. This will likely take 3-4 hours, so plan for the development instance to be inaccessible from 5:00 – 8:30 a.m.
      • In special cases, clones can be performed outside of the regular maintenance window. If a clone will occur during that time, advanced notice must be given to the functional user group (ebot@lists.ysu.edu) for confirmation.    
  4. Check the code tree date.
    • The DBA will verify that the code tree is current. If the last clone of the code tree is outdated, the DBA will inform the IT Applications Services manager/director to consider a clone of the code tree also.
  5. Upon completion of the clone request, the responsible DBA will:
    • Verify the post-clone script ran successfully, ensuring the development instance is not pointing to production
    • Communicate the clone completion to the function user group (ebot@lists.ysu.edu)
    • Change the clone request status to Completed
Was this helpful?
0 reviews

Details

Article ID: 80005
Created
Thu 6/6/19 12:50 PM
Modified
Fri 7/23/21 9:50 AM