Small Sites

2004-05-19 Thread Douglas Currell
Has anyone deployed TSM in a very small site? When I say a small site I mean something 
like this:


   4 or 5 workstations  2 or 3 servers
   very limited bandwidth available from WAN - assume 56k (yes)
   NO local administration
   NO budget for tape library
   TSM sharing a physical server with Domino, platform is Windows
   150 MB per user per week storage growth
   1 X 73 GB hd for use as storage pool/file device
   100Mb LAN
   access to large remote TSM servers
   12 hour backup window, assumption that WAN link is at 56k (yes!)
   backup of local workstations preferred but not required
   TSM clients would mostly be Windows XP/2003 but could include Linux, in particular, 
and just about anything else.
   weekly full backup required to remote TSM server


Would this be a candidate for remote NAS backup? I am looking at TSM because it allows 
for policy implentation, can accommodate clients on just about all platforms and also 
because it allows backup to disk. This is not to say that other backup/restore 
products could be used - Retrospect might be usable too..

To me, this is an interesting exercise. Please share your thoughts..Thank you





-
Post your free ad now! Yahoo! Canada Personals


AW: Small Sites

2004-05-19 Thread Salak Juraj
Hi,

as far as I understand you,
you only want to backup this site into an existing large TSM server
elsewhere.
I not, GOTO (2)

A small TSM Server per site, if necessarey at all,
is not practicable without both local administration and tape library.

I have few site like this (with the exception of Domino)
and the answer is : 
first: it works, assuming that amount of files changed daily
is significantly  less than WAN capacity in the backup window.
Second, read first again.
Third, compression and subfile backup can help much, but it depends
on data and you configuration.

Probaly backup of system object will not be practicable,
but backup of data files probably yes.

You will have to tune include/exclude options down,
you will have to tune network parameters,
compression/compressalways parameters (per directory, file type..)
subfilebackup
you will want to use  journal service.

FORGET full backup weekly, no one needs it. Read TSM concepts,
browse in this user forum.
What you/your users need is RESTORE and ONLY RESTORE,
no one in the world ever needed backup, not to say a full backup.

Consider you restore requirements,
if full restore is an issue, it will take long time through the WAN.
Maybe is backup set generation and physical transfer of the backup set along
with
technician and restore on-site required and/or practicable.

For backup of Domine, think about replication. This might cause less
bandwidth consumption
comparing to TSM backup.

(2) if you want an backup server (tsm or not) in each of this sites,
you have apparently got a problem with both budget and administration,
in fact.

this are only couple of points from more to be considered

regards
Juraj


