ADSM-L

Re: [ADSM-L] Directory-Container Storage Pools - Export/Import

2016-03-23 16:29:04
Subject: Re: [ADSM-L] Directory-Container Storage Pools - Export/Import
From: David Ehresman <david.ehresman AT LOUISVILLE DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 23 Mar 2016 20:27:28 +0000
If your v6 tsm is a different server than your v7 tsm, then you only need to do 
step 1 of the procedure below.  It is only if you are trying to get the data 
back to the original server that you have to go to a second server then back 
again.

David

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Maness, Eric
Sent: Wednesday, March 23, 2016 4:09 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Directory-Container Storage Pools - Export/Import

Thanks David.  I think the steps you mention follow what is in the 
directory-container storage pool FAQ:


Q6. How can I store existing data to a directory-container pool by using 
replication? Are there other techniques?
Firstly, a conversion utility is currently being considered by product 
management. Currently, the only methods that you can use to store data in a 
directory-container pool are:
*         Client store operations such as backup, archive, and space management.
*         Node Replication from another server.
You can use node replication to move data from one storage pool to another on 
the same machine, but you must replicate the data to another server to do this. 
For example, if you have a node, N1, on a server, S1, in a storage pool, P1, 
and you want to move it to a directory-container storage pool, P2, you must 
complete the following steps:
1.      Replicate all the data for node N1 to server S2.
2.      Rename node N1 to N1.X.
3.      Replicate the node to server S1 from server S2.
4.      Change the management class and the copy group destinations, or both, 
in the policy on server S1 to ensure that the data from server S2 is stored the 
directory-container storage pool, P2.
When all the data from node N1 is stored on server S1, you can delete the file 
spaces for node N1 on servers S1 and S2, remove node N1.X from server S1, and 
remove node N1 from server S2. To switch replication directions, you must use 
the REMOVE REPLNODE command after the first replication (from S1 to S2) on both 
servers and then re-enable replication on server S2 to server S1. You cannot 
use the node replication on a single file space within a node. The entire node 
must be replicated.





This process seems cumbersome.  Would be much easier to start backing up node 
again on new 7.1.5.0 server and age node out on 6.3.5.100 server.  I hope they 
fix the export/import in the near future.





Eric Maness

OA | ITSD | SDC

Work: (573) 526-0578

eric.maness AT oa.mo DOT gov





-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Nixon, Charles D. (David)
Sent: Wednesday, March 23, 2016 2:51 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Directory-Container Storage Pools - Export/Import



Since you are trying to "export node from version 6.3.5.100 and import into 
version 7.1.5.0," you should be able to replicate the node instead of exporting 
it to get your data migrated.



Copy the policy domain from source to destination, and then in the destination, 
point the target to the container.





---------------------------------------------------

David Nixon

Storage Engineer II

Technology Services Group

Carilion Clinic

451 Kimball Ave.

Roanoke, VA 24015

Phone: 540-224-3903

cdnixon AT carilionclinic DOT org<mailto:cdnixon AT carilionclinic DOT org>



Our mission: Improve the health of the communities we serve.







________________________________________

From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] on behalf of 
Maness, Eric [Eric.Maness AT OA.MO DOT GOV]

Sent: Wednesday, March 23, 2016 3:44 PM

To: ADSM-L AT VM.MARIST DOT EDU<mailto:ADSM-L AT VM.MARIST DOT EDU>

Subject: [ADSM-L] Directory-Container Storage Pools - Export/Import



Is the following still true for directory-container storage pools for version 
7.1.5.0:



Q4. Can I use existing commands or utilities to move data out of a 
directory-container storage pool?

No, but these, or similar, capabilities are being considered by IBM Spectrum 
Protect product management for the future roadmap. Traditional move and copy 
features are not supported for directory-container storage pools. You cannot 
use the following commands with directory-container storage pools:

*         BACKUP STGPOOL

*         EXPORT/IMPORT

*         GENERATE BACKUPSET

*         MOVE DATA

*         MOVE NODEDATA

*         MIGRATE STGPOOL

I'm trying to export node from version 6.3.5.100 and import into version 
7.1.5.0.



Eric Maness

OA | ITSD | SDC

Work: (573) 526-0578

eric.maness AT oa.mo DOT gov<mailto:eric.maness AT oa.mo DOT 
gov<mailto:eric.maness AT oa.mo DOT gov%3cmailto:eric.maness AT oa.mo DOT gov>>



________________________________



Notice: The information and attachment(s) contained in this communication are 
intended for the addressee only, and may be confidential and/or legally 
privileged. If you have received this communication in error, please contact 
the sender immediately, and delete this communication from any computer or 
network system. Any interception, review, printing, copying, re-transmission, 
dissemination, or other use of, or taking of any action upon this information 
by persons or entities other than the intended recipient is strictly prohibited 
by law and may subject them to criminal or civil liability. Carilion Clinic 
shall not be liable for the improper and/or incomplete transmission of the 
information contained in this communication or for any delay in its receipt.