Skip to main content
Action required - New Druva Cloud Upgrade Process
Updated over a week ago

About new upgrade process

Starting February 18th, 2023, Druva will be implementing a rolling upgrade or a staggered process across supported AWS regions. The upgrade will be performed on a subset of the supported AWS regions at a time to align better with business work hours. To know more, see Druva Cloud Upgrade Process.


❗ Important

Perform the actions mentioned in this article ONLY if you have received explicit communication from Druva Support.


What is the new Cloud Upgrade schedule?

Here is the new Cloud Upgrade schedule -

Druva Services

APAC AWS Regions

Rest of the World AWS Regions

Endpoints & SaaS Apps

Every other Saturday, beginning February 25th, 2023.

Time - 9:00 AM UTC or 5:00 PM SGT onwards

Every other Saturday, beginning March 04, 2023.

Time - 9:00 AM UTC or 01:00 AM PST onwards

Hybrid Workloads

(also referred to as "Phoenix")

1st and 3rd Monday of each month, beginning February 20th, 2023.

Time - 2:00 PM UTC or 10:00 PM SGT onwards.

2nd and 4th Monday of each month, beginning February 27th, 2023.

Time - 5:00 AM UTC onwards

Phoenix GovCloud

2nd and 4th Monday of each month.

Time - 8:00 AM UTC onwards


❗ Important

NOTICE – AVAILABILITY OF SERVICES AND CHANGE IN SERVICE LEVEL AGREEMENT.

This communication serves as your notice of a change to the scheduled maintenance days and times for inSync, Phoenix, and Phoenix GovCloud in your service level agreement with Druva, which is part of your customer agreement. By continuing to use the Druva Cloud services, you consent to the changes in Table 1 above to the “Category 1 – Scheduled Maintenance” days and times listed in your service level agreement, effective as of the date the change takes effect in your geographic region. All other terms and conditions will remain in full force and effect.


What actions do you need to do?

To successfully shift to the staggered deployment of its services, Druva has made changes that allow for geography-specific downtime timelines instead of a single worldwide downtime timeline.

You must upgrade the Druva components deployed in your environment to ensure that upgrade of services is seamless with the new Druva Cloud.

Endpoints & SaaS AppsHybrid Workloads

Upgrade the deployed Druva Components

Upgrade the following listed components to the latest version if deployed in your environment.


❗ Important

You must upgrade the deployed components to the latest version to avoid downtime twice, which is a minimum of 90 minutes each, due to scheduled upgrade every week across regions.


Name of the Component

Upgrade Instructions

AD Connector

For upgrade instructions, seeUpgrade AD Connector.

eDiscovery Download Client

For upgrade instructions, seeUpgrade eDiscovery Download Client.

Troubleshoot the Service/Job

Name of the Service/Job

Impact

Action Required

If you have configured Multi-Factor Authentication (MFA) and use Authenticator App for login

MFA for administrators will be reset.

Every administrator must reconfigure their MFA.

Druva UI will automatically prompt the administrators to reconfigure their MFA after they log in using password-based authentication.

Email MFA Backup Codes

To know more about Backup Codes, see FAQs.

Old Backup Codes will automatically expire.

Every administrator will receive a new set of Backup Codes over their registered email.

PST Download jobs for

  • Exchange Online

  • Gmail

Ongoing PST Download Jobs will fail.

For completed PST Jobs, old Download links will not be valid.


You must initiate a new PST Download Job. For instructions, see Download Exchange Online Data.

eDiscovery Data Download Jobs

All active, pending, and queued jobs will fail. The status will be updated to ‘Canceled’.

You must initiate a new eDiscovery Data Download Job.

WebDAV Data Access URL for data access used with 3rd party tool integrations

WebDAV Data Access URL will change

Configure the new Data Access URL from your Legal Hold policy.

Upgrade the deployed Druva Components

Upgrade the following listed components to the latest version if deployed in your environment.


❗ Important

You must upgrade the deployed Hybrid Workload Clients to the latest version to avoid downtime twice, which is a minimum of 90 minutes each, due to scheduled upgrade every week across regions.


Name of the Hybrid Workload Client

Upgrade Instructions

Linux (RPM, DEB)

For upgrade instructions, see

Windows (FS, SQL, NAS)

Phoenix CloudCache

  • CloudCache (Windows)

  • CloudCache ( Linux)

For upgrade instructions, see Upgrade Phoenix CloudCache.

VMWare Backup Proxy

For upgrade instructions, see Upgrade Backup Proxy.

Nutanix Backup Proxy

For upgrade instructions, see Upgrade the Backup Proxy.

DR Proxy

For upgrade instructions, see Upgrade Phoenix AWS Proxy.

HyperV FLR Proxy

For upgrade instructions, see Upgrade HyperV FLR Proxy.

Phoenix Backup Store

For upgrade instructions, see Upgrade Phoenix Backup Store.

Oracle DTC

For upgrade instructions, see Upgrade Phoenix Agent.

NAS Proxy (Linux)

Troubleshoot the Service/Job

Name of the Service/Job

Impact

Action Required

If you use AWS Private Link

AWS Proxy or Druva Proxy will fail to connect with Druva Cloud leading to DR jobs failure.

You must create new VPC Endpoints and update DNS routing information with updated configuration for the following -

  • Druva node service

  • AWS S3 service

  • Update Route 53 DNS records

For instructions, see

Proxy will fail to connect with Druva Cloud leading to backup job failures.

For instructions, see the link for your workloads under protection,

DR Restore Jobs

All active and queued jobs will fail.

You must initiate a new DR Restore job.

For instructions, see Update DR Copy Availability.

If you have configured Multi-Factor Authentication (MFA) and use Authenticator App for login

MFA for administrators will be reset.

Every administrator must reconfigure their MFA.

Druva UI will automatically prompt the administrators to reconfigure their MFA after they log in using password-based authentication.

Email MFA Backup Codes

To know more about Backup Codes, see FAQs.

Old Backup Codes will automatically expire.

Every administrator will receive a new set of Backup Codes over their registered email.

Logs

Logs for all the supported activities will be available only for the last 30 days.

To obtain logs that are more than 30 days old, raise a case with Druva Support.

Deprecation Announcement

After Feb 18, 2023, the Insights offering that consists of the following features for NAS and File Servers (Windows/Linux) will no longer be available in the APAC region -

  • File Analytics

  • Recommendations

For more information, raise a case with Druva Support.

Did this answer your question?