-Ursprüngliche Nachricht-
Von: Douglas Currell [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 19. Mai 2004 09:19
An: [EMAIL PROTECTED]
Betreff: Small Sites


Has anyone deployed TSM in a very small site? When I say a small site I mean
something like this:


   4 or 5 workstations  2 or 3 servers
   very limited bandwidth available from WAN - assume 56k (yes)
   NO local administration
   NO budget for tape library
   TSM sharing a physical server with Domino, platform is Windows
   150 MB per user per week storage growth
   1 X 73 GB hd for use as storage pool/file device
   100Mb LAN
   access to large remote TSM servers
   12 hour backup window, assumption that WAN link is at 56k (yes!)
   backup of local workstations preferred but not required
   TSM clients would mostly be Windows XP/2003 but could include Linux, in
particular, and just about anything else.
   weekly full backup required to remote TSM server


Would this be a candidate for remote NAS backup? I am looking at TSM because
it allows for policy implentation, can accommodate clients on just about all
platforms and also because it allows backup to disk. This is not to say that
other backup/restore products could be used - Retrospect might be usable
too..

To me, this is an interesting exercise. Please share your thoughts..Thank
you





-
Post your free ad now! Yahoo! Canada Personals


Re: AW: Small Sites

2004-05-19 Thread Douglas Currell
Juraj,

I should state that my organization currently has a couple 100-user sites using local 
Windows TSM Servers with 2-drive tape libraries and they are administered remotely. 
Physical visits to the sites are no more than twice per year.

Full backup of the Domino server, is required, by Service Level Agreement. If Domino 
is local then there might as well be a local backup. As far as other TSM clients go, 
it's incrementals forever.

I



My suspicion is that a small site will consist of:


   portable, dockable XP laptops that will be backed up by schedule, using a client 
option set.
   Windows server
   Domino Server.


Salak Juraj [EMAIL PROTECTED] wrote:
Hi,

as far as I understand you,
you only want to backup this site into an existing large TSM server
elsewhere.
I not, GOTO (2)

A small TSM Server per site, if necessarey at all,
is not practicable without both local administration and tape library.

I have few site like this (with the exception of Domino)
and the answer is :
first: it works, assuming that amount of files changed daily
is significantly less than WAN capacity in the backup window.
Second, read first again.
Third, compression and subfile backup can help much, but it depends
on data and you configuration.

Probaly backup of system object will not be practicable,
but backup of data files probably yes.

You will have to tune include/exclude options down,
you will have to tune network parameters,
compression/compressalways parameters (per directory, file type..)
subfilebackup
you will want to use journal service.

FORGET full backup weekly, no one needs it. Read TSM concepts,
browse in this user forum.
What you/your users need is RESTORE and ONLY RESTORE,
no one in the world ever needed backup, not to say a full backup.

Consider you restore requirements,
if full restore is an issue, it will take long time through the WAN.
Maybe is backup set generation and physical transfer of the backup set along
with
technician and restore on-site required and/or practicable.

For backup of Domine, think about replication. This might cause less
bandwidth consumption
comparing to TSM backup.

(2) if you want an backup server (tsm or not) in each of this sites,
you have apparently got a problem with both budget and administration,
in fact.

this are only couple of points from more to be considered

regards
Juraj


-Urspr|ngliche Nachricht-
Von: Douglas Currell [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 19. Mai 2004 09:19
An: [EMAIL PROTECTED]
Betreff: Small Sites


Has anyone deployed TSM in a very small site? When I say a small site I mean
something like this:


4 or 5 workstations  2 or 3 servers
very limited bandwidth available from WAN - assume 56k (yes)
NO local administration
NO budget for tape library
TSM sharing a physical server with Domino, platform is Windows
150 MB per user per week storage growth
1 X 73 GB hd for use as storage pool/file device
100Mb LAN
access to large remote TSM servers
12 hour backup window, assumption that WAN link is at 56k (yes!)
backup of local workstations preferred but not required
TSM clients would mostly be Windows XP/2003 but could include Linux, in
particular, and just about anything else.
weekly full backup required to remote TSM server


Would this be a candidate for remote NAS backup? I am looking at TSM because
it allows for policy implentation, can accommodate clients on just about all
platforms and also because it allows backup to disk. This is not to say that
other backup/restore products could be used - Retrospect might be usable
too..

To me, this is an interesting exercise. Please share your thoughts..Thank
you





-
Post your free ad now! Yahoo! Canada Personals



-
Post your free ad now! Yahoo! Canada Personals


Reconcile Volumes fails

2004-05-19 Thread Christoph Pilgram
Hi all,

On my two TSM-servers (AIX 5.1, TSM 5.1.7.3) we use server-to-server virtual
volumes for the copy_pools.
Since some time when the daily reconcile-volumes runs I get the following
error :

05/18/04 15:57:49 ANRD admserv.c(2337): ThreadId72 Unable to get
volume attributes.
05/18/04 15:57:49 ANR4343W RECONCILE VOLUMES process terminated - internal
server error detected.
05/18/04 15:57:49 ANR4343W RECONCILE VOLUMES process terminated - internal
server error detected.
05/18/04 15:57:49 ANR0985I Process 467 for RECONCILE VOLUMES (REPAIR)
running in the BACKGROUND completed with completion state FAILURE at
15:57:49.

How can I get rid of this error without making an complete auditdb (50 GB).

Thanks for any help.

Chris


Re: moved file on Netware ?

2004-05-19 Thread Richard Sims
We have a question on an issue that came on a Netware box, that a user moved
some of directory tree from the original backup tree to another tree. Then we
had a restore request for the original tree which was moved. So we could not
find any files to restore. We had the default backup copy group set to version
exist 2, version delete 1, retain extra 30, and retain only 365.  So why was
there not any inactive files to restore for the original tree?  Need help in an
explanation of what happen.

Crucial information missing from the posting is relative timings and details on
how the restoral was attempted...  It's possible that the user change happened
so long ago that all versions evaporated.  If you have multiple management
classes, that client could have been using one with shorter retentions.  It's
unlikely, but not impossible, that the client used the dsmc Expire command to
eliminate the old stuff.

Related to retention is how the restoral was attempted.  If, for some reason,
the directories had a shorter retention than the files, attempting to drill down
the directory tree structure via the GUI may get nadda.
As the manuals and historic postings recommend, use the command line as the
authoritative method of checking: 'dsmc q backup -inactive -subdir=yes ...'.

Thanks but there was no excludes on this box at all.

There don't have to be, for Excludes to be in effect, as it's possible for them
to be in server-side Cloptsets.  Always do 'dsmc q inclexcl' to fully check.

All this may not fully resolve the mystery.  Per auditor requirements, there
*should* be client backup logs going way back which could be reviewed to see
what the scoop is.  And, given what happened, it would be healthy to review
current backups to see what is going on now, to prevent future repeats of this
scene.

   Richard Sims


Re: TSM on Tru64 and TruCluster

2004-05-19 Thread Amos Hagay
TSM Not supported TruCluster,

I manage to Install it, with the regular concept of a cluster,

I create for each cluster member a node e.g. NODE-A NODE-B

Each of them was running the dsmc sched ,

But in each dsm.opt file I create another stanza server_b which points to the virtual 
node, I had some problems with the passwords, but in the schedule I run dsmc incr 
-server=server_b -passw=VIRTUAL NODE PASSWORD,

AH

-Original Message-
From: David Henden [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 19, 2004 12:58 AM
To: [EMAIL PROTECTED]
Subject: TSM on Tru64 and TruCluster

Has anyone or is anyone running the TSM client on Tru64 with TruCluster?

I am seeing frequent segfaults and IBM support says that TSM is not
supported
when running TruCluster.

-David

--
David Hendn
 Exist AB, Sweden
+46-(0)70-3992759



MS SQL question

2004-05-19 Thread Kevin Lipscomb
If we do a full database backup on sql server, then a log backup hourly,
would we need to do a differential backup and why?



Kevin M. Lipscomb/Michael Lovern
Dan River Inc.
Systems Engineering


Re: TDP for Informix expiring backup files

2004-05-19 Thread Gary Oborn
Thanks for replying.  When I attempt to query the backup it refuses to show
anything.  Can you tell me if I'm on the right track?

[root:prod] / dsmc
Tivoli Storage Manager
Command Line Backup/Archive Client Interface - Version 5, Release 1, Level
5.0
(C) Copyright IBM Corporation 1990, 2002 All Rights Reserved.

tsm q filespace -fromnode=raven_ifmx
Node Name: RAVEN
Session established with server EAGLE: AIX-RS/6000
  Server Version 5, Release 1, Level 5.0
  Data compression forced on by the server
  Server date/time: 05/19/04   10:18:52  Last access: 05/19/04   10:18:28

Num Last Incr Date  TypeFile Space Name
--- --  ---
  1   00/00/00   00:00:00   API:R   /mhs_ds1n
  2   00/00/00   00:00:00   API:R   /mhs_ds2
tsm q backup -fromnode=raven_ifmx *
ANS1084E No files have previously been backed up for '*'
tsm

Gary Oborn






  Bill Boyer
  [EMAIL PROTECTED]To:   [EMAIL PROTECTED]
  ON.NET  cc:
  Sent by: ADSM:  Subject:  Re: TDP for Informix expiring 
backup files
  Dist Stor
  Manager
  [EMAIL PROTECTED]
  .EDU


  05/19/04 07:51 AM
  Please respond to
  ADSM: Dist Stor
  Manager






From my (limited) experience in doing TDP Informix, the actual backup
objects for the database are the same names, so your management class
retentions should be handling that. The archive logs are a different
matter.
They are uniquely named with a sequence number. You can remove them from
the
SYSUTILS table and then run the ONOMSYNC utility to syncronize the SYSUTILS
table with TSM, or get a list of the objects by running the B/A client with
the TDP Informix nodename and doing a query backup. Then issue the EXPIRE
command for each object you want to remove.

Bill Boyer
DSS, Inc.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Gary Oborn
Sent: Wednesday, May 19, 2004 10:20 AM
To: [EMAIL PROTECTED]
Subject: TDP for Informix expiring backup files


I have been unable to find out how to get old onbar backup files to expire
from the TSM server.  I am using the 5.1.5 client and
server.  Backups are working fine, but it seems that the amount of data for
my Informix client nodes continually increases and expiration doesn't ever
remove anything.

Does anyone have any pointers to information on configuring management
classes for Informix and for actually expiring the files?

Thanks,

Gary Oborn


Re: TDP for Informix expiring backup files

2004-05-19 Thread Stapleton, Mark
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Gary Oborn
Thanks for replying.  When I attempt to query the backup it refuses to
show
anything.  Can you tell me if I'm on the right track?

[root:prod] / dsmc
Tivoli Storage Manager
Command Line Backup/Archive Client Interface - Version 5, Release 1,
Level
5.0
(C) Copyright IBM Corporation 1990, 2002 All Rights Reserved.

tsm q filespace -fromnode=raven_ifmx
Node Name: RAVEN
Session established with server EAGLE: AIX-RS/6000
  Server Version 5, Release 1, Level 5.0
  Data compression forced on by the server
  Server date/time: 05/19/04   10:18:52  Last access: 05/19/04
10:18:28

Num Last Incr Date  TypeFile Space Name
--- --  ---
  1   00/00/00   00:00:00   API:R   /mhs_ds1n
  2   00/00/00   00:00:00   API:R   /mhs_ds2
tsm q backup -fromnode=raven_ifmx *
ANS1084E No files have previously been backed up for '*'

You can't use the TSM b/a client to make meaningful queries against data
that is backed up with API-based backups (which includes all TDP
agents).

I would suspect you need to use Informix's own utilities to scan for
backups (much like you would use Oracle's RMAN).

--
Mark Stapleton


Re: Data organization on tape storage pool?

2004-05-19 Thread Ben Bullock
Look in the manuals about collocation. It is turned on at the
storagepool level.

Look also in the archives as there are a lot of threads about
pros and cons about using it.

Ben


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Alexander Lazarevich
Sent: Wednesday, May 19, 2004 11:01 AM
To: [EMAIL PROTECTED]
Subject: Data organization on tape storage pool?


Hi TSMers,

TSM 5.1.6.5 on windows 2K server. Library is overland storage neo 4100
with 60 LTO-2 tapes, and 2 X LTO-2 HP drives. Setup the system last
July, works just fine. But I'm a little curious how data is organized on
tape volumes. I don't have a problem with anything, but I'm very curious
what the logic is to how the server decides what data is put on what
volume.

For example, I noticed that data from a single client is on several
different tapes. And as data is put on the tape storage pool, the server
finds the tape which has a volume status of 'filling', and there is only
one such tape, so it dumps data on there regardless of what client that
data belongs to. Also, space reclamations can further jumble up the data
on tapes, so that a client may have data on several different tapes.

My questions is this: is there any way to control the organization of
the data on the tape storage pool. For example, could I force all data
from a single client to be put on a single tape, and if it needed
another tape for data, it would grab a scratch tape only, and avoid
putting data on a tape that has other client data on it. In addition to
that, the server would probably be forced to have x many tapes with a
volume status of 'filling', one for each client that backs up, right?
Space reclamations could work fine, it just deletes the old data, then
moves any data from a tape belonging to that client back onto another
tape belonging to that client.

I suppose in this scenario, there might be a lot of waisted tape space,
because many clients have more data than the 200GB LTO-2 can store, so
each client might have one tape which is only using, in theory, 1% of
capacity.

Anyone have any comments? Should I just leave it alone? Did tivoli study
and come up with the best way to organize the data? Or is this something
that people mess around with to get better performance?

Thanks in advance,

Alex
---   ---
   Alex Lazarevich | Systems Administrator | Imaging Technology Group
Beckman Institute | University of Illinois | www.itg.uiuc.edu
---   ---


Re: TDP for Informix expiring backup files

2004-05-19 Thread Bill Boyer
I always use the -VIRTUALNODENAME= parameter on the DSMC command. I believe
that if you use the -fromnode= the nodename you are currently logged in as
needs to be givin access to the -fromnode's data.

And from Mark's reply, the output of the data just shows the objects, size,
date/time and unless you know exactly what you're looking at, yes it is
meaningless. But this will show you the objects and allow you to EXPIRE them
if you have the BACKDELETE=YES for the node.

So, try 'dsmc -virtualnode=raven_ifmx'. You'll be prompted for a password.

Bill

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Gary Oborn
Sent: Wednesday, May 19, 2004 1:25 PM
To: [EMAIL PROTECTED]
Subject: Re: TDP for Informix expiring backup files


Thanks for replying.  When I attempt to query the backup it refuses to show
anything.  Can you tell me if I'm on the right track?

[root:prod] / dsmc
Tivoli Storage Manager
Command Line Backup/Archive Client Interface - Version 5, Release 1, Level
5.0
(C) Copyright IBM Corporation 1990, 2002 All Rights Reserved.

tsm q filespace -fromnode=raven_ifmx
Node Name: RAVEN
Session established with server EAGLE: AIX-RS/6000
  Server Version 5, Release 1, Level 5.0
  Data compression forced on by the server
  Server date/time: 05/19/04   10:18:52  Last access: 05/19/04   10:18:28

Num Last Incr Date  TypeFile Space Name
--- --  ---
  1   00/00/00   00:00:00   API:R   /mhs_ds1n
  2   00/00/00   00:00:00   API:R   /mhs_ds2
tsm q backup -fromnode=raven_ifmx *
ANS1084E No files have previously been backed up for '*'
tsm

Gary Oborn






  Bill Boyer
  [EMAIL PROTECTED]To:
[EMAIL PROTECTED]
  ON.NET  cc:
  Sent by: ADSM:  Subject:  Re: TDP for
Informix expiring backup files
  Dist Stor
  Manager
  [EMAIL PROTECTED]
  .EDU


  05/19/04 07:51 AM
  Please respond to
  ADSM: Dist Stor
  Manager






From my (limited) experience in doing TDP Informix, the actual backup
objects for the database are the same names, so your management class
retentions should be handling that. The archive logs are a different
matter.
They are uniquely named with a sequence number. You can remove them from
the
SYSUTILS table and then run the ONOMSYNC utility to syncronize the SYSUTILS
table with TSM, or get a list of the objects by running the B/A client with
the TDP Informix nodename and doing a query backup. Then issue the EXPIRE
command for each object you want to remove.

Bill Boyer
DSS, Inc.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Gary Oborn
Sent: Wednesday, May 19, 2004 10:20 AM
To: [EMAIL PROTECTED]
Subject: TDP for Informix expiring backup files


I have been unable to find out how to get old onbar backup files to expire
from the TSM server.  I am using the 5.1.5 client and
server.  Backups are working fine, but it seems that the amount of data for
my Informix client nodes continually increases and expiration doesn't ever
remove anything.

Does anyone have any pointers to information on configuring management
classes for Informix and for actually expiring the files?

Thanks,

Gary Oborn


Re: Using open file support for PST files

2004-05-19 Thread TSM_User
I have completed a lot of OFS tests with the V5.2.2.9 client.  The primary file that I 
used for those tests was an Outlook 2003 PST.  I also ran tests with older versions of 
Outlook PST's.  For all of my tests the file was backed up and could be restored.  I 
did not loose any mail items with my tests.  Of course what happened in my tests may 
not reflect what happens in your production environment.  I believe using OFS is the 
only way you can get a backup of a PST file when a user leaves it open.

There is a utility you can get from Microsoft's web site that lets you run backups of 
the PST, well kind of...  The utility when set up will make a copy of the PST to a 
backup PST every time the user closes Outlook.  As you might imagine that is hardly a 
good solution.

Lastly, remember that in order for OFS to work you have to have a drive that is not 
being backed up with OFS to put the cache directory on.  As a result when backing up 
PST's that are on a local desktop the only way to use OFS is if they also have more 
than one local drive.  The fact that your PST's are on a network share is a plus for 
you in this case.



Bill Boyer [EMAIL PROTECTED] wrote:
I've been searching the archives for how people got around backing up open
PST files and came across a couple messages about using the open file
support in the 5.2 client to back them up while open. Is this a good idea???
Are these backups good? These backups will take place during the night when
nobody SHOULD be using their Outlook, but may not have closed it down. This
is Outlook 2003 so you can't use the registry setting to close them after a
period of inactivity.

Also, this client has the PST files as part of the users home directory on a
fileserver.

Bill Boyer
Experience is a comb that nature gives us after we go bald. - ??

-
Do you Yahoo!?
Yahoo! Domains - Claim yours for only $14.70/year


Re: TDP for Informix expiring backup files

2004-05-19 Thread Stapleton, Mark
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bill Boyer
And from Mark's reply, the output of the data just shows the objects,
size,
date/time and unless you know exactly what you're looking at, yes it is
meaningless. But this will show you the objects and allow you to EXPIRE
them
if you have the BACKDELETE=YES for the node.

So, try 'dsmc -virtualnode=raven_ifmx'. You'll be prompted for a
password.

I don't believe that is correct. Remember, Mr. Oborn asked about data
backed up with TDP for Informix. That data is backed up with API code,
not BA code. The dsmc b/a client cannot access anything about filespaces
or backups, since it doesn't access the relevant information.

From the TSM server, he *could* use QUERY OCCUPANCY on the Informix
filesystems and see how much storage space the Informix data is taking
up on tape and/or disk storage pools, but that's about it. If you run a
QUERY FILESPACE from the server, it will 0 MB of space occupied; this is
because the QUERY FILESPACE command only access data about clients
backed up with the BA code.

Again, I think the only way to access information about what is
available for backups is with the TDP for Informix code (and possibly
Informix itself), and that will only run if Informix is loaded and
running on the console.

Del, do I have that right?

--
Mark Stapleton


Re: restore of systemobjects (windows 2000), new user variables still there ?!

2004-05-19 Thread TSM_User
Was the enviornement variables part of the user or system environment settings.  
The user variables are part of the profile and are in NTUSER.DAT.  This file may not 
have been backed up directly due to being open and locked.  You can determine this by 
looking in the GUI under restore and seeing if it is there.  This is why the restore 
didn't overwrite the one you made changes to.

It is backed up under C:\Adsm.sys as part of the SYSTEM OBJECTS backup for Win2K and 
WinXP.  If you go under C:\ADSM.SYS and find the NTUSER.DAT file there you can copy it 
over the NTUSER.DAT for the ID who's profile you made changes too.  That should revert 
that profile back to the way it looked for the backup.  Of course in order to copy it 
you have to make sure that you aren't signed on with that ID.


TSM [EMAIL PROTECTED] wrote:
hello tsm friends,

environment:

tsm server 5.2.2.3
tsm client 5.2.2.5
windows 2000 server


i thought, that a complete restore of w2k system objects will completely
overwrite and replace existing registry on my w2k server.

what we made was backup of w2k systemobjects last night.
we then create some new user variables over the day for testing.

then we decide to restore our w2k system objects backup from last night to
delete all of our changes.


what we saw was the following:

the new user variables, which were not in our system object backup are
still on the server.

Is this tsm functionality or a bug?

what can we do, to delete new user variables during restore of system
objects?


what went wrong?


any comment will help.

with best regards

stefan savoric

-
Do you Yahoo!?
Yahoo! Domains - Claim yours for only $14.70/year


Re: Restore TSM database

2004-05-19 Thread TSM_User
I'm not sure why you have to pass those parms.  The backup volume should be in your 
volhist file.  All you should have to do is run dsmserv restore db todate=today 
totime=now if that was the last backup you ran.

But... If you really want to perform the restore that when then...

Looks like you are trying to use the dbvol parameter when you should be using the 
volumenames parameter.

The manual states the following:

DSMSERV RESTORE DB--DEVclass--=--device_class_name---

 .-,---.
 V |
--VOLumenames--=--+---volume_name-+-+--
   '-FILE:file_name--'

   .-COMMIT--=--No--.
--++--
   '-COMMIT--=--+-No--+-'
'-Yes-'

DEVclass (Required)
   Specifies the name of the sequential access device class to use. You cannot use a 
device class with a device type of NAS. The device class must be defined in a device 
configuration file. If a device configuration file is not available, you can manually 
create one (see the Administrator's Guide).
VOLumenames (Required)
   Specifies the backup volumes to use to restore the database. Possible values are:
volume_name
   Specifies the names of the volumes. To specify multiple volumes, separate the names 
with commas and without intervening spaces. List the volumes in the order in which 
they were written.
FILE:file_name
   Specifies the name of a file that contains a list of the volumes. Enter the volumes 
in the order in which they were written with each name on a separate line.
COMMIT
   Specifies whether this is the last restore command needed to restore the database. 
This parameter is optional. The default value is NO. Possible values are:
No
   Specifies that you will issue one or more additional DSMSERV RESTORE DB commands.
Yes
   Specifies that this is the last restore command to restore the database.

Abdullah, Md-Zaini B BSP-IMI/42 [EMAIL PROTECTED] wrote:
Hello TSM guru,

Normally, I did a tsm db backup to tape and managed to restore the database.

And also I have done tsm db backup to file devices class onto filesystem eg. /ldb. It 
created the file /ldb/808454.dbb.
But how to restore ?

I tried the following command to restore but not successful.

dsmserv restore db devclass=DISK-TMP dbvol=/ldb/84849157.dbb commit=yes

Anybody, who have experience please help...



This is the devconfig of the current set-up.
#
# cat devconfig
/* Device Configuration */
DEFINE DEVCLASS 3584DEV DEVTYPE=LTO FORMAT=ULTRIUM2 ESTCAPACITY=209715200K 
MOUNTLIMIT=DRIVES MOUNTWAIT=60 MOUNTRETENTION=60 PREFIX=ADSM LIBRARY=3584LIB
DEFINE DEVCLASS DISK-TMP DEVTYPE=FILE FORMAT=DRIVE MAXCAPACITY=3788800K MOUNTLIMIT=1 
DIRECTORY=/ldb SHARED=NO
SET SERVERNAME TSM
DEFINE LIBRARY 3584LIB LIBTYPE=SCSI SERIAL=000139860401 SHARED=NO
DEFINE LIBRARY DISK_LIB LIBTYPE=FILE
DEFINE DRIVE 3584LIB 3584DRV1 ELEMENT=258 ONLINE=Yes SERIAL=9100600016
DEFINE DRIVE DISK_LIB DISK_TMP ONLINE=Yes
/* LIBRARYINVENTORY SCSI 3584LIB A2 1110 101*/
/* LIBRARYINVENTORY SCSI 3584LIB A3 1041 101*/
#

#


Regards,
zaini

-
Do you Yahoo!?
Yahoo! Domains - Claim yours for only $14.70/year


Re: TDP for Informix expiring backup files

2004-05-19 Thread Bill Boyer
Here's a link to a thread just a couple months ago doing the same thing to
list TDP Oracle backup data
http://msgs.adsm.org/cgi-bin/get/adsm0403/541.html. Here's the output of
doing one on my system for a TDP SQLserver node:

tsm q fi
Num Last Incr Date  TypeFile Space Name
--- --  ---
  1   05/19/2004 18:30:08   API:SqlData  DSQL0100\data\0001
  2   05/19/2004 18:30:08   API:SqlData  DSQL0100\meta\
tsm q ba {DSQL0100\data\0001}*
 Size  Backup DateMgmt Class A/I File
   ----- --- 
API 68,812,801  B  03/29/2003 22:00:47DEFAULT A
DSQL0100\data\0001\ACDDataTest\full
API 21,135,361  B  03/29/2003 23:00:20DEFAULT A
DSQL0100\data\0001\ACDDataTest\20030329230020\017F\log
API162,112 KB  05/18/2004 22:00:13DEFAULT A
DSQL0100\data\0001\ACDData\full
API 20,061,185  B  05/18/2004 23:00:14DEFAULT A
DSQL0100\data\0001\ACDData\20040518230022\0184\log
API  2,097,153  B  11/23/2002 22:00:20DEFAULT A
DSQL0100\data\0001\ACDdata\full
API  1,473,537  B  11/23/2002 23:00:25DEFAULT A
DSQL0100\data\0001\ACDdata\20021123230025\01C0\log
API  1,473,537  B  11/24/2002 23:00:21DEFAULT A
DSQL0100\data\0001\ACDdata\20021124230021\01D2\log
API386,688 KB  04/12/2003 22:02:24DEFAULT A
DSQL0100\data\0001\CTAssetCenterTest\full
API 15,024,129  B  04/12/2003 23:00:30DEFAULT A
DSQL0100\data\0001\ctassetcentertest\20030412230029\018e\l
og
API 15,024,129  B  04/13/2003 23:00:26DEFAULT A
DSQL0100\data\0001\ctassetcentertest\20030413230026\01c5\l
og
API 15,024,129  B  04/14/2003 23:00:34DEFAULT A
DSQL0100\data\0001\ctassetcentertest\20030414230034\01d2\l
og
API391,808 KB  01/10/2004 22:01:01DEFAULT A
DSQL0100\data\0001\CTAssetCenter\full
API 15,363,073  B  01/10/2004 23:00:22DEFAULT A
DSQL0100\data\0001\CTAssetCenter\20040110230024\01CF\log
API 15,363,073  B  01/11/2004 23:00:22DEFAULT A
DSQL0100\data\0001\CTAssetCenter\20040111230024\0354\log
API 15,363,073  B  01/12/2004 23:00:24DEFAULT A
DSQL0100\data\0001\CTAssetCenter\20040112230027\0031\log
API  2,097,153  B  05/15/2004 22:01:14DEFAULT A
DSQL0100\data\0001\ClientData\full
API  1,478,657  B  05/15/2004 23:00:25DEFAULT A
DSQL0100\data\0001\ClientData\20040515230032\0032\log


and I know that I've done it on an AIX system to list Informix backup
information. I also have some unix shell scripts from another member of this
list that he uses to expire Informix log backups since they are uniquely
named. The input to the shell script is the output of a QUERY BACKUP for the
TDP nodename.

Bill Boyer
Some days you are the bug, some days you are the windshield. - ??


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Stapleton, Mark
Sent: Wednesday, May 19, 2004 4:55 PM
To: [EMAIL PROTECTED]
Subject: Re: TDP for Informix expiring backup files


From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bill Boyer
And from Mark's reply, the output of the data just shows the objects,
size,
date/time and unless you know exactly what you're looking at, yes it is
meaningless. But this will show you the objects and allow you to EXPIRE
them
if you have the BACKDELETE=YES for the node.

So, try 'dsmc -virtualnode=raven_ifmx'. You'll be prompted for a
password.

I don't believe that is correct. Remember, Mr. Oborn asked about data
backed up with TDP for Informix. That data is backed up with API code,
not BA code. The dsmc b/a client cannot access anything about filespaces
or backups, since it doesn't access the relevant information.

From the TSM server, he *could* use QUERY OCCUPANCY on the Informix
filesystems and see how much storage space the Informix data is taking
up on tape and/or disk storage pools, but that's about it. If you run a
QUERY FILESPACE from the server, it will 0 MB of space occupied; this is
because the QUERY FILESPACE command only access data about clients
backed up with the BA code.

Again, I think the only way to access information about what is
available for backups is with the TDP for Informix code (and possibly
Informix itself), and that will only run if Informix is loaded and
running on the console.

Del, do I have that right?

--
Mark Stapleton


Re: TDP for Informix expiring backup files

2004-05-19 Thread Steve Harris
Mark,

I believe that you can use braces to access information about API backup and archives. 
I do this for DB2 and adsmpipe backups. See the Client guide

eg.
$ /opt/adsmpipe/adsmpipe -c -B -s /test -f test CLOG040511-03
$ dsmc  
IBM Tivoli Storage Manager 
*** Fixtest, Please see README file for more information *** 
Command Line Backup/Archive Client Interface - Version 5, Release 2, Level 0.4 
(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.

Node Name: HBCIS-IPS-RBW1
Session established with server QHADSM2: AIX-RS/6000
  Server Version 5, Release 2, Level 2.1
  Server date/time: 20-05-2004 09:11:51  Last access: 20-05-2004 09:11:32

tsm q backup {/test}/ -subdir=y
 Size  Backup DateMgmt Class A/I File
   ----- --- 
API  1,000,000  B  20-05-2004 09:11:32DEFAULT A  /test//test
tsm 

Steve Harris
AIX and TSM Admin
Queensland Health
Brisbane Australia



 [EMAIL PROTECTED] 20/05/2004 6:55:10 
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bill Boyer
And from Mark's reply, the output of the data just shows the objects,
size,
date/time and unless you know exactly what you're looking at, yes it is
meaningless. But this will show you the objects and allow you to EXPIRE
them
if you have the BACKDELETE=YES for the node.

So, try 'dsmc -virtualnode=raven_ifmx'. You'll be prompted for a
password.

I don't believe that is correct. Remember, Mr. Oborn asked about data
backed up with TDP for Informix. That data is backed up with API code,
not BA code. The dsmc b/a client cannot access anything about filespaces
or backups, since it doesn't access the relevant information.

From the TSM server, he *could* use QUERY OCCUPANCY on the Informix
filesystems and see how much storage space the Informix data is taking
up on tape and/or disk storage pools, but that's about it. If you run a
QUERY FILESPACE from the server, it will 0 MB of space occupied; this is
because the QUERY FILESPACE command only access data about clients
backed up with the BA code.

Again, I think the only way to access information about what is
available for backups is with the TDP for Informix code (and possibly
Informix itself), and that will only run if Informix is loaded and
running on the console.

Del, do I have that right?

--
Mark Stapleton



***
This email, including any attachments sent with it, is confidential and for the sole 
use of the intended recipient(s).  This confidentiality is not waived or lost, if you 
receive it and you are not the intended recipient(s), or if it is transmitted/received 
in error.

Any unauthorised use, alteration, disclosure, distribution or review of this email is 
prohibited.  It may be subject to a statutory duty of confidentiality if it relates to 
health service matters.

If you are not the intended recipient(s), or if you have received this email in error, 
you are asked to immediately notify the sender by telephone or by return email.  You 
should also delete this email and destroy any hard copies produced.
***


Re: Virtual Tape Library

2004-05-19 Thread Gee, Norman
I tried using the IBM 3494-B18 VTS with TSM on the zSeries (z/OS) and
decided it was not a good fit.  TSM recalls partially fill tapes to finish
filling it.  The recall time was about 4 minutes.  Reclaim processing took
forever to bring in reclaimable volumes. Restores took forever with double
recalls of volumes. I am much happier using native 3590 drives.

-Original Message-
From: Coats, Jack [mailto:[EMAIL PROTECTED]

Anyone tried using one with TSM?

I am mainly interested in a Windows environment, but other experiences would
be very intersting?

Vendor?   Size?   Price?   Ease of Setup?   Ease of Use?   Operational
considerations?  Opinions?

TIA ... Jack