I am sure TSM will wait. And while we're on this subject, we are looking at
Disaster Recovery plans and the path we must take using TSM to recover a
couple hundred servers. It looks bleak.
We are finding that, due to incremental forever backups, recovery times are
extremely long because of tape
It will wait for the tape. Normally that is. If there is a problem with the
tape (access=unavailable for instance) it will skip it. If another client
is currently restoring from this tape, it will wait till tape is free.
If tape is not in library, generally TSM will issue a "request" for the ta
th a fairly big
setup. In other words, don't just start all restores at once and let 100
clients fight for 6 drives. Of course it's gonna look slow!
-Original Message-
From: Talafous, John G. [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 17, 2002 10:34 AM
To: [EMAIL PROTECTED]
Sub
nal Message-
From: Walker, Thomas [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 17, 2002 11:08 AM
To: [EMAIL PROTECTED]
Subject: Re: DISASTER Client Restores Slow
And using another backup solution won't result in many tape mounts as well?
TSM might be more mounts than others, but yo
From: David Longo [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, May 17, 2002 11:16 AM
> To: [EMAIL PROTECTED]
> Subject: Re: DISASTER Client Restores Slow
>
> It will wait for the tape. Normally that is. If there is a problem with
> the
> tape (access=unavailable for instan
Talafous, John G. [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 17, 2002 10:34 AM
To: [EMAIL PROTECTED]
Subject: Re: DISASTER Client Restores Slow
I am sure TSM will wait. And while we're on this subject, we are looking at
Disaster Recovery plans and the path we must take using TSM to recover a
lker, Thomas [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 17, 2002 11:08 AM
To: [EMAIL PROTECTED]
Subject: Re: DISASTER Client Restores Slow
And using another backup solution won't result in many tape mounts as well?
TSM might be more mounts than others, but you only have to do one restore.
Rem
ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: DISASTER Client Restores Slow
You can use backup sets to create point in time restores of machines. Also
with that few tape drives have you considered collocation. That way
especially with LTO a
> AT my DISASTER REC.SITE
> we have a smaller lto library as compared to the one on our production
site
> if its looking for a tape while restoring and not able to do so, does
it
> wait till the tape is mounted before proceeding with the rest of the
client
> restore? or does it skips restoring tha
y offsite, and keep the copy pool tapes onsite. That would provide
> equal coverage and eliminate the slow/uncollocated restore problem. (AND
> you eliminate the up-front time required to rebuild the TSM server.)
>
> Just something to think about.
>
> -Original Message-
>
Has anyone had a look at a new feature in the TSM5.1 server code that
gives you the facility to consolidate a nodes data - either on filespace
level or node level?
This will address the multiple tapes that a client's data can end up
on over an extended period of time.
For those that do not know ab
Two thought on your comments.
First: If restores are taking a long time due to the amount of data being
restored, you could look at HSM. If your target client is a Windows 2000
machine look at OTG DiskXtender. These products will move files, based on
criteria such as age, size, and/or file type,
Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: DISASTER Client Restores Slow
I am sure TSM will wait. And while we're on this subject, we are looking
at
Disaster Recovery
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Talafous, John G.
> We are finding that, due to incremental forever backups, recovery
> times are
> extremely long because of tape mount after tape mount after tape
> mount. In a
> real disaster, we expect to take an entire day o
14 matches
Mail list logo
