Differences between structure backup with dependency and with out
Voted best answer
The size of the back-up file with dependencies is obiviously bigger compared to without dependencies.
To simplify the difference i will take the case of control structure back-up:
The objects of a control project under control network belongs to a specific library from object type structure. These objects may have, say for example, log configuration which is attached with specific trend template from library structure.
In the above case if you take the control structure back-up without dependencies, it won't back-up trend template from library structure. Like this it is applicable for all aspects of object(s).
Below are the two screen shots of same object back-up from objecttype structure. One is with dependencies and other is without dependencies. Both are excluded for system extensions during back-up. So missing system exentions will be common in both back-ups.
I hope this helps you to understand.
Back-up without dependencies:
Back-up with dependencies:
If the back-up is taken with dependencies, same can be imported in new system as well. Since it contains all required objects/aspects to complete the import.
The back-up without dependencies may not be imported on new system, because the new system may not be having the all required objects/aspects of other structures to successfully import back-up.
If you make a backup "with dependencies" than all that your objects need is in the backup, but it may be quite big in this case. And there is a lot of stuff in your backup that never has been changed. Such a backup is useful if you restore on na empty system. If you only intend to save your data from time to time, e.g. your graphic displays from the functional structure, it is better to save without dependencies because your backup is significant smaller.