Hi Gordon!
The way to prevent the installation from doing a upgradedb is to hide the
database during installation. You can easily do this by renaming the
dsmserv.dsk file before upgrading.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: Gordon Woodward [ma
"Slag, Jerry B." wrote
>>TSM currently at 5.2.2.2 on z/OS 1.4
>>The volume history file shows a backupset on tape 101334 but a query or
>>delete for backupset returns nothing.
>>How do I get rid of the entry in the volume history?
Try
del volh tod=today vol=101334 type=backupset force=yes
Hi,
I'm having a really strange problem with my copypool. It doesn't show some
of the columns
anymore when running the "q stgp" command.
Yesterday, I removed the complete copy1 storage pool and associated
volumes after
which I have created a new copy1 pool, but the problem stays.
Is there someon
Geert,
No, what you see is correct. Copy pools do not show the columns.
Migration and next pool do not have any meaning in the world of copy pools.
... Enjoy. ... Jack
-Original Message-
From: Geert De Pecker [mailto:[EMAIL PROTECTED]
Sent: Friday, August 06, 2004 4:48 AM
Thank you. That command worked. None of my doc shows the volume,
type=backupset or the force as valid parms. I will add this to my notes.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
John Naylor
Sent: Friday, August 06, 2004 3:50 AM
To: [EMAIL PROTEC
>I'm having a really strange problem with my copypool. It doesn't show some of
>the columns anymore when running the "q stgp" command.
>
>Yesterday, I removed the complete copy1 storage pool and associated volumes
>after which I have created a new copy1 pool, but the problem stays.
>
>Is there some
On Fri, 6 Aug 2004 16:22:17 +1000
Steve Harris <[EMAIL PROTECTED]> wrote:
> Hi all
>
> I've been switching from perl to the ruby programming language for my
> scripting as ruby is nicer in many ways. In order to use this with
> TSM I have ported Owen Crow's Adsm.pm perl module. Some of you might
On Thu, 5 Aug 2004 17:08:34 -0700
rh <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I saw somewhere in the list that IBM recommends two
> 3590 FC drives per HBA. Is this published somewhere or
> just "word of mouth"? If there is a planning document
> that discusses this I would be interested in the link.
>
It gets even worse -- a 6228 HBA can eat the entire available bandwidth
of a PCI bus (per IBM's doc) so each card should be on a separate PCI
bus with very little else on the bus. There are only 3 PCI buses in the
I/O drawers used by most of the 6000s currently installed. And, like
Remco said -- do
Well,
I recreated JFS2 with parameters:
[Entry Fields]
File system name/vol1
NEW mount point[/vol1]
SIZE of file system
Unit Size
...
>I have got the same message:
>File size for /vol1/vol1.dsm must be less than 68,589,453,312 bytes
...
Your postings on this problem did not include your Unix Resource Limit
values for the process involved in the operation, which may be your
artificial limiter. Those working in a Unix envirom
Have a 2000 server that is up, we cant login into it
all accounts say that they do not have login local rights, even local administrator
how can one restore the system state with tsm in a standalone mode
Tim Brown
Systems Specialist
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Tim Brown
>Have a 2000 server that is up, we cant login into it
>all accounts say that they do not have login local rights,
>even local administrator
>
>how can one restore the system state with tsm in a standalone mode
Page 85
I recreated filesystem as JFS2 and dfmfmt still show me that message but
"define volume" from dsmadmc worked properly (oops). There is some
difference between them, but it worked eventually for me. Hope my
experience helps the other.
Yuriy.
-Original Message-
From: ADSM: Dist Stor Manager
Sorry, just realized my mistake.
You're going to have to restore the entire machine. Install the OS and
the TSM client, and restore all files, including the system files. Be
sure to pick a point in time when you know the machine could be logged
into.
--
Mark Stapleton
>-Original Message---
Or, you could check this out.
http://www.winnetmag.com/Article/ArticleID/15917/15917.html
[EMAIL PROTECTED]
"Stapleton, Mark" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
08/06/2004 12:34 PM
Please respond to
"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To
[EMA
Hi all,
I have a question related to identifying the tape or volume number that a file (or set
of files) resides on. If I had to, for example, restore a file from 08/01 called
/home/test.file, I would identify the volume # that file is on by doing the following:
>From the TSM command line:
tsm
==> In article <[EMAIL PROTECTED]>, "Levinson, Donald A." <[EMAIL PROTECTED]> writes:
> Can anyone tell me how they defined their sequential FILE devclass and how
> the underlying hardware is setup? It seems like the best way to do this is
> to have multiple physical disks and spread the TSM volum
Can you try running the restore command with "preview=yes"? That **should**
give you an idea of what volumes the system will request, I believe.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Chris Hund
Sent: Friday, August 06, 2004 12:29 PM
To: [EM
Our DR system is Windows 2003, and we must test with TSM 4.2.3.1. We cannot
seem to get TSM to see the Library, it sees the drives OK.
All is SCSI.
We installed the drivers from IBM we though had the Library in it, but it
was for the Ultrium LTO Tape drives instead of the Library (insert grumble
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Mike Bantz
>Can you try running the restore command with "preview=yes"?
>That **should**
>give you an idea of what volumes the system will request, I believe.
That would be nice...if "preview" were a valid option for data resto
I don't believe there is a PREVIEW=YES for the client restore command.
Unless the access of the tape the file was on is UNAVAILABLE or DESTROYED it
should have requested the mount. Did you query the server activity log for
around the time you did the restore to see if there were any indications on
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Coats, Jack
>Our DR system is Windows 2003, and we must test with TSM
>4.2.3.1. We cannot
>seem to get TSM to see the Library, it sees the drives OK.
>All is SCSI.
TSM 4.X is not supported on Windows 2003. Hence (I suspect), y
Howdy TSM folks,
Something got me wondering when deleting filespace for a node. After you
enter the command for deleting filespace(s) and when you do " q pro" it
will display the number of objects deleted. My question is how do you
calculate how many objects will be deleted? This # does't matc
Oops, we figured it out. ... I hate when I hear that great poping sound when
I pull my head out!
25 matches
Mail list logo
