ADSM-L

Re: Backing Up Open Files

2002-10-11 12:47:45
Subject: Re: Backing Up Open Files
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 11 Oct 2002 09:47:28 -0700
The serialization parameter isn't so much for "in use" files as it is for 
files that change while they are being backed up. For example, if a file 
is open ("in use") by the Windows notepad.exe program, TSM can back it up 
regardless of the serialization setting, as long as you don't save the 
file while TSM is backing it up. If you actually save the file while TSM 
is backing it up, then TSM will detect this, and either retry the backup 
or skip the file, depending on the serialization setting.

Always use CAUTION with DYNAMIC or SHRDYNAMIC serialization, since this 
means that the backup copy may be inconsistent ("fuzzy"). It is 
recommended that DYNAMIC or SHRDYNAMIC serialization be used ONLY for 
those files where a restore of a fuzzy copy would be usable. Check with 
the vendor of the application that uses the file to see whether a fuzzy 
copy would be usable.

A different (but related) subject is "locked" files. A file is considered 
to be "locked" when an application opens the file for exclusive use, such 
that no other application (including TSM) can open the file. Note that 
locked files are NOT equivalent to open files; rather, they are a subset 
of open files. Open files can be broken out like this:

   Open ("in use")
         Shareable (nonexclusive)
               Shareable for read
               Shareable for write
               Shareable for read and write
         Non-shareable (exclusive or "locked")

Notepad.exe opens files such that they are shareable, which is why it is 
possible for TSM to back up these files.

When this subject comes up, it is usually with regard to how TSM handles 
(or, more correctly, can't handle) non-shareable files. In this case, 
regardless of the TSM copy serialization setting, TSM can not open these 
files, and thus it can not back them up; at least not without the help of 
an open file manager, such as St. Bernard Software's "Open File Manager" 
product.

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.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Talafous, John G." <Talafous AT TIMKEN DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/11/2002 06:43
Please respond to "ADSM: Dist Stor Manager"

 
        To:     ADSM-L AT VM.MARIST DOT EDU
        cc: 
        Subject:        Re: Backing Up Open Files

 

The 'COPY SERIALIZATION' parameter in the 'BACKUP COPY GROUP' of the
'MANAGEMENT CLASS' in the 'POLICY SET' of the DOMAIN specifies what to do
with an 'IN USE' file. Your choices are:

STATIC - Try once and backup only if not in use.
SHRSTATIC - Try as many as CHANGINGRETRIES parameter. Backup if not in 
use.
DYNAMIC - Backup the file on the first attempt, in use or not.
SHRDYNAMIC - Try as many as CHANGINRETRIES parameter. Try to backup file
when not in use, but backup anyway on the last attempt.

In this case, you want one of DYNAMIC of SHRDYNAMIC specified in your
policy.

John G. Talafous              IS Technical Principal
The Timken Company            Global Software Support
P.O. Box 6927                 Data Management
1835 Dueber Ave. S.W.         Phone: (330)-471-3390
Canton, Ohio USA  44706-0927  Fax  : (330)-471-4034 
talafous AT timken DOT com           http://www.timken.com


-----Original Message-----
From: Vazquez Vegas, Sergio [mailto:svazquez AT ENDESA DOT ES]
Sent: Friday, October 11, 2002 4:30 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Backing Up Open Files


Hi TSM'ers

        Does anyone know about any Tivoli Storage Manager module or tool
used for backing up open files?


Best regards, Sergio.







Sergio Vázquez Vegas
svazquez AT endesa DOT es
Tlf: 91.213.46.88
 <<...OLE_Obj...>> 


Este mensaje de correo electrónico y sus documentos adjuntos están 
dirigidos
EXCLUSIVAMENTE a los destinatarios especificados. La información contenida
puede ser CONFIDENCIAL y/o estar LEGALMENTE PROTEGIDA y no necesariamente
refleja la opinión de ENDESA. Si usted recibe este mensaje por ERROR, por
favor comuníqueselo inmediatamente al remitente y  ELIMÍNELO ya que usted
NO ESTA AUTORIZADO al uso, revelación, distribución, impresión o copia de
toda o alguna parte de la información contenida. Gracias. 

This e-mail message and any attached files are intended SOLELY for the
addressee/s identified herein. It may contain CONFIDENTIAL and/or LEGALLY
PRIVILEGED  information and may not necessarily represent the opinion of
ENDESA. If you receive this message in ERROR, please immediately notify 
the
sender and DELETE it since you ARE NOT AUTHORIZED  to use, disclose,
distribute, print or copy all or part of the contained information. Thank
you. 


**********************************************************************
This message and any attachments are intended for the 
individual or entity named above. If you are not the intended
recipient, please do not forward, copy, print, use or disclose this 
communication to others; also please notify the sender by 
replying to this message, and then delete it from your system. 

The Timken Company
**********************************************************************

<Prev in Thread] Current Thread [Next in Thread>