Hello,
We use TSM 5.3.2.2 on clinet side and 5.3.1 on server side. On client on W2K3
server we use journalling. Our problem is during backup versioning does not
work properly. It backups up same files as much as the version given in
management class.
Is there anyone who had a similar problem
Adam,
I finished upgrade of WAS on TAM Policy server. It is working fine now.
Regards
Jozef
--
SecurIT BV
Overschiestraat 184k
1062 XK AMSTERDAM
T +31 (0)20 408 44 27
F +31 (0)20 408 44 25
M +31 (0)65 116 2671
email to:
] Advantages of having backup by versioning...
My 2 cents worth. (Actual exchange rate will vary)
Using TSM's method of data storage we have about 3 bytes of data on tape for
every byte on a server. When we used a traditional backup method, we had
almost 9 bytes of data on tape for every byte
ebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bernaldo
de Quiros, Iban 1
Sent: Friday, July 14, 2006 5:42 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Advantages of having backup by versioning...
Hi everyone there !!
Could someone explain m
Hi everyone there !!
Could someone explain me the principal advantages of having the backup
organised by versions...¿?
Is it really an advantage to others backup softwares such as Veritas or Legato
¿?
Thanks In Advance,
Regards,
Iban Bernaldo De Quiros Y Marquez
Technical Speciali
?
Rich
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Hurst, David(LIT)
Sent: Wednesday, October 13, 2004 3:54 AM
To: [EMAIL PROTECTED]
Subject: Re: Versioning
Richard
I would highly recommend using a versioning tool such as CVS for change
control
Richard
I would highly recommend using a versioning tool such as CVS for change control . This
only stores the delta's between versions making it much more efficient in terms of
storage . We use it in our software house , the backend is based on MySql which we
dump to file each night (
> We are currently implementing Tivoli as our backup soltuion for all our
AIX
> and Windows servers. As far as versioning, is there some sort of
guideline
> most people are using as far as number of verisons of a specific file to
> keep ? We are primarily a software production house an
with management and describing how the
versioning system worked so that they could develop a retention policy.
R.
-Original Message-
From: Richard Mochnaczewski +AFs-mailto:RichardM+AEA-INVERA.COM+AF0-
Sent: Tuesday, October 12, 2004 11:34 AM
To: ADSM-L+AEA-VM.MARIST.EDU
Subject
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Richard Mochnaczewski
>We are currently implementing Tivoli as our backup soltuion
>for all our AIX and Windows servers. As far as versioning, is
>there some sort of guideline most people are using as far as
&
Hi,
We are currently implementing Tivoli as our backup soltuion for all our AIX
and Windows servers. As far as versioning, is there some sort of guideline
most people are using as far as number of verisons of a specific file to
keep ? We are primarily a software production house and I'm t
t: Re: Backup Versioning / Retention Policy Survey
I expect you will get many replies, so here goes my small offering.
1) There is no such thing as an industry standard for backup
2) You need to find out/understand you r bisiness requirements for
restore and keep your backups sufficient to meet
t; <[EMAIL PROTECTED]>@vm.marist.edu> on 11/03/2003
02:17:23 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To:[EMAIL PROTECTED]
cc:
Subject:Backup Versioning / Retention
Hi TSMers,
It's our understanding that industry standard TSM backup versioning policies (if
there is such a thing) are the following:
TSM Policy Setting Industry Standard
Versions Data Exist 7 / 14**
Versions Data Deleted 7/ 14**
Retain Extra Ve
Hello,
this is a known problem.
APAR= IC37236
TSM ADMINISTRATIVE CLIENT REPORTS SERVER OR STORAGE AGENT
VERSION 5.2.0.0 WHEN CONNECTED TO 5.2.1.0.
.
RCOMP= 5698ISMSVTSM SERVER 510 RREL= R52A
Bye
Rainer Tammer
On Tue, 7 Oct 2003 09:39:07 +0200, Loon, E.J. van - SPLXM wrote:
>Hi *SM-ers!
>
Hi Karel!
I missed that one, thanks!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: Karel Bos [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 07, 2003 10:47
To: [EMAIL PROTECTED]
Subject: Re: Strange TSM 5.2 server versioning
Hi,
>From the rea
Kirsten [mailto:[EMAIL PROTECTED]
Verzonden: dinsdag 7 oktober 2003 10:29
Aan: [EMAIL PROTECTED]
Onderwerp: AW: Strange TSM 5.2 server versioning
Hi Joachim,
We noticed the same with TSM Server V 5.2.1.1 on AIX:
Session established with server HB1: AIX-RS/6000
Server Version 5, Release 2, Level
000 - Version 5, Release 2, Level 1.1
Best regards,
Kirsten
-Ursprüngliche Nachricht-
Von: Stumpf, Joachim [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 7. Oktober 2003 09:55
An: [EMAIL PROTECTED]
Betreff: Re: Strange TSM 5.2 server versioning
Hi Eric,
I noticed the same on TSM Server 5.2.
Hi Eric,
I noticed the same on TSM Server 5.2.1.1 on MVS:
dsmc:
Session established with server TADSM12: MVS
Server Version 5, Release 2, Level 0.0
q st:
Storage Management Server for MVS - Version 5, Release 2, Level 1.1
Server Name: TADSM12
--
mit freundlich
Hi *SM-ers!
When logging on to the server through the admin interface:
Session established with server TSM: AIX-RS/6000
Server Version 5, Release 2, Level 0.0
Server date/time: 07-10-2003 09:18:35 Last access: 07-10-2003 09:17:32
Didn't I just install 5.2.1.1??? After a q status:
tsm: TSM>q
Hi TSMer's,
Is it possible to have onsite versioning different than offsite versioning.
Ex. They want to have 7 versions onsite and just 3 versions offsite. In
the TSM realm, is this possible, feasible, or else,
Thank You in advance,
Bill Rosette
Data Center/IS/Papa Johns International
WWJD
>Is it possible to have onsite versioning different than offsite versioning.
>Ex. They want to have 7 versions onsite and just 3 versions offsite. In
>the TSM realm, is this possible, feasible, or else,
As Andy touched on yesterday, a given file has only one policy affecting it;
so y
Not quite. Copy pools are normally not colocated...so are not clones of
storage pools.
>>> [EMAIL PROTECTED] 08/08/03 09:52AM >>>
>Is it possible to have onsite versioning different than offsite
versioning.
>Ex. They want to have 7 versions onsite and just 3 versions of
Q Vector
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 4:22 AM
To: [EMAIL PROTECTED]
Subject: Expiring Data / Versioning
Hi All
Thanx in advance, new to this and not sure I've set this up correctly.
I originally wanted to keep 7 versions and delete after 30 days any deleted
f
did you activate the policy set after updating copy group? ( just for
confirmation )
regards
Raghu.
Lawrie Scott -
Persetel Q Vector To: [EMAIL PROTECTED]
Subject: Expiring Data / Versioning
Hi All
Thanx in advance, new to this and not sure I've set this up correctly.
I originally wanted to keep 7 versions and delete after 30 days any deleted
files.
I run TSM Server 5.1 and I'm trying to expire all my data down to only one
copy of the data. My versions were set to 7 and the rest as
Hello,
as of my knowledge: init.bki (in .../dbs)
Bye
Rainer Tammer
On Mon, 15 Apr 2002 09:13:03 -0400, Tait, Joel wrote:
>Hi,
>
>Does any one know where the incremented variable for versioning is kept in
>TDP for R/3? I know that you specify the max number of versions in the
Hi,
Does any one know where the incremented variable for versioning is kept in
TDP for R/3? I know that you specify the max number of versions in the
initsid.utl. But where is the actually variable in TSM or TDP for R/3 held?
In a table space?
I would like to use this number in a scripted
PROTECTED]
Subject: Re: tdp r3 and versioning
Becky,
yes, it does. Data that are backed up either by brbackup or brachive are
stored as archive objects in TSM database
and they are deleted when eligible, thus freeing up the tapes.
I don't know of any issues during disaster recovery, when usin
Becky,
yes, it does. Data that are backed up either by brbackup or brachive are
stored as archive objects in TSM database
and they are deleted when eligible, thus freeing up the tapes.
I don't know of any issues during disaster recovery, when using TDP
versioning. The only thing that you s
and versioning
Becky,
yes, we use it in our environment and works exactly as designed; SAP backup
(brbackup/brarchive) utilities manage backup IDs
and delete apropriate ones according to the option MAX_VERSIONS in an
initSID.utl file (see below).
Martin Trcka
...
.
Versioning
Becky,
yes, we use it in our environment and works exactly as designed; SAP backup
(brbackup/brarchive) utilities manage backup IDs
and delete apropriate ones according to the option MAX_VERSIONS in an
initSID.utl file (see below).
Martin Trcka
...
.
Versioning: enabled
Has anyone out there used the tdp for r3 versioning instead of expiration?
How does it work with disaster recovery? What are the bonuses or
detriments?
Thanks
Becky Davidson
Data Manager/AIX Administrator
EDS/Sara Lee Bakery Group
voice: 314-259-7589
fax: 314-877-8589
email: [EMAIL PROTECTED]
Instead of playing with the utl file, why not modify the TSM storage pools?
Send the backup to a primary pool with no volumes assigned to it, then
modify the nextpool parameter as needed. All week it points to your normal
onsite tape pool, but for the weekly backup you want offsite, it points to
till have the two init.utl files. Now I run 5
sessions (five tape drives) on Sunday for the off-line, and 4 sessions (four
tape drives) for the on-line backup.
Tom Kauffman
NIBCO, Inc
> -Original Message-
> From: Tait, Joel [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 25, 2002 9:23
Versioning and Off-site Vaulting
The only way that I can think of is to create 2 onsite primary pools and
change the management classes before each backup to what you want it to be.
Unfortunately, that means the init[SID].utl file has to be different for
each primary pool and you will have to do
Inc
> -Original Message-
> From: Tait, Joel [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 22, 2002 2:48 PM
> To: [EMAIL PROTECTED]
> Subject: TDP R/3 Versioning and Off-site Vaulting
>
>
> Hi
>
> Does anyone have any idea's of how to use copy pools to ta
sent offsite.
-Original Message-
From: Tait, Joel [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 22, 2002 2:48 PM
To: [EMAIL PROTECTED]
Subject: TDP R/3 Versioning and Off-site Vaulting
Hi
Does anyone have any idea's of how to use copy pools to take only 1 SAP DB
Backup version off
e respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: TDP R/3 Versioning and Off-site Vaulting
Hi
Does anyone have any idea's of how to use copy pools to take only 1 SAP DB
Backup version off-site every week
Hi
Does anyone have any idea's of how to use copy pools to take only 1 SAP DB
Backup version off-site every week?
Reason: Primary Pool will hold 4 - 4TB versions of a SAP DB Backup.
Thanks
Joel E. Tait
Joel Tait (E-mail).vcf
Description: Binary data
l Association of Contract Employees (P.A.C.E.)
San Jose, CA
mailto:[EMAIL PROTECTED]
- Original Message -
From: "Ken Long" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, March 17, 2002 5:21 PM
Subject: versioning for user's files
> Hello all...
ut the recovery
capability will be immearsurably improved.
-Original Message-
From: Ken Long [mailto:[EMAIL PROTECTED]]
Sent: Sunday, March 17, 2002 8:22 PM
To: [EMAIL PROTECTED]
Subject: versioning for user's files
Hello all...
We're migrating our NetWare servers, currently backed
abase size.
What kind of versioning do you set for user files, shared documents, etc.,
which are, in my mind, more volatile than application server files because
users are involved? Any examples of the model you use would be
appreciated.
Thanks... Ken
[EMAIL PROTECTED]
cc:
Subject:Re: versioning / expiring / multiple backups under same
nodename
We know the correct way to be backing up the cluster. The customer did not
implement it this way, but we are recommending them to do so.
Before they switch from their current set-up to how we are re
27 51
"Warren, Matthew
James" To: [EMAIL PROTECTED]
Subject:
, the other for shared disk) they would like to know exactly what risk
they are runing with their current setup.
Matt.
-Original Message-
From: Mike Yager [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 18, 2002 4:27 PM
To: [EMAIL PROTECTED]
Subject: Re: versioning / expiring / multiple
(to doubt check unreliable scheduler status)
Jeff Bach
> -Original Message-
> From: Warren, Matthew James [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, January 18, 2002 9:00 AM
> To: [EMAIL PROTECTED]
> Subject: Re: versioning / expiring / multiple backups under same
>
Exactly, while im not doing TSM on my clusters (yet) Daniel is correct.
In my MS-clustered environment, I have the following entries in DNS
SRV01
SRV02
CLUSTER1
DB2-01
the last 2 are a "logical" name of the cluster resource. This allows the "resource" to
be managed separately from the phys
Subject: Re: versioning / expiring
/ multiple
Sent by: "ADSM:backups under same nodename
Dist Stor Manager"
[EMAIL PROTECTED]
Subject: Re: versioning / expiring / multiple backups under same
nodename
Hi,
> I have a customer who wishes to assess the maximum risk he would incurr in
> the following situation;
>
>
> We have a copygroup for backup set for 31 day point-in-time recovery. We
do
> n
Hi,
> I have a customer who wishes to assess the maximum risk he would incurr in
> the following situation;
>
>
> We have a copygroup for backup set for 31 day point-in-time recovery. We
do
> not have nolimit for any copygoup parameters - we assume there will only
be
> a single backup each day.
>
Hi TSM'ers,
(this ones a little long winded, sorry :) )
I have a customer who wishes to assess the maximum risk he would incurr in
the following situation;
We have a copygroup for backup set for 31 day point-in-time recovery. We do
not have nolimit for any copygoup parameters - we assume the
ss. Each management class can have its own set of versioning criteria.
You can have as many management classes as you want to deal with. Thus if
you wanted to, each file of a given database can have different versioning
criteria associated with it.
The include/exclude would look something like
class can have its own set of versioning criteria.
You can have as many management classes as you want to deal with. Thus if
you wanted to, each file of a given database can have different versioning
criteria associated with it.
The include/exclude would look something like this:
include /database1
PROTECTED]
>>> [EMAIL PROTECTED] 06/22/01 02:30PM >>>
If I have one physical server with 2 separate databases on this one physical server,
can I have two separate versioning criteria? i.e. Database 1 with 6 versions data
exists, 3 data deleted, 60 day retain only and Database 2 with
If I have one physical server with 2 separate databases on this one physical server,
can I have two separate versioning criteria? i.e. Database 1 with 6 versions data
exists, 3 data deleted, 60 day retain only and Database 2 with 10 versions data
exists, 6 data deleted, 90 day retain ony
56 matches
Mail list logo
