I think you should treat all skipped open files the same way. Unless you
know for sure that taking a backup of an open file is OK, I think OFS just
gives you a false warm and fuzzy feeling. Just because you get a backup
doesn't necessarily mean it's a GOOD backup. So now you're at D/R and that
critical file for the application that you've been successfully backing up
with OFS proves to be unusable after the restore.

Plus according to the latest client manual:

There are two snapshot providers that can be used for open file support:
LVSA and VSS (VSS is not supported on WindowsR XP). VSS is the recommended
solution, since it utilizes Microsoft's strategic snapshot solution. The
LVSA is provided for customers migrating from prior versions of TivoliR
Storage Manager, where LVSA was utilized, and as an alternative to VSS if
there are issues with using VSS.


The option is:

Snapshotproviderfs LVSA | VSS | NONE.

Bill Boyer


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Wanda Prather
Sent: Thursday, January 15, 2009 8:32 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Open File Support -Win2k3 32bit vs 64bit

Jason,

Before you go further down the OFS rabbit hole:

On Windows, it is rare to use OFS for  backups of MS apps like SQL.
Those files are in use by MS SQL.  Backing them up via OFS just gives you a
copy of a possibly unstable/inconsistent file that may not be usable on
restore.

When you see those skipped files on the daily report, your response should
be:

1) Find out what those files are
2) If they belong to a DB app, make sure the DB is being backed up through
an application-appropriate method.  For SQL, you can
     a)   use the SQL manager to dump the files into the \backups directory
on the box.  Those are flat files that are never locked, and TSM can back
them up just fine.
    b) If the DB's are too large to dump to flat files, implement the TSM
for SQL agent.
3) Once the DB files are backed up elsewhere appropriately, put an EXCLUDE
statement in the dsm.opt file (or a client option set on the server) so that
you don't get the skipped files msgs from the backup/archive client in your
daily report anymore.

W





On Wed, Jan 14, 2009 at 6:00 PM, Jason Clarke <JCL AT gwsc.vic.edu DOT au> 
wrote:

> Hi list,
>
> First post, new admin, thrown in the deep end :-)
>
> 5.4 server, 5.4 clients. New installs everywhere.
> Win2k3 64bit server, mixture of Win2k3,2k,XP,Linux clients.
>
> Going through the nightly Operational Report, I'm noticing that various
> files are not backed up due to being in use. They're all 64bit machines.
>
> When I did the client installs I made sure that Open File Support was
> installed. However, the 64bit installer appears to not have it.
>
> Funnily enough, the 64bit machines are the more important servers.
> SQL/FSMO Roles etc.
>
> Where do I look for more info regarding Open File support for 2k3 64bit,
> either enabling it, using it or installing it?
>
> Regards,
>
> Jason Clarke
> ------------------
> Network Manager
> Glen Waverley S.C.
> p 03 8805 6750
> m 0418 145 318
> e jcl AT gwsc.vic.edu DOT au
> Please consider the environment before printing this email.
>