Rules for the Backup Import Utility
Importing follows these rules to resolve conflicts during import:
• If an imported resource does not exist, it is created. The person performing the import is given creator privileges (such as READ|WRITE|EXECUTE for a procedure or READ|WRITE for a folder). If the user is in the admin group and has specified the ‑includeaccess option, the resource owner and privileges are restored as well.
• If a resource is imported to a nonexistent folder, the folder and any parent folders that do not yet exist are created with the importing user being granted READ|WRITE privileges and ownership of the folders.
Note: Auto-creation of missing folders is not supported in the Data Services area.
• If an imported resource already exists, the old version is overwritten (assuming you have the WRITE privilege), except that:
— The owner is not changed. The original owner retains ownership.
— Privileges for users that are not explicitly changed by the import are left intact. For example, if Abe has READ|WRITE and Bob has READ|WRITE, and the import lists Abe as READ but does not mention Bob, Abe’s privileges are updated but Bob’s are left intact.
— If the resource is a folder or data source, its child resources are not removed.
• Physical data sources cannot be partially exported or imported.
• The Administration > Configuration settings are not carried over when you export or import a resource using Studio menu options.
• You must have WRITE privileges on a folder to create a resource in a folder.
• You must have WRITE privileges on a resource to overwrite that resource.
• You cannot import anything that was exported from the Data Services area to a location outside of that area.
• You cannot import anything that was exported from a location outside of the Data Services area into that area.