D-PVM-OE-01 Practice Questions

Set up the migration environment to migrate applications from the source array to the target array.

Examine the specific storage for the applications on the source array and automatically provision equivalent storage on the target array.

Initiate data synchronization from the source to the target and cutover to make source array paths inactive so target array services all host I/O.

Commit the necessary changes after the source to target data synchronization is complete and all application data has been migrated to the target.

Remove the configured array-to-array connectivity for the data migration pathway on both storage arrays.

Correct Order:

Set up the migration environment to migrate applications from the source array to the target array.

Why:This is the initial setup phase, where you configure the necessary settings on both the source and target arrays to enable the migration. This involves actions like:

Verifying compatibility between the source and target arrays.

Ensuring that the required licenses are in place (e.g., NDM license).

Configuring network connectivity (FC or iSCSI) for data transfer between the arrays.

Examine the specific storage for the applications on the source array and automatically provision equivalent storage on the target array.

Why:Before migrating data, you need to ensure that the target array has the appropriate storage capacity and configuration to host the applications.

How:NDM can often automatically provision equivalent storage on the target based on the source configuration. This includes creating storage groups, volumes, and masking views that mirror the source.

Initiate data synchronization from the source to the target and cutover to make source array paths inactive so target array services all host I/O.

Why:This is the core of the migration process. Data is copied from the source to the target while the application continues to run. Cutover is the final step where I/O is redirected to the target array.

How:

Synchronization:Data is copied in the background.

Cutover:Once synchronization is complete, a brief cutover is performed. In a well-planned NDM, this cutover is designed to be within the I/O timeout limits of most applications.

Commit the necessary changes after the source to target data synchronization is complete and all application data has been migrated to the target.

Why:This step finalizes the migration and makes it permanent.

What it involves:The migration session is acknowledged and the configuration is finalized on the target array.

Remove the configured array-to-array connectivity for the data migration pathway on both storage arrays.

Why:After the migration is complete, the temporary connections used for data transfer between the arrays should be removed to free up resources and maintain a clean configuration.

What it involves:This typically means removing the FC zones or iSCSI settings that were configured specifically for the NDM process.

Okay, I understand. We need to configure a recurring exclusion window in the Unisphere for PowerMax simulator to exclude performance load during a weekly backup that occurs every Sunday from 8:00 AM to 9:00 AM. This exclusion will prevent the backup load from affecting system-level compliance calculations.

Here's a step-by-step guide on how to do this, based on typical Unisphere functionality:

Steps:

1. Launch the Simulator and Navigate to the System Settings

Open Unisphere for PowerMax in your web browser.

Log in to the simulator (you should already be logged in with the array SID 1762 selected, based on the image).

In the left-hand navigation pane, locate the settings or configuration section. The exact location might vary slightly, but it's often found under:

Home>System Settings

Settings(an icon representing settings, like a gear)

Admin>System

In this instance, click thegearicon on the top right corner of the Unisphere interface.

2. Find the Exclusion Window Settings

Within the system settings, look for a section related to performance monitoring, metrics, or thresholds.

Within this section, search for an option to configure "Exclusion Windows," "Scheduled Exclusions," or something similar. The exact name may vary.

3. Create a New Exclusion Window

Click on a button or link to create a new exclusion window. This might be labeled:

"Create"

"Add"

"+"(a plus icon)

A new window or panel will appear, allowing you to configure the exclusion window settings.

4. Configure the Exclusion Window Settings

Name (Optional):You can give the exclusion window a descriptive name, such as "Weekly Backup Exclusion."

Type:Select"Recurring"or"Repeating"as the exclusion window type.

Schedule:

Day of the Week:Select"Sunday".

Start Time:Set the start time to 08:00 (or 8:00 AM). Make sure the time is in 24-hour format or that you correctly select AM if using 12-hour format.

End Time:Set the end time to 09:00 (or 9:00 AM).

Scope/Target:Since we want this exclusion to apply at the system level, make sure the scope is set to"System"or the entire array (SID 1762 in this case). You might not need to explicitly select this if system-level is the default.

Components/Metrics:In some Unisphere versions, you can choose which components or metrics to exclude. In our case, we want to exclude the load for "all components." If there's an option to select components, either choose "All" or leave it at the default (which likely includes all components).

5. Save the Exclusion Window

After configuring all the settings, review them carefully to make sure they are correct.

Click the button to save the exclusion window. This might be labeled:

"Create"

"Save"

"OK"

"Apply"

6. Verify Exclusion Window Creation (Optional)

After the exclusion window is created, you can usually verify its settings in the exclusion window list.

You should see the new exclusion window listed with the correct schedule (Sunday, 8:00 AM - 9:00 AM) and scope (system level).

Topic2, Multiple Choice Questions