yu dong dong wrote:
hi all:
how to restore linux client backup files to my windows client ?
not. (period). It's impossible, due to the huge differences in file
system design.
--
Met vriendelijke groeten,
Remco Post, PLCS
Hi,
You can't do that.
But if you install CBMR on your Linux box and on your Windows box then can you
backup Linux files and restore them to Windows file system via the TSM API.
But that's the only way as I know.
Best Regards / Med Vänlig Hälsning
Christian Svensson
Products Specialist
Or, install SAMBA, mount the file share to the Windows server and just copy the
files over. (unless the Linux box is dead).
See Ya'
Howard
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
Of Christian Svensson
Sent: Thursday, July 31, 2008 6:01 AM
That is probably where the event is so far back that it has fallen off the
event history.
Event Record Retention Period: 65 Day(s)
Use query stat to see your current setting.
Additionally, the last thing your client does is send the results to the
server, it is possible that the client
I didn't see it mentioned yet, but there is also TSMtape and the older
adsmtape programs on sourceforge:
http://sourceforge.net/projects/tsmtape
Regards,
Shawn
Shawn Drew
Internet
[EMAIL PROTECTED]
Sent by: ADSM-L@VM.MARIST.EDU
07/30/2008
The excludedb option is the only way to have tdpsqlc backup * diff
ignore the master db, right?
Regards,
Shawn
Shawn Drew
Internet
[EMAIL PROTECTED]
Sent by: ADSM-L@VM.MARIST.EDU
07/30/2008 06:16 PM
Please respond to
ADSM-L@VM.MARIST.EDU
Quoting Shawn Drew [EMAIL PROTECTED]:
I didn't see it mentioned yet, but there is also TSMtape and the older
adsmtape programs on sourceforge:
http://sourceforge.net/projects/tsmtape
What I'm now wondering, has anyone seen any of these
programs/solutions work relyably?
--
Met vriendelijke
Did you try by adding this to the DSM.OPT file?
EXCLUDE \...\master\...\diff*
Del
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 07/31/2008
09:18:24 AM:
[image removed]
Re: TDPSQL update
Shawn Drew
to:
ADSM-L
Clever bugger! Strange that EXCLUDE \...\master\...\* didn't work, but
this variation did.
ADSM-L!
Regards,
Shawn
Shawn Drew
Internet
[EMAIL PROTECTED]
Sent by: ADSM-L@VM.MARIST.EDU
07/31/2008 09:31 AM
Please respond to
ADSM-L@VM.MARIST.EDU
We are in the process of designing our new TSM server. As part of this
we are also going to give it new SAN drive space.
Currently we have 661 Gig in our disk pool and we are upping that to 900
Gig. What our questions is how should we partition that? Our current
pool is in 7 partitions but I
I would break them up in a way that makes sense with the physical disk
layout.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Dollens, Bruce
Sent: Thursday, July 31, 2008 9:16 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] New TSM
I would highly recommend dividing that into two pools. This gives you
more flexibility in number of reclamation, migration, and backup
processes that can be run. The backup and migration can be run
concurrently in newer versions of TSM, however you can only run 1
reclamation process at a time.
That depends more on the number of disks you writing to and the type of
san you are using.
For instance if you are using an SVC or other virtualization solution
your 900 gb may already be striped across more than 30 disks. Then
partitioning may not be necessary.
If you are using a direct connect
Hi
I would stick to 100GB diskpool volumes as many as you require.
Its not necessary to split into different LUNS as the SAN takes care of
itself and it is RAID 5 hopefully.
I have learnt to keep to smaller logical units for every thing in TSM.
Makes for better management and migration etc.
Greetings ADSM-L! I've a port problem today. When we're trying to run
a command schedule in prompted mode, we see this in the activity log:
2008-07-26 23:01ANR8213W
Session open with vmhyper1-toc timed out. (SESSION: 984)
2008-07-26 23:01
Quoting Steve Stackwick [EMAIL PROTECTED]:
Greetings ADSM-L! I've a port problem today. When we're trying to run
a command schedule in prompted mode, we see this in the activity log:
2008-07-26 23:01ANR8213W
Session open with vmhyper1-toc timed out. (SESSION:
I went through a number of different configurations on our Clariion. The
best ended up being to take only 1 LUN from each raid group. As many raid
groups as possible.
My main TSM server has 19 X 200gB raw volumes for its diskpool. Each
volume is from a different raidgroup.
Just try not to use
What I've seen in the past, in general, is that inbound work looking for a
place to store data will bind to a defined TSM volume that is not currently
in use.
Now, knowing that volume name is an internal key within TSM you can prevent
excessive TSM DB lock contention by breaking that storage pool
We had 4 TSM server sharing 4 raid groups in one Clariion.
Although we had plenty of LUNs and many spindles, our problem was that we
were flooding the 2 internal paths of the Clariion.
It really cut into our i/o rates.
Gerald Michalak
IBM
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote
FWIW, in TSM 5.5 you can have multiple reclamation processes per pool.
(Doesn't apply to random disk pools, tho)
On Thu, Jul 31, 2008 at 11:23 AM, Gerald Michalak [EMAIL PROTECTED]wrote:
We had 4 TSM server sharing 4 raid groups in one Clariion.
Although we had plenty of LUNs and many
Steve -
There's no TCPCLIENTPort spec in the client options, so the TSM
server uses the port number which the client chose to use in
establishing itself with the TSM server. See IBM Technote 1083673.
Richard Sims
Tsm server 5.4
Tsm tdp 5.5.0.0
Trying to restore a large db from one sql server to another. I believe
the errors point to the fact that the original db has 2 full text
indexes. I'm trying to use the gui for the restore, I've tried both
specifying placement for the db/log/other file as well
Thanks, Richard, but after reading the Technote I'm still a little
confused. It seems that the port is selected (presumably randomly) at
initial contact right after installation and stored by the server, at
least that's how I'm reading the technote. If so, where does that
configuration live on the
This should work.
Have you tried using the CLI and the /RELOCATEDir=directory option?
For example, restoring from server1 to server2, it would be something like
this:
(The following is all one command.)
TDPSQLC RESTORE db1 full /FROMSQLSERVER=server1 /SQLSERVER=server2
/REPLACE
On Jul 31, 2008, at 17:17 , Steve Stackwick wrote:
Well, it's working now after we poked a hole in the firewall, my real
question is: where is 1757 coming from?
random, the default was unavailable (must have been, otherwise that
would have been selected).
On Thu, Jul 31, 2008 at 10:58 AM,
for STG pools, i create the raid group large enough for 2 LUNs (4TB), and
assign each LUN (2TB) to a different STG pool. then migrate or reclaim the STG
pools separately. extra effort, but well worth the extra performance. rule of
thumb is when the number of spindles doubles performance will
On Thu, Jul 31, 2008 at 11:56 AM, Remco Post [EMAIL PROTECTED] wrote:
On Jul 31, 2008, at 17:17 , Steve Stackwick wrote:
Well, it's working now after we poked a hole in the firewall, my real
question is: where is 1757 coming from?
random, the default was unavailable (must have been,
On Jul 31, 2008, at 11:51 AM, Steve Stackwick wrote:
Thanks, Richard, but after reading the Technote I'm still a little
confused. It seems that the port is selected (presumably randomly) at
initial contact right after installation and stored by the server, at
least that's how I'm reading the
Ah, I'll buy that, esp. since the port is persistent and obviously
stored *somewhere*. Mere mortals are not to know where, though,
apparently. Thanks, Richard!
Steve
On Thu, Jul 31, 2008 at 12:27 PM, Richard Sims [EMAIL PROTECTED] wrote:
On Jul 31, 2008, at 11:51 AM, Steve Stackwick wrote:
Two weeks ago, I had written ...
[...]
FYI, the last ADSM-L Digest I received was of June 5.
In the past, perfect service thru April 2008.
I notice that the daily ADSM-L digests once more arrive at our site,
so far for a total of 5 days, starting with issue #2008-189.
So it seems the ADSM-L
On Jul 31, 2008, at 19:38 , Wolfgang Moeller wrote:
Two weeks ago, I had written ...
[...]
FYI, the last ADSM-L Digest I received was of June 5.
In the past, perfect service thru April 2008.
I notice that the daily ADSM-L digests once more arrive at our site,
so far for a total of 5 days,
Hi All,
I have been asked to move multiple volumes to another storage pool so that I
can change the retention to no limit. I do not want to change all of the
volumes on a node, only select volumes. I know that retention is determined by
the management class and if you change the management
Data on specific volumes...
How do you know what is on those volumes?
Need more information...
Is this copy pool data?
Is it data for a single node and you know what is on it because of
collocation?
Dwight
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
I think you mean volumes on your system, not TSM volumes. Without
running another backup, I don't believe you can change the retention on
specific volumes. If you change the retention policy in the management
class for the node, all of the data will be retained in that way. You
are correct: if
I mean actual tape volumes, not system volumes.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Kelly Lipp
Sent: Thursday, July 31, 2008 2:08 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Change retention policy on specific volumes
I think you
The specific volumes are determined by a SQL query, the tapes are in the
primary tapepool. Multiple nodes are affected.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Dwight Cook
Sent: Thursday, July 31, 2008 2:05 PM
To: ADSM-L@VM.MARIST.EDU
Since data retention is at the data item level, you need to go back to that
to extend set things to no limit.
I had to freeze some past data (only... no future data) so I renamed the
nodes to existingname_xxx(where your xxx can be something like
frozen)
Build a domain such as outlined
You can only change the retention of the management class. You don't
rebind if the files are already bound to the management class you change.
(You don't change retention by volume)
If you can change the retention by the node, then you can move the nodes
to a new domain with the same name
Hi list,
What should be the best approach to upgrade a TSM 5.3 Server running on a Linux
RH4? The Install Guide tells you to perform several actions prior to installing
TSM 5.5, including removing completely TSM 5.3 code.
The same guide however, tells you that if an older version is detected,
Hi,
I have a tsm server on linux and mail server on windows, these two servers
are connected to SAN. At present I am using ba client on windows for
mailserver backup . How to configure storage agent on windows system for lan
free backup for better performance.
Thanks,
MAHENDER.
40 matches
Mail list logo
