[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[[["\u003cp\u003eConflicts during appliance import, such as differing backup templates or roles, must be resolved on the appliance experiencing the conflict by renaming, modifying policies or attributes, or modifying services/rights.\u003c/p\u003e\n"],["\u003cp\u003eWhen adding appliances in sharing mode, the primary appliance must be added to the management console before the dependent appliance to ensure proper object import.\u003c/p\u003e\n"],["\u003cp\u003eIf an invalid IP address or FQDN is entered, or if the appliance is already managed by another management console, an error will be displayed, requiring the correct information to be entered or the appliance to be removed from the existing console.\u003c/p\u003e\n"],["\u003cp\u003eWhen importing backup templates, roles, and users, the management console will resolve conflicts for templates and roles, while ignoring users with the same names that already exist on the console.\u003c/p\u003e\n"],["\u003cp\u003ePost-import, creating new policy templates directly on a managed appliance will result in free-standing templates that cannot be shared with other appliances, and only capture data from its source.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot conflicts when adding backup/recovery appliances\n\nIf you encounter a conflict when adding a new backup/recovery appliance, resolve\nthe conflict on the appliance that is experiencing the issue.\nFor example, based on the identified conflict you can do the following:\n\n- Rename conflicting backup templates on the appliance.\n- Modify a conflicting backup template on the appliance to add the missing policies or remove the extra policies.\n- Modify the attributes in the differing policy (or policies) in the conflicting backup template on the appliance to make the attributes the same.\n- Modify the services or rights associated with the conflicting role identified on the appliance to make the services or rights the same.\n\nImported backup templates, users, and roles that already exist in the\nmanagement console (that have the same name) are addressed as follows:\n\n- **Backup templates**: Templates go through a conflict-resolution process by management console described as follows.\n- **Users**: Users that already exist in management console are ignored and are not imported from the appliance.\n- **Roles**: Roles go through a conflict-resolution process by the management console described as follows.\n\nTemplate ownership\n------------------\n\nImported backup templates---and associated policies---managed by the\nmanagement console can be modified from the management console. After you add\nan appliance to the management console, don't create additional policy\ntemplates in the managed appliance after performing the initial import. If you\ndo create additional policy templates on that same appliance post-import, when\nthe appliance is synchronized with the management console and the non-management\nconsole template is added to management console, the template is considered\nto be a free-standing template. In this case, the template can only be used\nto capture application data from the originating appliance and cannot be shared\nwith other appliances managed by the management console.\n\nInvalid IP address or fully qualified domain name (FQDN) of backup/recovery appliance\n-------------------------------------------------------------------------------------\n\nThe management console displays an error condition if you:\n\n- Enter an invalid IP address or FQDN of the appliance to add to the management console.\n- Attempt to promote the dependent appliance before the primary appliance.\n- Attempt to add an appliance that is already managed by another management console. Backup/recovery appliances can only be managed by a single management console.\n\nIn the following example an invalid IP address has been entered for an appliance\nand the **Import Status** is **Failure**.\n\nIf you encounter an issue with an incorrect IP address or FQDN, check that you\nare entering the correct IP address or appliance hostname. You must enter the\ncorrect information for the appliance to be able to add it as a managed device\nby the management console.\n\nIf the appliance that you are trying to add to the management console is joined\nin sharing mode, the primary appliance must always be added first to the\nmanagement console. The primary appliance is used as the source for importing\nobjects into the management console, and the dependent appliance's shared\nobjects is the same as the primary appliance. Ensure that you add the primary appliance\nfirst, followed by the dependent appliance. This order of adding appliances\nthat are joined in shared mode is very important.\n\nIf the import fails because the appliance is managed by another\nmanagement console, keep in mind that you cannot add the same appliance to\nmultiple management consoles. If it is critical that this appliance be managed\nby a different management console, your solution is to first remove the\nappliance from the original management console and then add it to a different\nmanagement console.\n\nConflict with imported objects from the appliance\n-------------------------------------------------\n\nWhen you add a new appliance to the management console, during the dry-run phase\nof the import process a log appears to outline all import actions and decisions.\nThe log includes a summary of the objects imported and added to the management\nconsole (templates, roles, and users) as well as any areas of conflict in\nbackup templates or roles with the incoming appliance that exist in\nthe management console.\n\nObject conflicts during the import process can occur under the following\nconditions:\n\n- Backup templates of the same name have a different number of policies or defined attributes between the appliance and the management console.\n- Roles of the same name have differences in services or access control level (ACL) rights between the appliance and the management console.\n\nFor example, the log example shown outlines the following:\n\n- Policies are missing from the standard and enterprise templates found in the in-coming appliance and the management console.\n- Specific rights are missing from the basic role found in the in-coming appliance and the management console.\n\nIf you encounter a conflict, resolve the conflict on the appliance as outlined\nin the following table.\n| **Note:** When you encounter a conflict with a backup template, we recommend that you make the necessary changes to the backup template on the appliance."]]