Re: Backing Up Open Files
Thanks to Andy and Bill Boyer for clarifying "in use" versus "files that change" during the backup process. It helps my understanding of this. jt ** 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 **
Re: Backing Up Open Files
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: [EMAIL PROTECTED] (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." <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10/11/2002 06:43
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
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 CompanyGlobal 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
[EMAIL PROTECTED] http://www.timken.com
-Original Message-
From: Vazquez Vegas, Sergio [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 11, 2002 4:30 AM
To: [EMAIL PROTECTED]
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
[EMAIL PROTECTED]
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.
Re: Backing Up Open Files
No, it tells TSM what to do with a file that CHANGES during the backup. From
the help:
SERialization
Specifies how TSM handles files or directories when they are modified
during backup processing.
If a file is OPEN, then it depends on HOW the application opened itfor
share or exclusive use. If it's opened SHARE access then TSM will back it up
and if it is modified then the SERIALIZATION takes effect. If the file isn't
modified while TSM backs it up, then you got a copy, but no guarantee what
shape it's in. Microsoft even says that you can't back up an MDB file if
it's open. Even though you can physically do it.
If the application opens the file for EXCLUSIVE use, then TSM won't touch
it. Then you need an product like Open File Manager.
Bill Boyer
DSS, Inc.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Talafous, John G.
Sent: Friday, October 11, 2002 9:44 AM
To: [EMAIL PROTECTED]
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 CompanyGlobal 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
[EMAIL PROTECTED] http://www.timken.com
-Original Message-
From: Vazquez Vegas, Sergio [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 11, 2002 4:30 AM
To: [EMAIL PROTECTED]
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 Vazquez Vegas
[EMAIL PROTECTED]
Tlf: 91.213.46.88
<<...OLE_Obj...>>
Este mensaje de correo electrsnico y sus documentos adjuntos estan dirigidos
EXCLUSIVAMENTE a los destinatarios especificados. La informacisn contenida
puede ser CONFIDENCIAL y/o estar LEGALMENTE PROTEGIDA y no necesariamente
refleja la opinisn de ENDESA. Si usted recibe este mensaje por ERROR, por
favor comunmqueselo inmediatamente al remitente y ELIMMNELO ya que usted
NO ESTA AUTORIZADO al uso, revelacisn, distribucisn, impresisn o copia de
toda o alguna parte de la informacisn 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
**
Re: Backing Up Open Files
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Vazquez Vegas, Sergio > Does anyone know about any Tivoli Storage Manager module or tool > used for backing up open files? Look at http://adsm.org at the archives, and look up the monthly TSM FAQ, answer 4-12. Then review answers 02-05 through 02-09. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
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 CompanyGlobal 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 [EMAIL PROTECTED] http://www.timken.com -Original Message- From: Vazquez Vegas, Sergio [mailto:svazquez@;ENDESA.ES] Sent: Friday, October 11, 2002 4:30 AM To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 **
Re: Backing Up Open Files
Tivoli keeps on promising this in future releases for Windows. In fact http://www.tivoli.com/products/resources/storage-mgr/enhancements-5.1.5.html indicates: New Management Features: Windows locked file access improves the availability of applications during backup because there is no longer a need to take an application off-line to backup files that are open/locked during the backup. Although I don't see this mentioned as a new feature in the 5.1.5 client doc though ... -Original Message- From: Vazquez Vegas, Sergio [mailto:[EMAIL PROTECTED]] Sent: October 11, 2002 3:30 AM To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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.
Re: Antwort: Backing Up Open Files
You can, but that doesn't guarantee you a "good" copy of the file, but a "fuzzy" copy. It also doesn't get you any files that are exclusively opened by an application. You'll need Open File Manager from St. Bernard Software for this. When OFM recognizes a backup function starting on a disk, it syncronizes the disk with a cache so that any new writes go to the file, but the original data (time-zero) is placed in the cache. So when the backup program reads the file, any changed data is ignored and OFM hands the backup program the original data from the cache. We have a client that is using OFM on lots of SQLServer boxes to backup the active databases without having to bring SQL down. Not an ideal backup solution, but OFM is working just fine. Make sure that you use the latest OFM release and check for compatibility issues with your virus software. Just a couple things we ran into. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of Sascha Braeuning Sent: Friday, October 11, 2002 4:54 AM To: [EMAIL PROTECTED] Subject: Antwort: Backing Up Open Files Hello, you can use a different managementclass and then the option copy serialization dynamic in the backup copy group. Tivoli then backs up the file at the first attempt if it is open or not! MfG/regards Sascha Brduning Sparkassen Informatik, Fellbach OrgEinheit: 6322 Wilhelm-Pfitzer Str. 1 70736 Fellbach Telefon: (0711) 5722-2144 Telefax: (0711) 5722-1634 Mailadr.: [EMAIL PROTECTED] =
Antwort: Backing Up Open Files
Hello, you can use a different managementclass and then the option copy serialization dynamic in the backup copy group. Tivoli then backs up the file at the first attempt if it is open or not! MfG/regards Sascha Bräuning Sparkassen Informatik, Fellbach OrgEinheit: 6322 Wilhelm-Pfitzer Str. 1 70736 Fellbach Telefon: (0711) 5722-2144 Telefax: (0711) 5722-1634 Mailadr.: [EMAIL PROTECTED]
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 [EMAIL PROTECTED] 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.
Re: Backing up open files under NT?
Yeah, I apologize for implying that the registry is not backed up. It is, just not in the normal fashion. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (719) 260-5991 Email: [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Richard Sims Sent: Monday, August 14, 2000 2:13 PM To: [EMAIL PROTECTED] Subject: Re: Backing up open files under NT? >However, within NT some files cannot be backed up while open. Registry >files are in this category. A good reference for this topic is the redbook "Windows NT Backup and Recovery with ADSM" (SG24-2231). Topic 4.1.2.1 Registry Backup nicely explains this area. *SM uses an NT-provided API to access the active registry files and copy them to an adsm.sys directory, whereas one should exclude the system32\config Registry area per se. *SM then backs up the copies of the Registry files from the adsm.sys directory. Per the BACKUPRegistry option default, the Registry is always backed up. Richard Sims, not an NT expert, BU
Re: Backing up open files under NT?
> I'm a fairly new ADSM admin with a Unix background, and the NT team has been > insisting that ADSM doesn't backup > open files, and that an add-on product is required to do so. This seems > quite odd to me, but perhaps they know something I don't. > > OTOH, perhaps they have confused open files for running databases. > > How does ADSM handle open files under NT? Open files as such are not usually a problem with NT. ADSM will back them up and check to see if they changed while being read by ADSM. If need be, ADSM will retry the backup as many as four times in an attempt to get a version that did not change while being read. This is the default behavior. It is possible to configure ADSM for other behaviors. NT provides a mechanism by which a program that opens a file can request exclusive access to the file. Files opened in this way are a much more difficult problem than files opened without exclusive access. ADSM really cannot read the files. In my experience, three classes of files are commonly opened with exclusive access. The first is the files making up the registry. ADSM has a built-in circumvention for its inability to read these files. It uses an NT API to query the registry contents, writes files containing the same key/value pairs, and backs up those files. The second class is user profiles for users logged on when the ADSM backup is run. The NT administrators at my site regard this as a minor issue. In most cases where profiles are not backed up ADSM already has a backup that was up to date about 24 hours earlier. There are a few users who appear to never log off. They could end up with a much older version of their profiles or even the system default profile if we ever had to do a restore of user profiles. The third class is database files. As far as I know, there are three ways to handle these: 1.Shut the database down before the backup and restart it after the backup. 2.Buy an add-on product that uses database facilities to extract the database contents and send them to ADSM. 3.Use facilities of the database product to export the contents to flat files and have ADSM back up the flat files.
Re: Backing up open files under NT?
>However, within NT some files cannot be backed up while open. Registry >files are in this category. A good reference for this topic is the redbook "Windows NT Backup and Recovery with ADSM" (SG24-2231). Topic 4.1.2.1 Registry Backup nicely explains this area. *SM uses an NT-provided API to access the active registry files and copy them to an adsm.sys directory, whereas one should exclude the system32\config Registry area per se. *SM then backs up the copies of the Registry files from the adsm.sys directory. Per the BACKUPRegistry option default, the Registry is always backed up. Richard Sims, not an NT expert, BU
Re: Backing up open files under NT?
It depends. Within the backup/archive copy group within the server, you select the copy serialization you would like: if the client encounters an open file either: back it up - DYNAMIC Ignore it - STATIC try it a few times and then back it up - SHRDYNAMIC try it a few times and then ignore it - SHRSTATIC However, within NT some files cannot be backed up while open. Registry files are in this category. Outlook PST files are the same. So the TSM parameter may or may not help. St. Bernard has a package that will allow you to backup files that are open, even PST files. The question then becomes "can you restore a file that was backed up while open?" That you get to test. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (719) 260-5991 Email: [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Swan/TM Sent: Monday, August 14, 2000 12:15 PM To: [EMAIL PROTECTED] Subject: Backing up open files under NT? I'm a fairly new ADSM admin with a Unix background, and the NT team has been insisting that ADSM doesn't backup open files, and that an add-on product is required to do so. This seems quite odd to me, but perhaps they know something I don't. OTOH, perhaps they have confused open files for running databases. How does ADSM handle open files under NT?
Backing up open files under NT?
I'm a fairly new ADSM admin with a Unix background, and the NT team has been insisting that ADSM doesn't backup open files, and that an add-on product is required to do so. This seems quite odd to me, but perhaps they know something I don't. OTOH, perhaps they have confused open files for running databases. How does ADSM handle open files under NT?
