Hi,
DB2 backup reads config settings only at start up. Cleaning the config
files after that wont change the running setup untill db2 gets restarted.
Either check time stamp of current config files or restart db2 and see
whats going to happen :) .
Kind regards,
Karel
Op 11 sep. 2013 15:47
Hi all,
We have a Linux TSM Server running TSM for VE 6.4 too and we would like to
backup VM using SAN but there is no specific recommandations on this case.
Whereas under Windows you have to make some modifications using
diskpart.exe utility (auto mount disable, san policy OnlineAll...), nothing
AD restore works with Server 2003 AD and 5.5.x clients (did a DR test just
last week). Not sure if things have changed with later versions, but I can
hardly imagine that. Not to say it ain't so, ofcourse...
Cheers,
Rick
On Thu, Sep 19, 2013 at 6:57 AM, Grigori Solonovitch
In theory, AD gets backed up with System State.
A Microsoft-supported method would probably take a hybrid approach, using
their tool to create the files, and then back the files up to TSM.
http://technet.microsoft.com/en-us/library/cc754472(v=ws.10).aspx
You may also consider using Cristie's
Also, make absolutely sure that the config file you located is the one DB2 is
using.
I had a similar situation on a system that many DBA's had administered one
several years and let's just say they got pretty creative.
In the end the DB2 processes was getting the parameters from another location
We are in a transition of our SAN storage from one EMC box to another.
Since this requires my relocating 18TB of TSM server storage, I thought I
would take this opportunity to revisit FILE devclass vs DISK, which we are
using now.
I have been reading through the Linux Server Admin Guide on the
I always use this link for client code and server updates. I find it convenient
because they put the updated-date next to the versions,
http://www-01.ibm.com/support/docview.wss?rs=663uid=swg21239415
Regards,
Shawn
Shawn Drew
-Original Message-
We had the same debate a year or so ago, and ended up making the DISK -
FILE migration for everything except the targets of DIRMC (we figured
pure random access would be better for those).
The only problem was we had naively set REUSEDELAY to be the same as our
tape pools. We are /very/ bursty,
Wanda,
As always, thanks for the education lesson.
And what I HATE about the file devclass, is that you don't get pool
failover. If the pool fills up before you can migrate out, your backups
fail, rather than waiting for a tape from the NEXTSTGPOOL.
Well, that pretty much tells me I don't want
That's the page I remember. I guess I need to bookmark it, because finding
it again is always a challenge.
Thanks,
Nick
On Thu, Sep 19, 2013 at 11:21 AM, Shawn DREW
shawn.d...@us.bnpparibas.comwrote:
I always use this link for client code and server updates. I find it
convenient because they
I am not sure if this is an issue with file device class, but I define the max
capacity as 2 GB and started backups direct to file device class. Many of my
clients has excessive media wait the next morning report. After that I move
them back to a small disk device class that migrate to a file
Sounds like collocation is turned on.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee,
Gary
Sent: Thursday, September 19, 2013 1:05 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] strange tape handling
Tsm server 6.2.4 on RHEL
Yes, permission needs to be considered for v6 resource access, although you
don't necessarily need to reassign ownership.
http://www-01.ibm.com/support/docview.wss?uid=swg21394164
Regards,
Shawn
Shawn Drew
-Original Message-
From:
For file devclass, I generally don't worry about maximum volumes because I
don't set the volumes up as scratch, I predefine them.
Just something else that can cause issues for the customer, and reports of
other people seeing the coming and going of scratch file volumes causing
fragmentation in
Just to add a few more thoughts to the discussion...
If you ever have to restore your TSM database, you will need to audit all of
your DISK volumes. If you set reusedelay appropriately, you can avoid having
to audit FILE volumes. Yes, this requires a bit more space, because you'll
have
I go directly to FTP / service.boulder.com then storage and then
tivoli-storage-management - From there pick maintenance or patches
and so-on. Just keep drilling down to what you are looking for. They have
clients going back to v3.7
On Thu, Sep 19, 2013 at 12:08 PM, Nick Laflamme
Our TSM v5 servers all run as root. After the conversion to v6 they will
be running as a non-root account which is the tsm/db2 instance owner.
Our disk pools are all raw logical volumes. Do we need to change
ownership of the raw volumes to the new instance owner so dsmserv can
access the LV's?
Tsm server 6.2.4 on RHEL 6
Tape storage pool on ts1120 tapes, collocation set to group.
Node libprint does not belong to any group. Its data is now on two volumes.
First volume has estimated capacity 1 tB.
It is 1.4% full.
This morning, tsm was migrating its data from disk pool to tape. It
IBM has changed their support portal again; they now are trying to restrict
customers only to software downloads to which they're entitled.
I can't figure out how to get them to offer me client code, and I can't
figure out how to get them to offer me 6.2 code.
Does anyone have any suggestions
What is the access setting on the tape, is it READWRITE? And is status FULL or
FILLING?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee,
Gary
Sent: Thursday, September 19, 2013 2:05 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] strange
A few were readonly. However, that did not explain all of them by a long way.
Others are filling.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Thursday, September 19, 2013 4:05 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re:
It very much depends on the disk you are putting these on. It is a lot
easier to get bigger cheaper disks to stream data using FILE than to do
lots of small IOPS using DISK.
We were mainly concerned about getting a large amount data to the disk
storage pool and to tape as quickly as possible.
22 matches
Mail list logo
