Incremental by date backups compare the modification time of each file
with the time of the file system's last backup. If the file's modification
time is greater than the time of the file system's last backup, then the
file is considered to have changed, and will be backed up. Otherwise the
file is not backed up.
The file system's last backup time is changed only after the last backup
of the entire file system. According to your QUERY FILESPACE output, you
have not completed full incremental backups of your file systems.
I would recommend that you first perform complete incremental backups of
your file systems, i.e.:
dsmc i
or if you just want to back up /home:
dsmc i /home
Once you have done this, QUERY FILESPACE should show a valid last backup
time. Then you can run the incremental by date backup.
NOTE: Remember what I said about the last backup time being changed only
after a backup of the entire file system. If, for example, you do this:
1) First full backup of /home:
dsmc i /home
QUERY FILESPACE now shows a valid last backup time.
2) Incremental by date of a particular directory or files:
dsmc i /home/u/NetCmmnd/proyecto/rexx/*.rex -incrbydate
QUERY FILESPACE shows the same last backup time as in step #1 because you
did not do a backup of the *entire* file system. Therefore...
3) Another incremental by date of the same directory or files:
dsmc i /home/u/NetCmmnd/proyecto/rexx/*.rex -incrbydate
The same files are backed up as in step #2!
In general, it is recommended that you always use full incremental backup
to back up your data since that is the most accurate and complete method
for performing incremental backup and managing your data on the TSM
server. However, full incremental processing can be very time-consuming
for very large file systems due to the amount of time it takes to query
the TSM server for information about existing backups. Incremental by date
is a compromise: the TSM server query is eliminated, but at the cost of
less accurate incremental backups and less refined management of your data
on the TSM server.
If the size of your file systems make it impractical to use full
incremental backup for daily backups, then you should implement a backup
strategy like this:
- Full incremental on a regular periodic basis, i.e. once a week.
- Incremental by date backups on other days.
For backing up individual files and directories, there is almost certainly
no reason to use the -incrbydate option.
Please see the client manual for more information about incremental by
date backup, the INCRBYDATE option, and considerations related to
incremental by date processing.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Lopez Janeth <jlop10 AT CANTV.COM DOT VE>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06/13/2003 12:27
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: active version
I am workin on Solaris, client tsm 4.2.1
tsm> q file
Node Name: EQ201PATROL02
Please enter password for node "EQ201PATROL02":
Session established with server ADSM: MVS
Server Version 3, Release 1, Level 2.50
Server date/time: 06/13/03 15:22:46 Last access: 06/13/03 15:19:27
Num Last Incr Date Type File Space Name
--- -------------- ---- ---------------
1 00/00/00 00:00:00 UFS /backup
2 00/00/00 00:00:00 UFS /home
3 00/00/00 00:00:00 UFS /opt
Janeth
-----Mensaje original-----
De: Dwight Cook [mailto:cookde AT US.IBM DOT COM]
Enviado el: Viernes, 13 de Junio de 2003 02:38 p.m.
Para: ADSM-L AT VM.MARIST DOT EDU
Asunto: Re: active version
Well, either something is broken or something isn't what you are
expecting...
to verify, from your unix prompt, in the directory
"/home/u/NetCmmnd/proyecto/rexx/" do a "df ./"
it should show /home as the file system...
AIX-> df ./
Filesystem 512-blocks Free %Used Iused %Iused Mounted on
/home 3899392 1061264 73% 3040 1% /home
then double check
tsm> q file
Num Last Incr Date Type File Space Name
--- -------------- ---- ---------------
<... stuff deteted ...>
6 06/13/2003 06:16:36 JFS /home
<... more stuff deleted ...>
now do an "ls -l /home/u/NetCmmnd/proyecto/rexx/*.rex" and if any of those
files show a date later than the date on the "Last Incr Date", it will be
backed up, every time you do your incremental with the -incrbydate (until
you do another plain "incr" and the "last incr date" is updated...
NOTE: a ~failed~ incremental will not update the "last incr date" an
incremental must finish successfully for the date to be updated...
IF not, I would look into upgrading the client code.
Might I point out that you have not provided any information on what TSM
client level you are at, what platform it is for (AIX, Solaris, etc...)
you
have not provided the listing of what you are seeing with your "q file"
and
you are not providing information on an "ls -l" of the files in question.
without any hard proof of what they are... only guesses can be made...
sorry...
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 01:06
PM
Please respond to
"ADSM: Dist Stor
Manager"
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
|
