To: [EMAIL PROTECTED]
Subject: synthetic fullbackup
Hi Halvorsen:
I am trying to implement this same move nodedata idea, but am coming up
with problem. My environment is Win2k server running TSM server 5.1.5.2
and same on clients. My goal is consolidate my tapepool data for each node
so each node has
Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:Re: synthetic fullbackup
Make the tape pool collocation enabled and do a migration on the disk
pool
(update stg diskpool hi=0 low=0). Also helps to have migration process
set
to 1 for the disk pool. I don't know
Halvorsen
GeirrTo: [EMAIL PROTECTED]
Gulbrand cc:
gehal@WMDATASubject: Re: synthetic fullbackup
.COM
Sent by:
ADSM: Dist
On Fri, 2002-12-20 at 12:16, Ron Lochhead wrote:
I am trying to implement this same move nodedata idea, but am coming up
with problem. My environment is Win2k server running TSM server 5.1.5.2
and same on clients. My goal is consolidate my tapepool data for each node
so each node has it's
-Plough Corp.
(901) 320-4462
(901) 320-4856 FAX
[EMAIL PROTECTED]
-Original Message-
From: Ron Lochhead [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 20, 2002 12:16 PM
To: [EMAIL PROTECTED]
Subject: synthetic fullbackup
Hi Halvorsen:
I am trying to implement this same move
: 18. december 2002 16:10
To: [EMAIL PROTECTED]
Subject: AW: synthetic fullbackup
Hi Richard
thanks for your hints.
We still hope on a solution that makes us happy. The idea with BackupSet is
theoretically the closest one. But I heard from people with experince, that
(i) its not so easy to restore
We are looking for a solution for the following problem:
During a restore of a whole TSM-client we found that the needed ACTIVE
backup_versions were heavy scattered around our virtual tape-volumes. This
was the main reason for an unacceptable long restore-time. Disk as a primary
STGPool is too
have just
pointed out some of TSM's features.
Rgds.
Geirr Halvorsen
-Original Message-
From: Schwarz Werner [mailto:[EMAIL PROTECTED]]
Sent: 18. december 2002 14:08
To: [EMAIL PROTECTED]
Subject: synthetic fullbackup
We are looking for a solution for the following problem:
During
We are looking for a solution for the following problem:
During a restore of a whole TSM-client we found that the needed ACTIVE
backup_versions were heavy scattered around our virtual tape-volumes. This
was the main reason for an unacceptable long restore-time...
Werner - As Geirr said,
are moved - we need quite a
lot of storage if we maintain many versions.
thanks very much
werner
-Ursprüngliche Nachricht-
Von: Halvorsen Geirr Gulbrand [mailto:[EMAIL PROTECTED]]
Gesendet am: Mittwoch, 18. Dezember 2002 14:44
An: [EMAIL PROTECTED]
Betreff: Re: synthetic fullbackup
Hi Werner,
we
Backupsets are the optimal solution
In TSM v5, I've replaced my backupsets with MOVE NODE DATA as my
preferred way of consolidating a node's backup data onto a minimum
number of tapes.
David
to the process GENERATE BACKUPSET
(collect/consolidate all newest versions).
Regards,
werner
-Ursprüngliche Nachricht-
Von: Richard Sims [mailto:[EMAIL PROTECTED]]
Gesendet am: Mittwoch, 18. Dezember 2002 15:21
An: [EMAIL PROTECTED]
Betreff: Re: synthetic fullbackup
We are looking
:
Sent by: ADSM: Subject: AW: synthetic fullbackup
Dist Stor
13 matches
Mail list logo