Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Druva Phoenix support to backup and restore virtual machines hosted on vSAN datastore (51601)

Last Updated: 11/30/2019Categories: InformationalTotal Views: 4114Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article provides information about Druva Phoenix.

Disclaimer:​ The partner solution referenced in this article is a solution that is developed and supported by a partner. Use of this product is also governed by the end user license agreement of the partner. You must obtain from the partner the application, support, and licensing for using this product. For more information, see Druva Support.

Resolution

Use Cases

To backup and restore virtual machines residing on a vSAN datastore.

To perform file level restores to virtual machines residing on a vSAN datastore.

Solution Architecture

Phoenix includes Phoenix Cloud and Phoenix backup proxy. Phoenix Cloud is the server component hosted on AWS, and is managed by Druva, while the Phoenix backup proxy is the client component that you need to deploy on the hypervisor which hosts virtual machines that you want to backup. Phoenix backup proxy communicates with Phoenix Cloud to initiate scheduled backups and restores. Phoenix Cloud acknowledges the requests and assigns the request to a storage within the cloud.

Solution Components

Phoenix solution includes the following components to successfully execute the backup and restore activities.

Phoenix Cloud

The server side Phoenix component hosted on AWS. Phoenix Cloud comprises the following components:

​Phoenix Master: Amazon EC2 instances that authorize outgoing and incoming requests to and from the backup proxy. It also authorizes administrator logins through the Phoenix Management Console.

Customer Configuration: The RDS that stores customer settings such as backup schedule, retention settings, and auto-configuration rules.

Storage: The elastic, on-demand S3 storage that stores data backed up from different servers at a dedicated location on the cloud. A single Phoenix setup can be associated with multiple instances of storage. You can purchase multiple instances of storage using credits depending on your data needs and location preferences. Also stores DynamoDB managed metadata.

Phoenix Management Console: A Web-based, unified console for monitoring the servers you manage, irrespective of the location of the servers. Using this management console, Phoenix administrators can register and configure servers for backup, define backup policy and retention policy, and monitor backup and recovery jobs, activities, and reports.

Phoenix backup proxy

The client side component of Phoenix. The Phoenix backup proxy is a virtual machine that you deploy in your VMware setup to backup and restore virtual machines. The Backup proxy is the client side component that:

Detects virtual machines on the VMware setup

Creates virtual machine snapshots for backup

Executes backup and restore jobs

Phoenix CloudCache (optional)

Phoenix CloudCache is an optional component hosted on a dedicated server that locally stores up to 30 days of backup data from Phoenix agents, and periodically synchronizes this data to Phoenix Cloud.

Phoenix CloudCache is deployed within the perimeters of remote office locations or data centers. This ensures that Phoenix agents can locally connect to Phoenix CloudCache, thus accelerating backups and restores of local data. Moreover, administrators can schedule synchronization operations from Phoenix CloudCache to Phoenix Cloud during off-peak hours, thus ensuring an optimized utilization of WAN bandwidth.

To get started with Phoenix, see Phoenix documentation.

For detailed VMware specific documentation, see Backup and Restore VMware Virtual Machines.

For Druva Phoenix system requirements, see System Requirements.

For steps on how to deploy Phoenix backup proxy to backup and restore virtual machines in your environment, see:

About Phoenix backup proxy for VMware

Download backup proxy and generate activation token

Register vCenter using web client

Backup proxy load balancing

Configure virtual machines for backup

Automatically configure virtual machines for backup (vCenter only)

For more information on Phoenix CloudCache, see Phoenix CloudCache.

Support Information

Troubleshooting (logs, procedures and techniques

Link to product documentation

Link to downloads site

Link to steps to collect partner SVM logs

Support Process, SLA and Escalation Process

Contact information

Error codes

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vSAN が有効になっていないクラスタで「Virtual SAN ライセンスの有効期限が切れました」というアラームが表示される (51458)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
使用 WinSCP 连接到 vCenter Server Virtual Appliance 6.0 失败：收到的 SFTP 数据包过大 (2115983)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 7.0.x

VMware vSAN 6.6.x

VMware vSAN 6.5.x

Take Our Survey

Support Assistant