1) I have backups from many servers on primary DISK storage pool permanently;
2) I want to move approximately half of nodes to one FILE storage pool;
3) I want to move all remaining nodes to another FILE storage pool;
4) I want to remove empty DISK storage pool (both the FILE storage pools will
be used permanently instead of DISK pool).
Grigori G. Solonovitch
Senior Technical Architect
Information Technology Bank of Kuwait and Middle East http://www.bkme.com
Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: G.Solonovitch AT bkme
DOT com
Please consider the environment before printing this Email
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tchuise, Bertaut
Sent: Monday, August 10, 2009 4:33 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Move node data from DISK primary storage pool to FILE
storage pool
Grigori, you are right about the move data operation working only with
volumes and not nodes. You stated earlier that migration was not going
to work since you wanted to deal with a few nodes data only; are you
going to run move data on the sequential copy pool for the primary data
currently hosted on the DISK? Is your primary data on DISK eventually
sent to a primary sequential pool or you just keep in on DISK?
BERTAUT TCHUISE
Storage Support Administrator
Legg Mason Technology Services
*410-580-7032
BTchuise AT leggmason DOT com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Grigori Solonovitch
Sent: Monday, August 10, 2009 8:56 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Move node data from DISK primary storage pool to
FILE storage pool
Hello Bertaut,
FILE storage pool is a primary storage pool, not a copy storage pool.
MOVE DATA is working with volumes, not with nodes (it is not suitable at
all for my case).
MOVE NODEDATA requires both sequential storage pools: source and target.
It just gives an error about DISK storage pool. RECONSTRUCT=No is a
default option.
I have decided to move all nodes to FILE storage pool by MOVE DATA, and
then move selective nodes to another FILE storage pool by MOVE NODEDATA.
I hope it will work, but I need to find enough disk space.
Kindest regards,
Grigori G. Solonovitch
Senior Technical Architect
Information Technology Bank of Kuwait and Middle East
http://www.bkme.com
Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail:
G.Solonovitch AT bkme DOT com
Please consider the environment before printing this Email
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tchuise, Bertaut
Sent: Monday, August 10, 2009 3:42 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Move node data from DISK primary storage pool to
FILE storage pool
Grigori,
Regarding the points you made below:
>>> It is impossible to use MOVE DATA, because it is working with volume
level and each DISK volume contains data of many nodes <<< You won't be
able to move data if you are trying to move data from any primary
storage storage pool to a secondary storage pool.
>>> it is impossible to use MOVE NODEDATA, because it is not working
with DISK storage pools <<<
You are correct if you are trying to use aggregrate reconstruction on
the DISK storage pools.
>>> it looks that it is impossible to use EXPORT NODEDATA / IMPORT
NODEDATA, because node will be imported into the same storage pool <<<
The export/import node commands involve using a source and target TSM
servers. I doubt that is the objective you are trying to achieve in this
situation.
Is your FILE storage pool a copy storage pool? If so, you wouldn't be
able to move the data from the primary DISK pool to the copy FILE pool.
Good luck.
BERTAUT TCHUISE
Storage Support Administrator
Legg Mason Technology Services
*410-580-7032
BTchuise AT leggmason DOT com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Grigori Solonovitch
Sent: Sunday, August 09, 2009 5:55 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Move node data from DISK primary storage pool to FILE
storage pool
Dear TSMAdmins,
We have TSM 5.5.3.0 under AIX 5.3-09-02.
Suddenly I have faced problem moving node data from DISK primary storage
pool to FILE storage pool on the same server:
1) it is impossible to use MOVE DATA, because it is working with
volume level and each DISK volume contains data of many nodes;
2) it is impossible to use MOVE NODEDATA, because it is not working
with DISK storage pools;
3) it looks that it is impossible to use EXPORT NODEDATA / IMPORT
NODEDATA, because node will be imported into the same storage pool (at
least I do not know how to do this).
How can I move node data from DISK to FILE storage pool?
Kindest regards,
Grigori G. Solonovitch
Senior Technical Architect
Information Technology Bank of Kuwait and Middle East
http://www.bkme.com
Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail:
G.Solonovitch AT bkme DOT com<mailto:G.Solonovitch AT bkme DOT com>
Please consider the environment before printing this Email
Please consider the environment before printing this Email.
________________________________
"This email message and any attachments transmitted with it may contain
confidential and proprietary information, intended only for the named
recipient(s). If you have received this message in error, or if you are
not the named recipient(s), please delete this email after notifying the
sender immediately. BKME cannot guarantee the integrity of this
communication and accepts no liability for any damage caused by this
email or its attachments due to viruses, any other defects, interception
or unauthorized modification. The information, views, opinions and
comments of this message are those of the individual and not necessarily
endorsed by BKME."
IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security
numbers, account numbers, or personal identification numbers. Delivery,
and or timely delivery of Internet mail is not guaranteed. Legg Mason
therefore recommends that you do not send time sensitive or
action-oriented messages to us via electronic mail.
This message is intended for the addressee only and may contain
privileged or confidential information. Unless you are the intended
recipient, you may not use, copy or disclose to anyone any information
contained in this message. If you have received this message in error,
please notify the author by replying to this message and then kindly
delete the message. Thank you.
"This email message and any attachments transmitted with it may contain
confidential and proprietary information, intended only for the named
recipient(s). If you have received this message in error, or if you are
not the named recipient(s), please delete this email after notifying the
sender immediately. BKME cannot guarantee the integrity of this
communication and accepts no liability for any damage caused by this
email or its attachments due to viruses, any other defects, interception
or unauthorized modification. The information, views, opinions and
comments of this message are those of the individual and not necessarily
endorsed by BKME."
IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security numbers,
account numbers, or personal identification numbers. Delivery, and or timely
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends
that you do not send time sensitive
or action-oriented messages to us via electronic mail.
This message is intended for the addressee only and may contain privileged or
confidential information. Unless you are the intended recipient, you may not
use, copy or disclose to anyone any information contained in this message. If
you have received this message in error, please notify the author by replying
to this message and then kindly delete the message. Thank you.
"This email message and any attachments transmitted with it may contain
confidential and proprietary information, intended only for the named
recipient(s). If you have received this message in error, or if you are not the
named recipient(s), please delete this email after notifying the sender
immediately. BKME cannot guarantee the integrity of this communication and
accepts no liability for any damage caused by this email or its attachments due
to viruses, any other defects, interception or unauthorized modification. The
information, views, opinions and comments of this message are those of the
individual and not necessarily endorsed by BKME."
|
