Enterprise Vault.cloud Migration to Azure - Critical Configuration Changes

Enterprise Vault.cloud Migration to Azure - Critical Configuration Changes

Article: 100041991
Last Published: 2018-04-11
Ratings: 6 1
Product(s): Enterprise Vault.cloud

Critical Configuration Changes for Enterprise Vault.cloud after migration to Microsoft Azure

 
  1. What is Veritas Enterprise Vault.cloud doing?
  2. When will the migration occur?
  3. What will happen to customer data?
  4. Will there be any impact to the service?
  5. Do customers need to take any action?
  6. What happens if customers do not make the changes above?
  7. Do customer who use O365 need to make changes?
  8. What will happen to the websites?
  9. How long will DNS replication take after we make the changes during the migration?
  10. What will happen to customer data in the event of a rollback?
  11. What actions does a customer need to take post migration?
  12. Do customers that use dual journaling for Enterprise Vault.cloud and Advisormail need to make any changes?

Veritas will be decommissioning SymantecCloud.com websites after migration to Microsoft Azure

 

Organizations should stop using *.symanteccloud.com addresses and use the *.archive.veritas.com equivalent as seen in the chart below, and any bookmarks to these sites should be updated.  In the case that an Outlook webfolder is being used please see article 100042624 for steps to take.

US

 Application  SymantecCloud.com  Veritas
 Personal Archive  https://personal.us.symanteccloud.com  https://personal.us.archive.veritas.com
 Discovery Archive  https://discovery.us.symanteccloud.com  https://discovery.us.archive.veritas.com
 Manage  https://manage.us.symanteccloud.com  https://manage.us.archive.veritas.com
 

EU

 Application  SymantecCloud.com  Veritas
 Personal Archive  https://personal.eu.symanteccloud.com  https://personal.eu.archive.veritas.com
 Discovery Archive  https://discovery.eu.symanteccloud.com  https://discovery.eu.archive.veritas.com
 Manage  https://manage.eu.symanteccloud.com  https://manage.eu.archive.veritas.com
 

Veritas will maintain a maintenance page for a week after migration to Microsoft Azure. Post that week the *.symanteccloud.com address will be decommissioned, and the website will not load.


1. What is Veritas Enterprise Vault.cloud doing?

Veritas is migrating Enterprise Vault.cloud into Microsoft Azure.


2. When will the migration occur?

The migration to Microsoft Azure is planned to occur on the following dates for the following regions:

Asia Pacific and Japan: Completed (March 10, 2018)
Europe, Middle East, Africa: Competed (March 25, 2018)
Americas: Completed (March 31, 2018)

A MIR3 notification will be sent prior to the planned mainteance outlining the maintenance window.

 


3. What will happen to customer data?

All data will migrated into Microsoft Azure.


4. Will there be any impact to the service?

Veritas is working to migrate to Microsoft Azure with as minimal impact to customers as possible. There will be scheduled maintenances where websites and services will be unavailable during the migration.
During the migration, customers will not be able to log into websites as there will be maintenance pages up. The journaling addresses will also be down and unavailable during the migration. An organizations email server(s) will temporarily queue email in the outbound journal queue until the migration is complete. Organizations may need to check the outbound journaling queue, and retry messages after the migration that are still in the queue.


5. Do customers need to take any action?

Yes. As part of the migration into Azure, Enterprise Vault.cloud services will be on a new public IP address range. If your organization is currently restricting specific IP addresses for each service then you will need to add the following addresses. These IP addresses are configured on an organizations network, and the organization's network team will need to be engaged to have these IP addresses updated.

 

***We recommend that you add the new IP addresses ahead of time so that journaling is uninterrupted, and can remove the current (old) IP addresses after the migration.***

 

If organization is on ELS (US) Data Center add the respective IP addresses for the service(s) to white-list:

 SERVICE  CURRENT IP RANGE  NEW IP
 Journaling  199.30.224.0/24  40.65.105.55
 Lync On-Premises    199.30.224.0/24  40.65.104.49
 Email Continuity
 Personal Archive Restores
 Personal Archive WebMail
 64.70.67.0/24  40.65.111.175
 Folder Sync  64.70.67.0/24  40.65.112.236
 CloudLink  64.70.67.0/24  40.65.104.88
 

