Phoenix extends its backup capabilities for servers that run mixed workloads. This feature provides the ability to configure multiple backup sets of File server (Windows) and MS-SQL server for a single server.
Phoenix exhibits the following behavior while configuring a server or during backup of the server that runs mixed workload:
- You can attach two backup policies to the server types: File server and MS-SQL server. However, you cannot attach two backup policies of the same type. For example, you cannot attach two File server or two MS-SQL server backup policies to a server group.
- You can attach only one retention policy to the server group.
- Phoenix creates the restore points differently for the File server and MS-SQL server workloads.
- For mixed workloads, the Backup Now button on the Servers tab (Server Group detailed page) and the Configured (Servers) tab, triggers the backup for both workloads.
- You can detach a previously attached backup policy barring the last one. However, you must be careful as the restore points of the detached backup policy get deleted for all the servers that are attached to the server group. If you want to retain the restore points associated with a backup policy but do not want to backup a particular workload, you can disable the backup instead of detaching a particular backup policy.
- If you change the backup policy attached to a server to a backup policy of the same type (for example, File server backup policy with another File server backup policy), Phoenix retains and merges the restore points of the previous backup policy with the restore points of the new backup policy.
- While reconfiguring a server, if you attach a server to a server group, which does not have a policy type same as the previous server group, the restore points are deleted corresponding to the unmatched policy type. For example, if a server attached to a server group with the File server and MS-SQL server backup policies, is reconfigured to a server group having only File server backup policy, then the restore points corresponding to the MS-SQL server backup policy type get deleted. Phoenix retains and merges the restore points of the File server policy with the restore points of the File server policy of the new server group.
While configuring a File server or MS-SQL server policy for a mixed server, you must consider the following points:
- You cannot attach an MS-SQL backup policy to a server group containing servers with Linux and Windows operating systems.
- You cannot attach a server having agent version 1.x with a server group having MS-SQL server policies.
- You cannot attach an MS-SQL backup policy to a server group containing servers with agent versions 1.x.
- If multiple servers, including Linux servers and Windows servers with agent version 1.x, are selected for configuration, then only supported clients get configured.
- You cannot attach a Linux server to a server group having MS-SQL policies.
- You cannot attach an MS-SQL backup policy to a server group containing servers with unsupported Windows operating system for MS-SQL server. For more information about the supported operating systems, see Support Matrix.
- You can have only one retention policy associated with a server group for the File server and MS-SQL server workload.
- The server group cannot have multiple policies for the same agent. For example, you cannot attach two File server or two MS-SQL server backup policies to a server group.
- For mixed workloads, you cannot trigger a restore simultaneously for File server and MS-SQL server. You need to wait before the restore of a particular workload finishes.
- You cannot directly delete a backup set for a server. However, as a workaround (not recommended), you can delete the server, which in turn would also delete the other backup set for the server.
- When you filter servers using the Last Backup Status filter, the result lists down all the servers for which that status is available, even if the other backup policy type for those servers have different statuses. For example, if you filter servers using the Successful status, the result lists the servers with Successful status. Additionally, for those servers, it will also list the other statuses, such as Failed, Successful with errors, and so on.