Remote Proactive Services Average Activity Lengths and Lead Times
Summary: This article provides estimates on scheduling lead time when booking Remote Proactive Services (RPS) upgrades.
Instructions
This article is updated with fresh content every Monday to reflect the latest Lead Times status.
Availability may exist sooner than the times set below. Always check for wanted availability.
Table 1. Remote Proactive Services (RPS) upgrades
|
Product |
Activity |
Duration and Notes |
Current Average Time To Available Slots (Midweek) |
Current Average Time To Available Slots (Weekend) |
|---|---|---|---|---|
|
Avamar |
OE Code Upgrade |
6 hours |
1 day |
Manual Resourcing |
|
Connectrix |
Code Upgrade |
One Hour + 30 Minutes for additional jumps |
2 days |
13 days |
|
Disk Library for mainframe (DLm) |
Code Upgrade |
For DLm2500: 2.5 hours For DLm8500: The duration varies depending on the number of VTEs and whether the upgrade is performed in a staggered or offline manner.
|
Manual Resourcing |
Manual Resourcing |
|
ECS |
ECS Upgrade |
Upgrade times can vary greatly based on the number of nodes and upgrade path. 12 Hours Average for OS and Fabric Upgrade (expected duration estimated During TC) |
3 days |
6 days |
|
PowerScale/Isilon |
Full Isilon Upgrade |
Upgrade times can vary greatly based on the number of nodes and upgrade path. A full PowerScale upgrade may contain some or all the following:
|
2 days |
13 days |
|
Metro node |
Code Upgrade |
2.5 hours |
8 days |
13 days |
|
PowerProtect Data Domain |
DDOS Upgrade |
3.5 hours |
2 days |
Manual Resourcing |
|
PowerProtect Data Protection (IDPA) |
OE Code Upgrade |
10.5 hours |
2 day |
N/A |
|
PowerProtect Data Manager Appliance (DM5500) |
OE Code Upgrade |
6 hours |
5 days |
N/A |
|
RecoverPoint |
Code Upgrade |
Subject to Change Control Approval. |
8 days |
13 days |
|
Midrange (PowerStore, Unity, VNX, VNXe) |
Code upgrade |
PowerStore - 5.5 hours
|
3 days |
6 days |
|
VMAX3/PowerMax (v3 arrays) |
Default Reserved Slot |
The duration varies depending on the type of activity:
|
1 day |
6 days |
|
PowerMax v4 |
Default Reserved Slot |
The duration varies depending on the type of activity:
|
1 day |
6 days |
|
VPLEX |
Code Upgrade |
3.5 hours based on a Metro Configuration
Subject to Change Control Approval. |
11 days |
13 days |
|
VxRail |
Upgrade |
Upgrade times can vary greatly based on the number of nodes and upgrade path. 9.5 hours average - 1.5 hours per node (personalized estimate to be provided during TC) |
2 days |
13 days |
|
VCF on VxRail (VoV) |
Code Upgrade |
VoV upgrades are longer upgrade engagements that depend primarily on the number of WLDs and number of nodes (hosts). Lead time presented here is purely an indication of when there are available free slots in the schedule to start these engagements. It does not indicate that your upgrade has been scheduled. A technical consultation must be scheduled and performed to calculate the upgrade duration after which the upgrade scheduling can occur. |
Manual Resourcing |
Manual Resourcing |
|
XtremIO |
Code Upgrade (one X-Brick) |
Two hours (Add 30 minutes per additional X-Brick) |
8 days |
13 days |
|
PowerFlex |
RCM/IC Upgrade |
TBD |
Manual Resourcing |
Manual Resourcing |
Additional Information
Tips:
- Plan upgrades as far in advance as possible.
- Follow best practices by reviewing the upgrade preparation guides ahead of upgrades.
- Provide Upgrade Readiness Utility logs where your product supports those to improve the scheduling experience.