If organization is on AMS (European) Data Center add the respective IP addresses for the service(s) to white-list:

 SERVICE  CURRENT IP RANGE  NEW IP
 Journaling  199.30.227.0/24  13.95.169.147
 Lync On-Premises    199.30.227.0/24  13.95.169.147
 Email Continuity
 Personal Archive Restores
 Personal Archive WebMail
 199.30.227.0/24  52.166.22.204
 Folder Sync   199.30.227.0/24  52.174.244.53
 CloudLink  199.30.227.0/24  13.95.120.160
 

If organization is on SYD (Australian) Data Center add the respective IP addresses for the service(s) to white-list:

 SERVICE   OLD IP RANGE  CURRENT IP
 Journaling  199.30.225.0/24  13.70.66.114
 Lync On-Premises  199.30.225.0/24  13.70.66.114
 Email Continuity
 Personal Archive Restores
 Personal Archive WebMail
 199.30.225.0/24  13.70.66.54
 Folder Sync  199.30.225.0/24  13.72.254.53
 CloudLink  199.30.225.0/24  13.72.242.186
 

If organization is on MIA Data Center add the respective IP addresses for the service(s) to white-list:

 SERVICE  OLD IP  CURRENT IP
 Journaling  8.30.107.18  52.183.94.219
 Lync On-Premises  8.30.107.18  52.183.94.219
 Email Continuity
 Personal Archive Restores
 Personal Archive WebMail
 8.30.107.13  52.183.88.192
 Folder Sync   8.30.107.15  52.229.30.213
 CloudLink   8.30.107.26  52.175.242.24

6. What happens if changes above are not made?

If an organization restricts journaling to specific IP address ranges, then after the migration, the journaling queue will build up on the servers. If IPs are not white-listed, a mail server may run out of space or start dropping the messages in the journal queue.  Be sure to check firewalls and firewall appliances that may restrict such access.


7. Do customers using O365 need to make changes?

If your organization has a send connector setup, please ensure that it is up to date with the latest settings for TLS shown in article 100013747.  Please note the settings have changed since October 2017.  If a specific IP address is being used for SmartHosting then refer to article 100042146 for the updated IP address.


8. What will happen to the websites?

Normally, white-list or hardcode DNS records for websites are not needed, so the vast majority should see the new Azure-based websites after migration.  If websites are unable to load after migration or see a maintenance page stating them to update DNS, Make sure DNS servers are refreshed, cache cleared, and that there are no hardcoded DNS entries for our websites.


9. How long will DNS replication take after we make the changes during the migration?

In past migrations, worldwide DNS updates were seen to complete within 2 hours. However, worldwide DNS root servers could take up to 2 days, but usually this is much faster, often around a few hours.


10. What will happen to customer data in the event of a rollback?

If a rollback occurs, customer data will cut back over to the on-prem datacenter. As mentioned above, journaling will not be accepted during the migration. Thus, a clean rollback to the on-prem datacenter will occur without having accepted any data in Microsoft Azure. However, in the event of a rollback, the original IP in the white-lists should not be removed until the migration is complete


11. What actions does a customer need to take post migration?

Post migration an organization should monitor the outbound journal queue in the mail system. There will be a buildup of items in the queue due to services being down during the maintenance window. After the completion of the migration this buildup of items should reduce as those items will be sent and archived in Enterprise Vault.cloud.


12. Do customers that use dual journaling for Enterprise Vault.cloud and Advisormail need to make any changes?

No configuration changes will need to be made to journal rules or send connectors with organizations that use this setup. However the Journal servers will need to have enough disk space to hold queued journal messages on the servers during the maintenance window, when the journal address being used ends in archivecloud.net. If the journal address does not end in archivecloud.net the messages will be queued on Veritas servers. Once the migration is complete data will be delivered automatically to both systems as with any normal maintenance.


To view the original FAQ sent regarding more details about the migration please reference article 100040593
To view the hostnames of the services, and their IP address please reference article 100042146


 

Was this content helpful?