Pre-migration tasks

Before performing data set migrations, you should complete the pre-migration tasks to ensure that the migration will go smoothly and to minimize the risk of problems.

Use the following list to help with the pre-migration tasks. For more information, see Table 1 and Table 2.
  1. Identify the application owners.
  2. Notify the entire application community about the upcoming migration at least 30 days prior to the intended migration date. Include an invitation to attend the initial migration kickoff meeting.
  3. Gather information about the SMS storage environment and applications.
  4. Inform Security and Compliance groups about the migration.
  5. Schedule a pre-migration rehearsal that includes all the members of the migration team and a plan that will enable the application groups to appropriately conduct the pre- and post-migration verification process.
  6. Establish a weekly meeting schedule that includes remote participants.
  7. Identify and follow the required Change Control process.
  8. Establish a Migration Status call-in process.
  9. Use the checklist to ensure that all of the pre-migration planning steps have been executed.
  10. Perform a catalog diagnostic.
  11. Create a new target volume SMS Storage Group Configuration.
  12. Add the target volume to the appropriate storage group in DISNEW status.
  13. Change the status of the source configuration to DISNEW.
  14. Create a list of source volumes that contain data to be moved and the associated target volumes or storage group.
  15. Establish an HLQ for the new target data sets.
  16. Establish a naming standard for the migration groups.
  17. Identify the time slot you want to the migration process to transition from mirroring to diversion, and then to completion, based on DSN or group activity, and fallback requirements.
    Note: Based on internal policies associated with a data migration process, some of the aforementioned list items may not be applicable.
    Table 1. Pre-migration planning checklist
    Action Item Assigned to Status
    Create a migration management team consisting of the following people:
    • Primary Migration Manager
    • Alternate Migration Manager
    • Application Coordinator
    • Security Coordinator
    • Technical Lead Coordinator
    		   
    Create a migration team to perform the pre-migration tasks; ensure that the team members have been trained to use zDMF and can also act as migration mentors.    
    Identify the application owners.    
    Notify the entire application community about the upcoming migration at least 30 days prior to the intended migration date. Include an invitation to attend the initial migration kickoff meeting.    
    Gather information about the SMS storage environment and applications.    
    Inform the security and compliance groups about the migration.    
    Schedule a pre-migration rehearsal that includes all the members on the migration team and define a data sampling that will enable the application groups to appropriately conduct the pre- and post-migration verification process.    
    Establish a weekly meeting schedule that includes remote participation dial in.    
    Follow the required Change Control process.    
    Establish a migration status call-in process.    
    Use the Migration Planning Checklist to ensure that all of the Pre-migration planning steps have been completed.    
    Perform a catalog diagnostic.    
    Create the new target volume SMS Storage Group Configuration.    
    Add the target volume to the appropriate storage group in DISNEW status.    
    Change the status of the source configuration to DISNEW.    
    Create a list of source volumes that contain data to be moved and the associated target volumes or storage group.    
    Establish an HLQ for the new target data sets.    
    Establish a naming standard for the migration groups.    
    Identify the time slot you want to move from mirroring to diversion to completion based on DSN or group activity, and fallback requirements.    
    Table 2. Migration Action Item Checklist . Populated as part of pre-planning process.
    Action Item Assigned to Status