Thanks for the feedback, I am going to open a case with IBM to get their input.
You may be right on why the files do not show up as eligible backup/restore
objects, when I thought of that being a possibility I immediately ruled it out
as they are not located on the OS system drive.
I will update the thread once IBM has ruled on the issue....
Rick
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Schaub, Steve
Sent: Monday, June 30, 2014 5:01 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Files not listed as backup object
Rick,
We have had to work around this issue regularly on certain types of app
servers. If your situation is the same as ours, here is the scenario:
1. An app installs on the server in such a way that the Windows O/S flags
certain files (usually .exe or .dll) as belonging to the systemstate.
2. When TSM goes to perform a normal file-level backup, it interacts with
Windows, and is told "don't even consider this file, it is part of the
systemstate"
3. TSM happily ignores the existence of the file, doesn't back it up or even
report it 4. When you need that file back, the only way to get it is by
restoring the systemstate Of course, when you mount the drive to your desktop,
your O/S only sees it as a normal file, so it allows TSM to back it up.
In our case, it has bit us more than once on DR tests, because the app files
were located on a data drive, and even though we were taking BMR backups of the
O/S drive, the inability to restore these few files on data drives meant
certain apps/services would not work.
One more reason I feel the days of file-level backups making sense are over.
-steve schaub
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Rick Adamson
Sent: Friday, June 27, 2014 11:25 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Files not listed as backup object
Performed a restore and the customer complained that files were missing.
Research showed that the file does exist on the file system but is not
available to restore (active or inactive).
When I enable a trace and try to back it up with either the GUI or CLI the TSM
client reports that the file is not found.
This is where it gets strange, if I map the drive to my desktop my client finds
the file and backs it up.
I have checked the client and server excludes, the registry, as well as run a
file trace and cannot ID the cause.
Here is a partial directory listing that lists one of the file names affected
(HyS9FoundationServices.exe)
07/03/2012 09:38 AM <DIR> .
07/03/2012 09:38 AM <DIR> ..
06/22/2012 12:52 PM 239,616 HyS9FoundationServices.exe
06/22/2012 12:52 PM 239,616 HyS9RaFramework.exe
06/29/2012 08:39 AM <DIR> nodemanager
06/29/2012 08:39 AM 1,087 processBootProperties.cmd
06/29/2012 08:39 AM 897 processBootProperties.sh
06/29/2012 08:39 AM 1,315 secureWebLogic.bat
06/29/2012 08:39 AM <DIR> server_migration
06/29/2012 08:39 AM <DIR> service_migration
When I attempt to back it up with trace enabled I receive:
Selective Backup function invoked.
ANS1016I No eligible files matching '\\hypgp01hdqww\g$\Oracle\Middleware\user_pr
ojects\domains\EPMSystem\bin\HyS9FoundationServices.exe' were found.
Selective Backup processing of '\\hypgp01hdqww\g$\Oracle\Middleware\user_project
s\domains\EPMSystem\bin\HyS9FoundationServices.exe' finished without failure.
All thoughts and feedback appreciated !
~Rick Adamson
-----------------------------------------------------
Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer: http://www.bcbst.com/email_disclaimer.shtm
|
