He mentioned "Due to tape library slot limitation" and "Check out all tape
(current cycle)" I think he is checking out all tapes (including primary
copies)
I believe he is trying to manage around primary tapes being requested and
wondering why it was needed in this case. Also, I think ANR1228I on
Victor,
Assuming it is a copy pool volume (since primary storage volumes should
always be available in your library).
Investigate the volume status on your TSM server:
Use the "query drmedia" command determine the volume's current state, if
in fact it should be out of the library it's state woul
I have observed that for primary storage pools where the tape volumes have been
DEFINEd to belong to that pool, MOVE DATA to consolidate tapes belonging to the
same collocation group has unexpected results. The database reliably selects
the volume copied FROM as the primary candidate for the ne
Ditto what everybody else said- can be lots of things.
But I've seen this behavior at exactly ONE customer with LTO4 drives in a
TS3310.
2-drive processes would sometimes take hours.
No errors recorded anywhere, just very, very slow.
Peering through the TS3310 window, I could see (with difficulty
Since you mentioned they were SCSI drives, is it possible you have a
cable quality / length / termination issue on your SCSI bus. It might
only manifest itself under certain signalling conditions such as those
under heavy load by multiple targets. Can you do a full tape-to-tape
copy outside of TS
And on Windows you can use the task manager to look at bytes read or written
per process. Find the TSM Server process and verify that it is indeed moving
data.
Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777 x7105
www.storserver.com
-Original Mes
Mario,
Based on your server level (5.5) you may be experiencing the following:
IC57855: TSM SERVER DELAYS TRANSACTIONS BY 1 SECOND WHEN RECOVERY LOG
UTILIZATION EXCEEDS 80% RESULTING IN PERFORMANCE DEGRADATION
Please check your recovery log utilization to see if this may be the issue.
With only
Mario,
So, if I understand this correctly, the primary storage pool is LTO4,
and the copy storage pool is LTO4, and so the whole "backup stgpool" is
straight tape to tape. Is that correct?
When you say the process becomes "idle" for 20 minutes, how can you tell
it is idle? Do you mean the number
This is a known bug, fixed in 5.4.2
http://www-01.ibm.com/support/docview.wss?uid=swg1IC54096
Michael DeGasperis
EDS - Centralized Backup and Restore
MS 3-o
1075 West Entrance Drive
Auburn Hills, MI 48326
( Phone:+1-248-853-3726(8-365)
+ [EMAIL PROTECTED]
pager: 248-272-0157
-O
I suspect that some sort of timeout is involved. Storage pool backups
use a lot of CPU, and a lot of db reads to generate a list of files that
need to be backed up. I suspect that it may take some time to ditch that
queued list of files before you can start another stg backup session
involving the
In any event, it is normal procedure to schedule creation of copypool from
disk then the tape pool they are migrated to. The 1st to avoid unnecessary
mount, the 2nd to ensure you do have all the files in the copypool.
You welcome:-).
- Original Message -
From: "Nick Laflamme" <[EM
Larry Clark wrote:
But I think the question was why are these files not in the copypool.
If they were migrated and a backup stg (of the pool disk files are
migrated
to) was scheduled, they should be.
So his problem suggests they have a scheduled backup to the copypool
from the primary disk poo
But I think the question was why are these files not in the copypool.
If they were migrated and a backup stg (of the pool disk files are migrated
to) was scheduled, they should be.
So his problem suggests they have a scheduled backup to the copypool
from the primary disk pool, but not the pool
Kelly Lipp wrote:
It can be thought of as the "just in case" backup operation. You may
well have had migrations.
I'm not sure if data that gets migrated, cached or not, is backed up
from disk or from tape. I'm thinking that if it has been migrated and
is cached, the backup will occur from the
It can be thought of as the "just in case" backup operation. You may
well have had migrations.
I'm not sure if data that gets migrated, cached or not, is backed up
from disk or from tape. I'm thinking that if it has been migrated and
is cached, the backup will occur from the nextstgpool in any e
> On Oct 2, 2007, at 4:36 PM, Nick Laflamme wrote:
>
> > Anything on tape should have been resident in the disk pools when they
> > were backed up.
>
> Nick -
Also, check "Maximum Size Threshold" setting on the disk pools. If it is
not set to "no limit", then any file exceeding the maxsize allowe
On Oct 2, 2007, at 4:36 PM, Nick Laflamme wrote:
Anything on tape should have been resident in the disk pools when they
were backed up.
Nick -
You're speculating, without analysis of what landed in each level of
the storage pool hierarchy. You can most readily utilize the Query
CONTent with
Nick Laflamme wrote:
>
> If the disk pools are sized correctly, migrations should occur once a
> day or less, after the daily backup window has ended. The storage pools
> should be backed up after migrations are "encouraged" (by updating
> storage pools with new migration thresholds). We backup the
??What I don't understand is, why does anything on tape get backed up to
the copy pool?
I'd look at your admin scheds. There needs to be an explicit backup stg
My guess is that was never set up.
- Original Message -
From: "Nick Laflamme" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, October
John,
We were having the same problem with long duration Exchange backups. We
used the example that Del suggested in a response to the list to run
multiple streams and it has resolved the problem. We are also currently
sending the backups directly to an EMC/CDL.
http://www.mail-archive.com/adsm
-John D. Schneider wrote: -
>2) Another unusual circumstance is that the 'backup stgpool' for the
>storage pool containing the Exchange data begins running before the
>clients are done. Sometimes the 'backup stgpool' get stuck waiting
>for a tape mount, even though the tape is not mounted,
>> On Fri, 10 Feb 2006 09:23:35 -0500, Richard Mochnaczewski <[EMAIL
>> PROTECTED]> said:
> Thanks for the info. What's even stranger is I can launch the same
> type of process using another storage pool ( backup stgpool prd_disk
> prd_dr maxpr=4 ) and it WILL use 4 tape drives and multithread ?
On other thing I noticed : There are no drives in use at all when I launch the
command, so why not launch the four threads if there is no tape drive
contention ?
Rich
-Original Message-
From: Richard Mochnaczewski
Sent: Friday, February 10, 2006 9:24 AM
To: 'ADSM: Dist Stor Manager'
Su
I'll guess what may be happening here.
The TSM server runs the 'backup storagepool' and 'migrate' commands on
a "per node" basis. Meaning that if you set it to 4 sessions, TSM will look at
the storage pool, pick the node with the most data and start to duplicate that
data, it w
Hi Richard,
Thanks for the info. What's even stranger is I can launch the same type of
process using another storage pool ( backup stgpool prd_disk prd_dr maxpr=4 )
and it WILL use 4 tape drives and multithread ?!?!?!?
Rich
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAI
On Feb 10, 2006, at 8:53 AM, Richard Mochnaczewski wrote:
Why does it always default to one process instead of multiple
sessions as I initiate ?
A question that keeps coming up... Some prevailing factors:
The operation is node-oriented, which limits the actual number of
operating processes; a
[mailto:[EMAIL PROTECTED] On Behalf Of
> L'Huillier, Denis (GTI)
> Sent: Thursday, February 09, 2006 7:52 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: BACKUP STGPOOL or MOVE DATA Error
>
> Contact support. I had a similar situation. Here's the synopsis:
>
> The d
11:59 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: BACKUP STGPOOL or MOVE DATA Error
I was first told to put in ionocopy off in my server options file to
resolve one problem and then latter I was told to remove this option as
it cause other problems. When I query ionocopy option it now shows on.
Your s
27;ON' enable or disable, sorry the query shows on or off and not
enable or disable.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
L'Huillier, Denis (GTI)
Sent: Thursday, February 09, 2006 7:52 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: BACKUP
Contact support. I had a similar situation. Here's the synopsis:
The data is corrupt but may be recoverable via a PTF. New storage pools
defined with 5.3 will verify the data before moving to a different pool.
If the data is corrupt it will not move the data so recovery efforts can
be initiated
This was discussed a few weeks ago on the listserv. Sounded like
a bug to me.
Search the archives for a message with this title for the
thread:
"Stgpool backup behavior change in 5.3.x?"
Ben
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECT
glish
Sent: Tuesday, September 27, 2005 11:11 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Backup stgpool
Andrew,
You can use the maxpr=number option with the backup stgpool command.
i.e.: backup stgpool primarypool copypool maxpr=2 <---If you are backing
up a tape pool, this will use 4 tape drives.
Andrew,
You can use the maxpr=number option with the backup stgpool command.
i.e.: backup stgpool primarypool copypool maxpr=2 <---If you are backing up
a tape pool, this will use 4 tape drives...if its a disk pool, it will use
only 2 tape drives.
Sean English
Sandra,
As I re-read through this, I realize I made a mistake. Using delete
volume will not adhere to the reuse delay. Reclamation set to 1 will.
But I also think there are other things that should be considered, most
of which were addressed by Andy in other posts.
Sorry if my mistake cause you
==> On Fri, 9 Sep 2005 15:15:12 +1000, Steven Harris <[EMAIL PROTECTED]> said:
> Excuse the obvious question, but what happens if there is a disaster at the
> *remote* site? Whilst you'll still have your current disk copies of
> everything, you'll lose all your historical stuff, and those "never
free
> backup client.. any idea if there are plans to change this in the near
> future?
>
> Many thanks
>
> Jon
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
> Andrew Raibeck
> Sent: 08 September 2005 20:41
&g
Hi Sandra,
> If my 1st DB backup expires on 4th day, its only that DB tape that
> would return to vault-retrieve and not the corresponding data tapes
> since these data tapes contain data that is refered to by the 2nd db
> backup. NOW the problem starts where I have to keep sending data
> tapes d
L@VM.MARIST.EDU
Subject: Re: backup stgpool
Hi Sandra,
I think one concept to understand is that a copy storage pool is a
logical, point-in-time mirror image of the primary storage pool(s) that
are backed up by that copy storage pool.
Let's say for the sake of simplicity that you have two p
Hmm Thanks Alot Andy,
All that description cleared lots of things.
There is one little question/confusion.
If my 1st DB backup expires on 4th day, its only that DB tape that would return
to vault-retrieve and not the corresponding data tapes since these data tapes
contain data that is refered
Allen,
Excuse the obvious question, but what happens if there is a disaster
at the *remote* site? Whilst you'll still have your current disk
copies of everything, you'll lose all your historical stuff, and
those "never to be deleted" backups that managers are so attached
to. You'll also have no
==> On Thu, 8 Sep 2005 12:40:41 -0700, Andrew Raibeck <[EMAIL PROTECTED]> said:
> [...I]nstead of having one onsite copy pool, why not just have two offsite
> copy pools. Again, assess the risks: what are the odds that you will
> actually need your copy storage pools in the event that a non-offsi
Hi Sandra,
I think one concept to understand is that a copy storage pool is a
logical, point-in-time mirror image of the primary storage pool(s) that
are backed up by that copy storage pool.
Let's say for the sake of simplicity that you have two primary storage
pools, DISKPOOL and TAPEPOOL; and t
Welll Andrew,
I had misconception as under:
1- backup stgpool will backup entire primary storagepool daily with DB tape.
This would be one set and on disaster, this set will recover us to the point
where that DB stands.
2- If any data tape in above set gets corrupted, i have a choice of going back
> Ok..i have to have two copy storage pools both having a complete and
> separate set of tapes. From this i understand that everytime the
> stgpool backup is performed, there is no way to tell TSM that you
> need to take full backup of primary pool instead of incremental from
> what it did last day
Sandra,
As I read through your initial request, it sounds like, every Friday,
you want all of your offsite copy pool tapes consolidated onto fewer
tapes. If that is what you are wanting, you can delete vol with
discarddata=yes for each of your offsite pool tapes prior to your backup
stgpool (now t
Hmmm thanks andy,
I have changed the reuse delay to 4, that is the same as dbbackup expiration
days.
Ok..i have to have two copy storage pools both having a complete and separate
set of tapes. From this i understand that everytime the stgpool backup is
performed, there is no way to tell TSM tha
Hi Sandra,
I'm sure you'll get plenty of advice and suggestions from others, but here
are my "two cents":
Once concern right off the bat is the reuse delay of zero, which puts at
risk your goal of 100% restore capability of up to 4 days ago. Instead,
your reuse delay should be the same as your db
il 20, 2005 1:47 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: backup stgpool from one server to another?
On Wed, 20 Apr 2005, Prather, Wanda might have said:
> Yes, you can use one TSM server as an "electronic vault" for another
TSM server.
>
> Look in the Administrator's Guide u
On Wed, 20 Apr 2005, Prather, Wanda might have said:
> Yes, you can use one TSM server as an "electronic vault" for another TSM
> server.
>
> Look in the Administrator's Guide under the topic "Using Virtual Volumes to
> Store Data on Another Server".
>
> It may not be the best approach, however:
Yes, you can use one TSM server as an "electronic vault" for another TSM server.
Look in the Administrator's Guide under the topic "Using Virtual Volumes to
Store Data on Another Server".
It may not be the best approach, however:
* The data is sent from the primary server to the secondary
> Suppose I've a storage pool called tapepool and a copy storage pool called
> disaster-recovery, both sequencial storage pools. After some data migrated
> to the tapepool storage pool a BACKUP STGPOOL is executed to copy this
> data to disaster-recovery. Some time later, new data are migrated to t
Depends!
If the DR tape is still in the library and still marked "readwrite", TSM
will append the new data to it.
If the DR tape has been marked access=OFFSITE, TSM will mount a new scratch
tape to write the new data.
-Original Message-
From: Reimer [mailto:[EMAIL PROTECTED]
Sent: Thursda
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Reimer
>Suppose I've a storage pool called tapepool and a copy storage pool
called
>disaster-recovery, both sequencial storage pools. After some data
migrated
>to the tapepool storage pool a BACKUP STGPOOL is executed to copy this
Have you looked at the value of "Current Physical File" - it is 55,767,181,387.
TSM Server does not increment the "Bytes Backed Up" value until the
transaction finishes and it may take a lot of time (calculate yourself how
much should take 55 GB with your tape technology). Whatever number of
times
>my daily backup storagepool works fine since yesterday. The process
>started with a central script. All storage pools are copied fine during a
>few minutes. But the last of them, TAPE_BACKUP_001, probably the biggest
>will not finish for more then 20 hours. I queried the process severalt
>times, b
t;[EMAIL PROTECTED]>
Gesendet von: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
12.10.2003 10:47
Bitte antworten an "ADSM: Dist Stor Manager"
An: [EMAIL PROTECTED]
Kopie: (Blindkopie: Gerd Becker/Emprise)
Thema: Re: Backup Stgpool Process han
Hi,
First, what version of TSM are you running? From the looks of it it must be
5.1.x or 5.2.x. And, is the library shared and/or SAN attached?
I think you have to restart and maybe reboot your TSM server. Because TSM is
not able to complete the file its working on, it will never end nor cancel
t
I don't know if someone else as suggested this already not having seen the
start of this thread but when I'm in a 'have to stop process, need tape
drive' situation, after I issue the cancel of the process, I also update
the cartridge itself to access=unavailable. This will stop the process
almost
ways
seems to recover ok and audit volumes of the volumes in use don't seem to
have any problems.
Just another pet peeve.
JT
From: "Stapleton, Mark" <[EMAIL PROTECTED]>
Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re
From: James Taylor [mailto:[EMAIL PROTECTED]
> Is there still no way to enter a command in that will cancel
> a process immediately. For years we have had to put up with
> this problem.
It's called rollback, James. In order for TSM to maintain integrity
between the state of the backup system a
]>
Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: BACKUP STGPOOL
Date: Wed, 5 Mar 2003 09:31:13 -0500
When you cancel a process of backup stg, the current file
in progress is completed. Not sure what yuu mean about
"170 GB file is
When you cancel a process of backup stg, the current file
in progress is completed. Not sure what yuu mean about
"170 GB file is moved" and how do a I see how many GB
have been moved?
David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH 321.4
I have a similar environment, running about 18 hours a day or so.
It works. Yes, you will have extra hits on disks etc. May need to do
some adjusting of schedules or disks if becomes a problem.
I have TSM server 4.2.1.10 on AIX 4.3.3, also have old server 3.7.4.0
on AIX 4.3.3 (separate server -
al Message-
From: Mire, Nona [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 01, 2002 3:16 PM
To: [EMAIL PROTECTED]
Subject: Re: backup stgpool
We start all of our backups between 9PM and Midnight - we have 39 clients -
our backups finish up before midnight. Our primary storage pool is a
di
We start all of our backups between 9PM and Midnight - we have 39 clients -
our backups finish up before midnight. Our primary storage pool is a
diskpool.
We then do a backup of our diskpool to the copypool. (around 3AM)
Then do a migration from our diskpool to the tapepool. 5AM
Then a backup st
RIST.EDU> on 03/19/2002 03:04:04
PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Backup StgPool Issue Discovered
The question I have: Does anyo
I would say it is a problem. If the backup can't get to some of the data
then it is an error.
- Kai
> Date:Tue, 19 Mar 2002 16:04:04 -0500
> From:"Seay, Paul" <[EMAIL PROTECTED]>
> Subject: Re: Backup StgPool Issue Discovered
>
> The question I have:
reports
success when there were problems??
-Original Message-
From: Seay, Paul [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 19, 2002 3:04 PM
To: [EMAIL PROTECTED]
Subject: Re: Backup StgPool Issue Discovered
The question I have: Does anyone consider this a problem or are you OK with
it
03/19/02 04:04PM >>>
The question I have: Does anyone consider this a problem or are you OK with
it working like this?
-Original Message-
From: Remeta, Mark [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 19, 2002 10:33 AM
To: [EMAIL PROTECTED]
Subject: Re: Backup StgPool Issue
You could also do a
q vol * access=unavailable (or whatever you want to check).
-Original Message-
From: Seay, Paul [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 18, 2002 11:18 PM
To: [EMAIL PROTECTED]
Subject: Backup StgPool Issue Discovered
I found out today it appears that a BACKUP
Paul,
I'm pretty new to TSM and trying bl**d* hard to get a grip on it. We're
experiencing some trouble with TSM in a Windows 2000 environment - issues
we'll most likely have solved by the end of this week, probably earlier -
this is just to give you *some* background to my question.
When TSM d
Yes, this will work.
Jeff Bach
Home Office Open Systems Engineering
Wal-Mart Stores, Inc.
WAL-MART CONFIDENTIAL
-Original Message-
From: Ray [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, May 24, 2001 1:32 PM
To: [EMAIL PROTECTED]
Subject:
>All my nightly backups goto a disk storage pool, and are migrated to tape
>later in the day. I need to start backing up the tape stgpool.
>
>Can i backup to disk storage pool to the copy storage pool first, before
>the disk is migrated to tape? Will the copy stgpool then "know" that the
>files
You want to use:
backup stgpool backupdisk copytape
as example. Look at back stgp command for options. This command copies all files
from backupdisk to the copytape that haven't already been copied.
Yes, this is smart. If you later do a backup stg for the tape to tape copy, that only
copies
say
#dsmadmc
id:
passwd:
dsmc>help backup stgpool
this will display then syntax
balanand pinniBALANAND PINNI.
PHONE 314-206-5911.
EM:[EMAIL PROTECTED]
PG:1-800-451-6897.
-Original Message-
From: Ray [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 24, 2001 1:32 PM
To: [EMAIL PROTECTED]
S
A= /C=us"@X400
cc:
Subject: Re: backup stgpool fails..
FYI,
Do a q stgp f=d
Look for the line Maximum Scratch Volumes Allowed:
Maybe you need to bump this up.
Brian Heiling
Shekhar Dhotre <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROT
>TSM creates daily copypool(offsite) tapes for me , with command backup
>stgpool tapepool copypool , but from yesterday it started failing with
>following error, gives insufficient space error ANR1221E , even though there
>are some scratch tapes.. and this process only needs one scratch tape .
One cause can be that the copypool maxscratch limit has been reached. The
maxscratch sets the maximum number of scratch volume that can be used by the
stroage pool.
Shekhar Dhotre wrote:
> Hi all,
> TSM creates daily copypool(offsite) tapes for me , with command backup
> stgpool tapepool
FYI,
Do a q stgp f=d
Look for the line Maximum Scratch Volumes Allowed:
Maybe you need to bump this up.
Brian Heiling
Shekhar Dhotre <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
12/01/00 08:01 AM
Please respond to "ADSM: Dist Stor Manager"
One cause for this that I had here was we had a few scratch tapes available but there
were defective. Look at your actlog carefully and see if you are getting other
messages (I forget message number) like "Mount request failed" or similar type
happening within a few minutes of you errors.
Dav
storsol.com
www.storserver.com
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Werner Nussbaumer
Sent: Monday, August 14, 2000 7:39 AM
To: [EMAIL PROTECTED]
Subject: Re: BACKUP STGPOOL and BACKUP DB Question
Thank you also for your information.
Kind regards
We
Thank you also for your information.
Kind regards
Werner Nussbaumer
-Original Message-
From: payne [mailto:[EMAIL PROTECTED]]
Sent: Freitag, 11. August 2000 17:28
To: ADSM-L
Cc: payne
Subject: Re: BACKUP STGPOOL and BACKUP DB Question
We do:
1) Backup Disk
2) Backup Tape
3) Backup DB
Thank you very much for your information, I'll do it this way.
Kind regards
Werner Nussbaumer
-Original Message-
From: Phillip.Ford [mailto:[EMAIL PROTECTED]]
Sent: Freitag, 11. August 2000 17:34
To: Phillip.Ford; ADSM-L
Subject: Re: BACKUP STGPOOL and BACKUP DB Question
I can no
We do:
1) Backup Disk
2) Backup Tape
3) Backup DB
4) Run checkouts to get tapes off site.
5) Migrate
6) Expire
7) Backup DB
8) Run Checkin of scratch tapes to fill library (This could be done as part
of step 4 as well).
The first DB backup will be use for Disaster Recover of the server. There
is
I can not say what is best but what we do.
1) backup diskpool to DLTPOOL2
2) Migrate
3) backup the tape pool to DLTPOOL2
4) Backup DB
Both backups must be to the same copy tape pool.
We do it in this order to keep down tape to tape operations. If no backups
occur during step 1 or 2 then step 3
t, 2000 13:57
To: [EMAIL PROTECTED]
Subject: Re: Backup stgpool bug
>08/10/2000 00:52:45 ANR1257W Storage pool backup skipping damaged file on
>volume 0630A5: Node OD6-VERITAS, Type Backup, File space /data0002, File
>name /ora/klapa/dbdata/klapasxb1_1.dbf.
...
>State of SUCCESS??
In article <[EMAIL PROTECTED]>, "Loon,
E.J. van - SPLXM" <[EMAIL PROTECTED]> says:
>
>Hi *SM-ers!
>I discovered a real big problem with TSM (3.7.3 on AIX).
>Yesterday I ran a backup stgpool and I came across the following message in
>the activity log:
>
>08/10/2000 00:52:45 ANR1257W Storage pool b
Suppose a file has been backup stgpool once from primary pool TAPEP to
copypool TAPEC successfully.
My question is: if the file is detected damage while reading primary pool
TAPEP during TAPEC reclaimation, will ADSM keep TAPEC for that file image?
Thanks in advance.
Regards,
Eric Tang
>08/10/2000 00:52:45 ANR1257W Storage pool backup skipping damaged file on
>volume 0630A5: Node OD6-VERITAS, Type Backup, File space /data0002, File
>name /ora/klapa/dbdata/klapasxb1_1.dbf.
...
>State of SUCCESS? 0 Unreadable Bytes? This in NOT correct!
Eric - This may be one of those interpr
Well, technically they are in sync 'cause the file doesn't exist in either
pool !
Granted the damaged file is a problem...
Being a .dbf I'm guessing that was an archived file... if it were a "backed
up file" TSM, now that the file has been identified as damaged, would back
it up during the next
Buy another tape drive.
Just kidding.
I suppose you could move the data from the tape pool back to the diskpool
one tape at a time and do a backup stg diskpool copypool. This might get
most of the data but would take a longg time and be a very manual
process.
TSM was not designed to work w
91 matches
Mail list logo