Without a description of the test procedure you are following is little
bit hard to find the mistake. Anyway an attempt to explain:
0. filesystem is not backed up at all
TSM has no knowledge of the files it contains.
1. dsmc incr /<fs_mount> is invoked and completes with success ("full
incremental" in TSM terms = "full backup" in legacy tools terms)
TSM contains "active" versions for all files in the filesystem.
2. N files are changed on the filesystem
using both `dsmc incr` and `dsmc incr -incrbydate`, only those N files
will be backed up
3. no files are changed after step 2 and another backup is attempted.
if `dsmc incr` was used in step 2, nothing would be backed up. If `dsmc
incr -incrbydate` was used in step 2, all N files will be backed up again.
4. New backup using `dsmc incr` is performed *without* -incrbydate option
and completes successfully.
TSM backups only the files changed since last backup regardless the fact
was last backup with or without -incrbydate. Last backup date of the
filespace is updated.
5. one file is changed and incremental by date is performed.
only one file will be backed up.
6. one more file is changed and another backup is performed.
now again we have the difference between the behavior of `dsmc incr` and
`dsmc incr -incrbydate`. Without the option only the file changed since
last backup (i.e. since step 5) would be backed up. With the option both
files (all files since "full incremental", i.e. since step 4) will be
backed up.
Step 4 or any subsequent "full incremental" becomes new starting point for
incrementals by date.
Zlatko Krastev
IT Consultant
Lopez Janeth <jlop10 AT CANTV.COM DOT VE>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
13.06.2003 21:06
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: active version
yes, I checked with a query -incremental the last backup date and TSM add
one new backup. If I do not mofified anything file, why TSM backed up
again?
Janeth
-----Mensaje original-----
De: Dwight Cook [mailto:cookde AT US.IBM DOT COM]
Enviado el: Viernes, 13 de Junio de 2003 01:08 p.m.
Para: ADSM-L AT VM.MARIST DOT EDU
Asunto: Re: active version
The manual states that:
If a file system is specified, all new and changed files are backed up.
In addition, the last incremental date for the file space is updated on
the
server.
If a file or directory is specified, the last incremental date is not
updated.
This means the file or directory might be backed up again if a later
backup
is performed using the incrbydate option.
so if you did
I /home/u/NetCmmnd/proyecto/rexx/*.rex
followed by
I -incrbydate /home/u/NetCmmnd/proyecto/rexx/*.rex
the last backup date of the filesystem "home" would not have been
updated...
you can view the last backup date of the file system via a query file
hope this helps
Dwight
Lopez Janeth
<jlop10 AT CANTV DOT COM To:
ADSM-L AT VM.MARIST DOT EDU
.VE> cc:
Sent by: "ADSM: Subject: Re: active
version
Dist Stor
Manager"
<[email protected]
.EDU>
06/13/2003 10:51
AM
Please respond to
"ADSM: Dist Stor
Manager"
I did an full backup and then did a incremental by date backup
I -incrbydate /home/u/NetCmmnd/proyecto/rexx/*.rex
Node Name: EQ201PATROL02
Session established with server ADSM: MVS
Server Version 3, Release 1, Level 2.50
Server date/time: 06/12/03 19:54:43 Last access: 06/12/03 19:42:05
Incremental by Date of volume '/home/u/NetCmmnd/proyecto/rexx/*.rex'
Normal File--> 173
/home/u/NetCmmnd/proyecto/rexx/MsgOperator.rex [Sent]
Normal File--> 1,292
/home/u/NetCmmnd/proyecto/rexx/comando.rex
[Sent]
Normal File--> 1,224
/home/u/NetCmmnd/proyecto/rexx/consolaDELR.rex [Sent]
Normal File--> 10,969
/home/u/NetCmmnd/proyecto/rexx/em_controlm.rex [Sent]
Normal File--> 8,050
/home/u/NetCmmnd/proyecto/rexx/em_os390.rex
[Sent]
Normal File--> 8,404
/home/u/NetCmmnd/proyecto/rexx/em_os390_phpt.rex [Sent]
Normal File--> 8,301
/home/u/NetCmmnd/proyecto/rexx/em_os390_phpt_SMS.rex [Sent]
Normal File--> 5,235
/home/u/NetCmmnd/proyecto/rexx/em_snmp.rex
[Sent]
Normal File--> 8,648
/home/u/NetCmmnd/proyecto/rexx/em_snmp_phpt.rex [Sent]
Normal File--> 1,792
/home/u/NetCmmnd/proyecto/rexx/levantar_agente.rex [Sent]
Normal File--> 2,429 /home/u/NetCmmnd/proyecto/rexx/luis.rex
[Sent]
Normal File--> 6,294
/home/u/NetCmmnd/proyecto/rexx/nt2_NetCmmnd.rex [Sent]
Normal File--> 779
/home/u/NetCmmnd/proyecto/rexx/nt2_borrar_notif_diaria.rex [Sent]
Normal File--> 800
/home/u/NetCmmnd/proyecto/rexx/nt2_borrar_notif_phpt.rex [Sent]
Normal File--> 13,591
/home/u/NetCmmnd/proyecto/rexx/nt2_patrol_clear.rex [Sent]
Normal File--> 14,089
/home/u/NetCmmnd/proyecto/rexx/nt2_patrol_critica.rex [Sent]
Normal File--> 24,681
/home/u/NetCmmnd/proyecto/rexx/nt2_patrol_critica_sap.rex [Sent]
Normal File--> 14,105
/home/u/NetCmmnd/proyecto/rexx/nt2_patrol_critica_work.rex [Sent]
Normal File--> 14,056
/home/u/NetCmmnd/proyecto/rexx/nt2_patrol_major.rex [Sent]
Normal File--> 14,130
/home/u/NetCmmnd/proyecto/rexx/nt2_patrol_minor.rex [Sent]
Normal File--> 13,270
/home/u/NetCmmnd/proyecto/rexx/nt2_patrol_phpt_fast.rex [Sent]
Normal File--> 13,221
/home/u/NetCmmnd/proyecto/rexx/nt2_patrol_phpt_janeth.rex [Sent]
Normal File--> 13,955
/home/u/NetCmmnd/proyecto/rexx/nt2_patrol_warn.rex [Sent]
Normal File--> 2,397
/home/u/NetCmmnd/proyecto/rexx/os390not.rex
[Sent]
Normal File--> 276
/home/u/NetCmmnd/proyecto/rexx/paconsolapatrol.rex [Sent]
Normal File--> 2,475
/home/u/NetCmmnd/proyecto/rexx/paemail_ora.rex [Sent]
Normal File--> 10,021
/home/u/NetCmmnd/proyecto/rexx/phptprueba.rex [Sent]
Normal File--> 6,230
/home/u/NetCmmnd/proyecto/rexx/ppInitiate.rex [Sent]
Normal File--> 6,304 /home/u/NetCmmnd/proyecto/rexx/ppJL.rex
[Sent]
Normal File--> 1,277
/home/u/NetCmmnd/proyecto/rexx/prg_rexx.rex
[Sent]
Normal File--> 1,425
/home/u/NetCmmnd/proyecto/rexx/pruebaoserep.rex [Sent]
Normal File--> 1,313
/home/u/NetCmmnd/proyecto/rexx/vconesa1.rex
[Sent]
Normal File--> 1,335
/home/u/NetCmmnd/proyecto/rexx/vconesa2.rex
[Sent]
Normal File--> 1,744
/home/u/NetCmmnd/proyecto/rexx/vconsola.rex
[Sent]
Successful incremental backup of '/home/u/NetCmmnd/proyecto/rexx/*.rex'
Total number of objects inspected: 61
Total number of objects backed up: 34
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 0
Total number of objects failed: 0
Total number of bytes transferred: 229.69 KB
Data transfer time: 3.77 sec
Network data transfer rate: 60.80 KB/sec
Aggregate data transfer rate: 45.76 KB/sec
Objects compressed by: 0%
Elapsed processing time: 00:00:05
Thu Jun 12 20:02:57 AST 2003
if the files do not was updated, why TSM backed up all files in the
incremental by date?
Janeth
-----Mensaje original-----
De: Dwight Cook [mailto:cookde AT US.IBM DOT COM]
Enviado el: Viernes, 13 de Junio de 2003 11:08 a.m.
Para: ADSM-L AT VM.MARIST DOT EDU
Asunto: Re: active version
So all "active" versions of files stored on a TSM server is what you can
classify as ~the current restore set~.
They make up all the data as it existed the last time a ~backup~ was
performed (be it "incr" or "sel")
Now, what might be missing ? files that are found in "exclude"
statements, files that failed to back up, etc...
Say we are on a windows box and you do a
restore -subdir=yes C:\*
tsm will give you back all the "active" files.
Dwight
Lopez Janeth
<jlop10 AT CANTV DOT COM To:
ADSM-L AT VM.MARIST DOT EDU
.VE> cc:
Sent by: "ADSM: Subject: active version
Dist Stor
Manager"
<[email protected]
.EDU>
06/13/2003 09:19
AM
Please respond to
"ADSM: Dist Stor
Manager"
hi, how I know if the active version is a full or partial incremental
backup?
Janeth
|
