IBM E16RMLL-I Implementation Guide - Page 497
Merging file spaces
![]() |
View all IBM E16RMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 497 highlights
subsequent backups performed on Atlantic. Below are some details on merging of files. 14.4.1 Merging file spaces You can merge imported client backup, archive, and space-managed files into existing file spaces, and automatically skip duplicate files that may exist in the target file space on the server. Optionally, you can have new file spaces created. Choosing to merge file spaces allows you to restart a cancelled import operation because files that were previously imported can be skipped in the subsequent import operation. The merge option is available when you issue an export server or export node command. When you merge file spaces, the server performs versioning of the imported objects based on the policy bound to the files. An import operation may leave the target file space with more versions than policy permits. Files are versioned to maintain the policy intent for the files, especially when incremental export (using the FROMDate and FROMTime parameters) is used to maintain duplicate client file copies on two or more servers. Here is how the server merges imported files, based on the type of object, when you specify MERGEfilespaces=Yes. Archive objects If an archive object for the imported node having the same TCP/IP address, TCP/IP port, name, insert date, and description is found to already exist on the target server, the imported object is skipped. Otherwise, the archive object is imported. Backup objects If a backup object for the imported node has the same TCP/IP address, TCP/IP port, insert date, and description as the imported backup object, the imported object is skipped. When backup objects are merged into existing file spaces, versioning will be done according to policy just as it occurs when backup objects are sent from the client during a backup operation. To do this: If the imported backup object has a later (more recent) insert date than an active version of an object on the target server with the same node, file space, TCP/IP address, and TCP/IP port, then the imported backup object becomes the new active copy, and the active copy on the target server is made inactive. Tivoli Storage Manager expires this inactive version based on the number of versions that are allowed in the policy. If the imported backup object has an earlier (less recent) insert date than an active copy of an object on the target server with the same node, file space, Chapter 14. Advanced operations 467
![](/manual_guide/products/ibm-e16rmlli-implementation-guide-3588123/497.png)