Re: TSM/EE 6.3.5 has two dsmserv processes
Hi Adam, Thank you for that thorough and detailed explanation. I'd say 'guru' is not much of an exaggeration, if any. All best wishes, Keith
Re: TSM/EE 6.3.5 has two dsmserv processes
Hi Keith,
I work with Zoltan here at Virginia Commonwealth University -- not sure if
"guru" is an accurate description! :-)
Here are the processes that I'm seeing when I grep for 'dsmserv' after the
update is applied:
root@processor ~ # ps -ef | grep dsmserv
root 4202 1 0 11:01 ?00:00:00 su - tsminst1 -c
/opt/tivoli/tsm/server/bin/dsmserv -i /home/tsminst1 -q
tsminst1 4297 4202 0 11:01 ?00:00:06
/opt/tivoli/tsm/server/bin/dsmserv -i /home/tsminst1 -q
root 16081 4554 0 12:56 pts/100:00:00 grep --color=auto dsmserv
Initially, this looks problematic, however, let's take note of a couple of
things:
1. Looking first at PID 4202, this process is owned by the 'root' user,
and is using 'su' to instruct the command
'/opt/tivoli/tsm/server/bin/dsmserv -i /home/tsminst1 -q' to run as user
'tsminst1'
2. Now, the second item, which at first glance appears to be a duplicate
instance of the 'dsmserv' process, is actually the only 'real' instance of
the process that is running. The first item is not a process at all, but
rather the 'root' account telling 'dsmserv' to run as user 'tsminst1'
rather than as the 'root' user. This process, PID 4297, has a PPID (parent
PID) of '4202', which tells us that PID 4297 was spawned by PID 4202.
Notice that PID 4297 is owned by the 'tsminst1' user, and is running the
command '/opt/tivoli/tsm/server/bin/dsmserv -i /home/tsminst1 -q', which is
exactly what PID 4202 asked for.
3. PID 4202 will continue running until PID 4297 ('dsmserv') has stopped
running.
If you're curious about the nuts and bolts going on in the background, on
our TSM servers, we have a file in '/etc/init.d' called
'tsminst1_dsmser.rc'. In the 'start()' section of this file, there is a
line that passes some variables along to another file at
'/opt/tivoli/tsm/server/bin/rc.dsmserv' to bring up the TSM server
process. In our file, that line looks like this:
$prefix/tivoli/tsm/server/bin/rc.dsmserv -u $instance_user -i $instance_dir
-q >/dev/null 2>&1 &
So, '/etc/init.d/tsminst1_dsmserv.rc' is taking variables defined earlier
in the file, namely '$instance_user' and '$instance_dir', and passing them
through to '/opt/tivoli/tsm/server/bin/rc.dsmserv'. So, to see what that
file does once it gets the variables, let's take a look.
After doing some logic and some work, we eventually arrive at a block of
code at the bottom of the 'rc.dsmserv' file that looks like this:
if [ "$instanceUser" != "" ]; then
exec su - $instanceUser "-c /opt/tivoli/tsm/server/bin/dsmserv $cmdParms"
else
exec /opt/tivoli/tsm/server/bin/dsmserv $cmdParms
fi
Since '/etc/init.d/tsminst1_dsmserv.rc' passed a username that should own
the running instance of the TSM server ('tsminst1'), the variable
'$instanceUser' is NOT null, so we end up running the
exec su - $instanceUser "-c /opt/tivoli/tsm/server/bin/dsmserv $cmdParms"
line. If we'd not defined an instance user, we wouldn't pass the condition
on the IF statement, and we'd end up calling 'dsmserv' as 'root' instead,
as per the ELSE statement:
exec /opt/tivoli/tsm/server/bin/dsmserv $cmdParms
Note that, substituting the variable assignments for the variables
themselves, the 'exec su - $instanceUser...' line gives us exactly what we
see for, in my case, PID 4202 in the 'ps -ef' output.
Hope this helps! Best,
-- Adam
__
*J. Adam Craig*
Linux & Windows Operating Systems Engineer
VCU Computer Center
804.828.4886
"Don't be a phishing victim -- VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details,
visit http://infosecurity.vcu.edu/phishing.html";
On Fri, Dec 12, 2014 at 12:51 PM, Arbogast, Warren K
wrote:
>
> So Zoltan,
> What does your Linux guru have to say about the possible consequences of
> having the two processes running? Is it a neutral matter, or not?
>
> Thank you,
> Keith
Re: TSM/EE 6.3.5 has two dsmserv processes
> Op 12 dec. 2014, om 18:51 heeft Arbogast, Warren K het > volgende geschreven: > > So Zoltan, > What does your Linux guru have to say about the possible consequences of > having the two processes running? Is it a neutral matter, or not? > > Thank you, > Keith in the past there was such a small difference between threads and processes in Linux that all threads would show as processes in ps. To date there is apparently a way to distinguish one from the other, but the difference is still almost insignificant in terms of resource utilization. -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
Re: TSM/EE 6.3.5 has two dsmserv processes
So Zoltan, What does your Linux guru have to say about the possible consequences of having the two processes running? Is it a neutral matter, or not? Thank you, Keith
Re: TSM/EE 6.3.5 has two dsmserv processes
Hi Zoltan, My hat is off to your LInux guru. I did notice that the ulimit commands have been added to the dsmserv.rc file that comes with 6.3.5, but I had not put 2 and 2 together. Best wishes, Keith
Re: Drive preference in a mixed-media library sharing environment
I've never had a problem defining multiple TSM (logical) libraries on one device address (but I can't say I've tried it since 6.2, and that was on Windows). What you can't do is have one device class pointing to 2 different libraries, so you'll also have to do some juggling there, create some new devclasses and storage pools to use going forward. Wanda Prather TSM Consultant ICF International Cybersecurity Division -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Skylar Thompson Sent: Thursday, December 11, 2014 10:15 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Drive preference in a mixed-media library sharing environment Interesting. I hadn't considered using different libraries to solve this. It was a little unclear from the thread - does this require partitioning on the library side? I wasn't aware that two different libraries (presumably with two different paths) could share a single device special node. On Wed, Dec 10, 2014 at 06:23:10PM -0600, Roger Deschner wrote: > It won't work. I tried and failed in a StorageTek SL500 library with > LTO4 and LTO5. Just like you are reporting, the LTO4 tapes would get > mounted in the LTO5 drives first, and then there was no free drive in > which to mount a LTO5 tape. I tried all kinds of tricks to make it > work, but it did not work. > > Furthermore, despite claims of compatibility, I found that there was a > much higher media error rate when using LTO4 tapes in LTO5 drives, > compared to using the same LTO4 tapes in LTO4 drives. These were HP > drives. > > The only way around it is to define two libraries in TSM, one > consisting of the LTO5 drives and tapes, and the other consisting of > the LTO6 drives and tapes. Hopefully your LTO5 and LTO6 tapes can be > identified by unique sequences of volsers, e.g. L50001 versus L60001, > which will greatly simplify TSM CHECKIN commands, because then you can > use ranges instead of specifying lists of individual volsers. To check > tapes into that mixed-media library I use something like > VOLRANGE=L5,L5 on the CHECKIN and LABEL commands to make sure > the right tapes get checked into the right TSM Library. Fortunately > the different generations of tape cartridges are different colors. > > You can read all about what I went through, and the good, helpful > recommendations from others on this list, by searching the ADSM-L > archives for "UN-mixing LTO-4 and LTO-5". Thanks again to Remco Post > and Wanda Prather for their help back then in 2012! > > Roger Deschner University of Illinois at Chicago rog...@uic.edu > ==I have not lost my mind -- it is backed up on tape > somewhere.= > > > On Wed, 10 Dec 2014, Grant Street wrote: > > >On 10/12/14 02:40, Skylar Thompson wrote: > >> Hi folks, > >> > >> We have two TSM 6.3.4.300 servers connected to a STK SL3000 with 8x > >> LTO5 drives, and 8x LTO6 drives. One of the TSM servers is the > >> library manager, and the other is a client. I'm seeing odd behavior > >> when the client requests mounts from the server. My understanding > >> is that a mount request for a volume will be placed preferentially > >> in the least-capable drive for that volume; that is, a LTO5 volume > >> mounted for write will be placed in a LTO5 drive if it's available, > >> and in a LTO6 drive if no LTO5 drives are available. > >> > >> What I'm seeing is that LTO5 volumes are ending up in LTO6 drives > >> first, even with no LTO5 drives in use at all. I've verified that > >> all the LTO5 drives and paths are online for both servers. > >> > >> I haven't played with MOUNTLIMIT yet, but I don't think it'll do > >> any good since I think that still depends on the mounts ending up > >> in the least-capable drives first. > >> > >> Any thoughts? > >> > >> -- > >> -- Skylar Thompson (skyl...@u.washington.edu) > >> -- Genome Sciences Department, System Administrator > >> -- Foege Building S046, (206)-685-7354 > >> -- University of Washington School of Medicine > >might be a stab in the dark . try numbering the drives such that > >the LTO5's are first in the drive list or vice versa. > >That way when tsm "scans" for an available drive it will always try > >the LTO5's first. > > > >HTH > > > >Grant > > -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine
Re: TSM/EE 6.3.5 has two dsmserv processes
My Linux guru has figured it out. IBM changed the *rc.dsmserv* script in /opt/tivoli/tsm/server/bin to start dsmserv using the command "*su exec*" versus just "*exec*". I think it is related to this apar: http://www-01.ibm.com/support/docview.wss?uid=swg1IC90127 On Fri, Dec 12, 2014 at 10:09 AM, Zoltan Forray wrote: > I just upgraded a Linux server from 6.3.4.200 to 6.3.5.100 and also see > 2-dsmserv processes: > > # ps -ef | grep dsmse > root 3008 1 0 10:05 pts/100:00:00 su - tsminst1 -c > /opt/tivoli/tsm/server/bin/dsmserv -i /home/tsminst1 -q > tsminst1 3103 3008 0 10:05 ?00:00:00 > /opt/tivoli/tsm/server/bin/dsmserv -i /home/tsminst1 -q > > Has anyone determined if this is the new "normal"? > > > > > On Thu, Dec 11, 2014 at 2:50 PM, David Bronder > wrote: > >> Keith, >> >> I'm running 6.3.5 on AIX, not RHEL, but I see only one dsmserv process. >> It's >> possible something on the RHEL version changed at 6.3.5. >> >> One thing I used to do in TSM 5 and earlier was add an "exec" to the >> rc.dsmserv start script so it wouldn't leave the invoking rc script shell >> lying around. IBM seemed to finally figure that out with 6.3.4, since >> they >> did the same thing in that version (maybe in earlier TSM 6, too; I went >> from >> 5.5 to 6.3.4). On 6.3.5 for AIX, the exec is still there, too. Maybe it >> got >> dropped somehow on the RHEL version of 6.3.5? >> >> =Dave >> >> >> On 12/11/2014 12:48 PM, Arbogast, Warren K wrote: >> > I just updated a test TSM server from 6.3.4 to 6.3.5 on RHEL6. The >> post-startup behavior of dsmserv seems to be diferrent. >> > >> > __Our other 6.3.4 servers show one dsmserv process on a process list; >> like this: ps -ef | grep dsm >> > tsm 16782 1 99 Nov28 ?29-07:37:33 >> /opt/tivoli/tsm/server/bin/dsmserv -u tsm -i /home/tsmbl01/tsm -q >> > >> > __The 6.3.5 server shows two dsmserv processes; the first one, owned by >> root, starts the second dsmserv process after 'su'ing to the instance >> owner, but, the first process continues running. >> > >> > root 103721 0 12:46 pts/000:00:00 su - tsm >> -c /opt/tivoli/tsm/server/bin/dsmserv -i /home/tsm/tsm -q >> > tsm 10466 10372 0 12:46 ?00:00:04 >> /opt/tivoli/tsm/server/bin/dsmserv -i /home/tsm/tsm -q >> > >> > __Is this new behavior, that the process owned by root continues >> running after starting the process owned by the instance owner? Or, did I >> overlook a configuration or permssion setting somewhere? >> > >> > Thank you, >> > Keith Arbogast >> > Indiana University >> > >> > >> >> -- >> Hello World.David Bronder - Systems >> Architect >> Segmentation Fault ITS-EI, Univ. of >> Iowa >> Core dumped, disk trashed, quota filled, soda warm. >> david-bron...@uiowa.edu >> > > > > -- > *Zoltan Forray* > TSM Software & Hardware Administrator > BigBro / Hobbit / Xymon Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > zfor...@vcu.edu - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://infosecurity.vcu.edu/phishing.html > -- *Zoltan Forray* TSM Software & Hardware Administrator BigBro / Hobbit / Xymon Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: TSM/EE 6.3.5 has two dsmserv processes
I just upgraded a Linux server from 6.3.4.200 to 6.3.5.100 and also see 2-dsmserv processes: # ps -ef | grep dsmse root 3008 1 0 10:05 pts/100:00:00 su - tsminst1 -c /opt/tivoli/tsm/server/bin/dsmserv -i /home/tsminst1 -q tsminst1 3103 3008 0 10:05 ?00:00:00 /opt/tivoli/tsm/server/bin/dsmserv -i /home/tsminst1 -q Has anyone determined if this is the new "normal"? On Thu, Dec 11, 2014 at 2:50 PM, David Bronder wrote: > Keith, > > I'm running 6.3.5 on AIX, not RHEL, but I see only one dsmserv process. > It's > possible something on the RHEL version changed at 6.3.5. > > One thing I used to do in TSM 5 and earlier was add an "exec" to the > rc.dsmserv start script so it wouldn't leave the invoking rc script shell > lying around. IBM seemed to finally figure that out with 6.3.4, since they > did the same thing in that version (maybe in earlier TSM 6, too; I went > from > 5.5 to 6.3.4). On 6.3.5 for AIX, the exec is still there, too. Maybe it > got > dropped somehow on the RHEL version of 6.3.5? > > =Dave > > > On 12/11/2014 12:48 PM, Arbogast, Warren K wrote: > > I just updated a test TSM server from 6.3.4 to 6.3.5 on RHEL6. The > post-startup behavior of dsmserv seems to be diferrent. > > > > __Our other 6.3.4 servers show one dsmserv process on a process list; > like this: ps -ef | grep dsm > > tsm 16782 1 99 Nov28 ?29-07:37:33 > /opt/tivoli/tsm/server/bin/dsmserv -u tsm -i /home/tsmbl01/tsm -q > > > > __The 6.3.5 server shows two dsmserv processes; the first one, owned by > root, starts the second dsmserv process after 'su'ing to the instance > owner, but, the first process continues running. > > > > root 103721 0 12:46 pts/000:00:00 su - tsm -c > /opt/tivoli/tsm/server/bin/dsmserv -i /home/tsm/tsm -q > > tsm 10466 10372 0 12:46 ?00:00:04 > /opt/tivoli/tsm/server/bin/dsmserv -i /home/tsm/tsm -q > > > > __Is this new behavior, that the process owned by root continues running > after starting the process owned by the instance owner? Or, did I overlook > a configuration or permssion setting somewhere? > > > > Thank you, > > Keith Arbogast > > Indiana University > > > > > > -- > Hello World.David Bronder - Systems > Architect > Segmentation Fault ITS-EI, Univ. of > Iowa > Core dumped, disk trashed, quota filled, soda warm. > david-bron...@uiowa.edu > -- *Zoltan Forray* TSM Software & Hardware Administrator BigBro / Hobbit / Xymon Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Backing up SystemState issues on Windows 2008 x32 SP2 box
Zoltan,
In this case, the vssadmin list shadowstorage results are not
deterministic; I am guessing that maybe successful shadows have not been
created, else I'd have expected it to show something (even there are no
current shadow copies).
If you haven't examined the windows event logs, it would be good to do
that. Normally with VSS related operations, I would expect the event logs
(application and / or system) to show some kind of errors besides just TSM
generated messages, around the time of the backup.
You can also try to use the diskshadow utility to test basic shadow copy
creation functionality. This might help further isolate the problem, e.g.,
remove TSM from the equation if it is an issue with the OS:
1. Create a plain text file (I called mine "script.ds") with this content:
set metadata testshadow.cab
set verbose on
begin backup
add volume c: alias testshadow
create
list shadows all
end backup
list shadows all
2. Run the script like this, from an OS prompt (cmd.exe):
diskshadow /s script.ds /l script.out
On screen you will see the diskshadow output, and it will also be saved to
script.out. The shadow copy will be only temporary, it will be deleted
(just the test shadow copy) when the script completes, as the second "list
shadows all" in the script will show.
In my case, the output is shown below. Does this work for you?
Note: When you are done, you can delete the testshadow.cab file. It is
created in the same directory from which you launched the diskshadow
command.
Note: If this is a production system, consider running the test off-hours,
or doing it on a test system that exhibits the same problem.
-- BEGIN OUTPUT --
C:\>diskshadow /s script.ds /l script.out
Microsoft DiskShadow version 1.0
Copyright (C) 2007 Microsoft Corporation
On computer: WIN2008R2ENT, 12/12/2014 9:34:08 AM
-> set metadata testshadow.cab
-> set verbose on
-> begin backup
-> add volume c: alias testshadow
-> create
Excluding writer "Shadow Copy Optimization Writer", because all of its
components have been excluded.
Excluding writer "SqlServerWriter", because all of its components have been
excluded.
* Including writer "Task Scheduler Writer":
+ Adding component: \TasksStore
* Including writer "VSS Metadata Store Writer":
+ Adding component: \WriterMetadataStore
* Including writer "Performance Counters Writer":
+ Adding component: \PerformanceCounters
* Including writer "WMI Writer":
+ Adding component: \WMI
* Including writer "COM+ REGDB Writer":
+ Adding component: \COM+ REGDB
* Including writer "System Writer":
+ Adding component: \System Files
* Including writer "ASR Writer":
+ Adding component: \ASR\ASR
+ Adding component: \Volumes\Volume
{d1e1e243-2cb2-11e4-bf09-806e6f6e6963}
+ Adding component: \Disks\harddisk0
+ Adding component: \BCD\BCD
* Including writer "Registry Writer":
+ Adding component: \Registry
Alias testshadow for shadow ID {745d60db-07a6-46e3-8c16-a11810b5e682} set
as environment variable.
Alias VSS_SHADOW_SET for shadow set ID
{ad4ab0df-225a-4c7f-9b33-af7da466bda8} set as environment variable.
Inserted file Manifest.xml into .cab file testshadow.cab
Inserted file BCDocument.xml into .cab file testshadow.cab
Inserted file WM0.xml into .cab file testshadow.cab
Inserted file WM1.xml into .cab file testshadow.cab
Inserted file WM2.xml into .cab file testshadow.cab
Inserted file WM3.xml into .cab file testshadow.cab
Inserted file WM4.xml into .cab file testshadow.cab
Inserted file WM5.xml into .cab file testshadow.cab
Inserted file WM6.xml into .cab file testshadow.cab
Inserted file WM7.xml into .cab file testshadow.cab
Inserted file WM8.xml into .cab file testshadow.cab
Inserted file WM9.xml into .cab file testshadow.cab
Inserted file script.out into .cab file testshadow.cab
Querying all shadow copies with the shadow copy set ID
{ad4ab0df-225a-4c7f-9b33-af7da466bda8}
* Shadow copy ID = {745d60db-07a6-46e3-8c16-a11810b5e682}
%testshadow%
- Shadow copy set: {ad4ab0df-225a-4c7f-9b33-af7da466bda8}
%VSS_SHADOW_SET%
- Original count of shadow copies = 1
- Original volume name: \\?\Volume
{d1e1e243-2cb2-11e4-bf09-806e6f6e6963}\ [C:\]
- Creation time: 12/12/2014 9:34:20 AM
- Shadow copy device name: \\?\GLOBALROOT\Device
\HarddiskVolumeShadowCopy6
- Originating machine: WIN2008R2ENT
- Service machine: WIN2008R2ENT
- Not exposed
- Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes: Auto_Release Differential
Number of shadow copies listed: 1
-> list shadows all
Querying all shadow copies on the computer ...
* Shadow copy ID = {745d60db-07a6-46e3-8c16-a11810b5e682}
%testshadow%
- Shadow copy set: {ad4ab0df-225a-4c7f-9b33-af7da466bda8}
%VSS_SHADOW_SET%
- Original count of
Re: Backing up SystemState issues on Windows 2008 x32 SP2 box
Andy,
As always, we greatly appreciate your Windows expertise.
The OS owner says running the "vssadmin list shadowstorage" results in "No
items found that satisfy the query" - Shadow Copies is disabled on both
servers
So, I gather that Shadow Copies is required to perform SystemState backups?
On Fri, Dec 12, 2014 at 7:18 AM, Andrew Raibeck wrote:
> Hi Zoltan,
>
> Some random thoughts:
>
> * Check the Windows OS application and system event logs for more details.
> If something is going haywire in VSS, it is possible some clues could be
> found there.
>
> * Run the command:
>
>vssadmin list providers
>
> On my Windows 7 system, for example, output looks like this:
>
>C:\>vssadmin list providers
>vssadmin 1.1 - Volume Shadow Copy Service administrative command-line
> tool
>(C) Copyright 2001-2005 Microsoft Corp.
>
>Provider name: 'Microsoft Software Shadow Copy provider 1.0'
> Provider type: System
> Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
> Version: 1.0.0.7
>
> This is the "system" provider that comes with all Windows operating systems
> and, generally speaking, is the one that should be used to back up system
> state. If you have more than one provider installed -- a hardware provider
> or maybe another software provider -- then maybe that provider is
> configured as the default provider but does not work well for system state.
> In that case, you can try adding this option to dsm.opt:
>
>vssusesystemprovider yes
>
> This would force TSM to use the Microsoft system provider even if the OS is
> configured to use a different provider as the default.
>
> * Run the command:
>
>vssadmin list shadowstorage
>
> And make sure there is sufficient space for shadow copy creation.
>
> * Check if you have any other products installed that might be taking
> snapshots at the same time, as this could cause conflicts in the OS that
> prevent successful snapshot creation.
>
> * If all else fails, open a PMR with support so we can explore this in more
> depth.
>
> Regards,
>
> - Andy
>
>
>
>
> Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead |
> stor...@us.ibm.com
>
> IBM Tivoli Storage Manager links:
> Product support:
>
> http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager
>
> Online documentation:
> http://www.ibm.com/support/knowledgecenter/SSGSG7/welcome
> Product Wiki:
>
> https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager
>
> "ADSM: Dist Stor Manager" wrote on 2014-12-11
> 16:16:06:
>
> > From: Zoltan Forray
> > To: ADSM-L@VM.MARIST.EDU
> > Date: 2014-12-11 16:17
> > Subject: Backing up SystemState issues on Windows 2008 x32 SP2 box
> > Sent by: "ADSM: Dist Stor Manager"
> >
> > The OS owner sent me this. Any suggestions on how to narrow down /
> resolve
> > this? My thought was to have them push for W2K8 R2 but I know there are
> > some applications that have issues with R2.
> >
> > *The PentanaPAWS servers are both having issues with backing up the
> system
> > data. Restarting the VSS services sometimes fixes the issue but it’s
> never
> > a finalize solution. Do you have any insight on what can be done to fix
> > this problem? I have attached the dsmerror.log. To temporary fix the
> > issue, I have been restarting the VSS services having issues but it’s
> only
> > a temporary fix. Upgrading the TSM client to 7.1.1.0 didn’t fix the
> > problem.*
> >
> >
> >
> > *PENTANAPAWS8VM*
> >
> > *12/10/2014 00:51:52 ANS5250E An unexpected error was encountered.*
> >
> > * TSM function name : BaStartSnapshot*
> >
> > * TSM function : failed to start the snapshot*
> >
> > * TSM return code : -1*
> >
> > * TSM file : ..\..\common\ba\backsnap.cpp (6730)*
> >
> > *12/10/2014 00:51:53 ANS5283E The operation was unsuccessful.*
> >
> > *12/10/2014 00:51:53 ANS1327W The snapshot operation for
> > 'PENTANAPAWS8VM\SystemState\NULL\System State\SystemState' failed with
> > error code: -1.*
> >
> > *12/10/2014 00:51:54 ANS1228E Sending of object
> > 'PENTANAPAWS8VM\SystemState\NULL\System State\SystemState' failed.*
> >
> > *12/10/2014 00:51:54 ANS5283E The operation was unsuccessful.*
> >
> >
> >
> > *12/10/2014 00:52:20 ANS1512E Scheduled event 'ADMINSYSTEMS' failed.
> > Return code = 12.*
> >
> >
> >
> >
> >
> > *PENTANAPAWS8VMDEV*
> >
> > *12/09/2014 14:44:17 ANS2250W A TSM core file or crash report was found:
> > C:\Program Files\Tivoli\TSM\baclient\dsmcrash.dmp*
> >
> > *12/10/2014 00:35:16 ANS5250E An unexpected error was encountered.*
> >
> > * TSM function name : BaStartSnapshot*
> >
> > * TSM function : failed to start the snapshot*
> >
> > * TSM return code : -1*
> >
> > * TSM file : ..\..\common\ba\backsnap.cpp (6730)*
> >
> > *12/10/2014 00:35:17 ANS5283E The operation was unsuccessful.*
> >
> > *12/10/2014 00:35:17 ANS1327W The snapshot oper
Re: VSS & SystemState issues
It's look like VSS writers issue,check the vss writers status, are they in failed or waiting for completion state,if the writers are not stable,then windows team have to check or most of the time server reboot will fix the vss writers issue,Hence check with your Wintel team. Regards, Gopikrishna Bangalore On Thu, Dec 11, 2014 at 10:56 PM, Srikanth Kola23 wrote: > > Hi Team, > > Can you Guys Please forward me the solutions which you have got for > different VSS Issues and system state issues you faced . So that it will > be help full @@Thanks@@ > > Thanks & Regards, > > Srikanth kola > Backup & Recovery > IBM India Pvt Ltd, Chennai > Mobile: +91 9885473450 > > > > From: Zoltan Forray > To: ADSM-L@VM.MARIST.EDU > Date: 12/12/2014 02:48 AM > Subject:[ADSM-L] Backing up SystemState issues on Windows 2008 x32 > SP2 box > Sent by:"ADSM: Dist Stor Manager" > > > > The OS owner sent me this. Any suggestions on how to narrow down / > resolve > this? My thought was to have them push for W2K8 R2 but I know there are > some applications that have issues with R2. > > *The PentanaPAWS servers are both having issues with backing up the system > data. Restarting the VSS services sometimes fixes the issue but it’s > never > a finalize solution. Do you have any insight on what can be done to fix > this problem? I have attached the dsmerror.log. To temporary fix the > issue, I have been restarting the VSS services having issues but it’s only > a temporary fix. Upgrading the TSM client to 7.1.1.0 didn’t fix the > problem.* > > > > *PENTANAPAWS8VM* > > *12/10/2014 00:51:52 ANS5250E An unexpected error was encountered.* > > * TSM function name : BaStartSnapshot* > > * TSM function : failed to start the snapshot* > > * TSM return code : -1* > > * TSM file : ..\..\common\ba\backsnap.cpp (6730)* > > *12/10/2014 00:51:53 ANS5283E The operation was unsuccessful.* > > *12/10/2014 00:51:53 ANS1327W The snapshot operation for > 'PENTANAPAWS8VM\SystemState\NULL\System State\SystemState' failed with > error code: -1.* > > *12/10/2014 00:51:54 ANS1228E Sending of object > 'PENTANAPAWS8VM\SystemState\NULL\System State\SystemState' failed.* > > *12/10/2014 00:51:54 ANS5283E The operation was unsuccessful.* > > > > *12/10/2014 00:52:20 ANS1512E Scheduled event 'ADMINSYSTEMS' failed. > Return code = 12.* > > > > > > *PENTANAPAWS8VMDEV* > > *12/09/2014 14:44:17 ANS2250W A TSM core file or crash report was found: > C:\Program Files\Tivoli\TSM\baclient\dsmcrash.dmp* > > *12/10/2014 00:35:16 ANS5250E An unexpected error was encountered.* > > * TSM function name : BaStartSnapshot* > > * TSM function : failed to start the snapshot* > > * TSM return code : -1* > > * TSM file : ..\..\common\ba\backsnap.cpp (6730)* > > *12/10/2014 00:35:17 ANS5283E The operation was unsuccessful.* > > *12/10/2014 00:35:17 ANS1327W The snapshot operation for > 'PENTANAPAWS8VMD\SystemState\NULL\System State\SystemState' failed with > error code: -1.* > > *12/10/2014 00:35:18 ANS1228E Sending of object > 'PENTANAPAWS8VMD\SystemState\NULL\System State\SystemState' failed.* > > *12/10/2014 00:35:18 ANS5283E The operation was unsuccessful.* > > > > *12/10/2014 00:36:24 ANS1512E Scheduled event 'ADMINSYSTEMS' failed. > Return code = 12.* > > *12/10/2014 23:47:19 ANS5250E An unexpected error was encountered.* > > * TSM function name : BaStartSnapshot* > > * TSM function : failed to start the snapshot* > > * TSM return code : -1* > > * TSM file : ..\..\common\ba\backsnap.cpp (6730)* > > *12/10/2014 23:47:20 ANS5283E The operation was unsuccessful.* > > *12/10/2014 23:47:20 ANS1327W The snapshot operation for > 'PENTANAPAWS8VMD\SystemState\NULL\System State\SystemState' failed with > error code: -1.* > > *12/10/2014 23:47:21 ANS1228E Sending of object > 'PENTANAPAWS8VMD\SystemState\NULL\System State\SystemState' failed.* > > *12/10/2014 23:47:21 ANS5283E The operation was unsuccessful.* > > > > *12/10/2014 23:47:56 ANS1512E Scheduled event 'ADMINSYSTEMS' failed. > Return code = 12.* > > > -- > *Zoltan Forray* > TSM Software & Hardware Administrator > BigBro / Hobbit / Xymon Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > zfor...@vcu.edu - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://infosecurity.vcu.edu/phishing.html > > > >
Re: Backing up SystemState issues on Windows 2008 x32 SP2 box
Hi Zoltan,
Some random thoughts:
* Check the Windows OS application and system event logs for more details.
If something is going haywire in VSS, it is possible some clues could be
found there.
* Run the command:
vssadmin list providers
On my Windows 7 system, for example, output looks like this:
C:\>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001-2005 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
This is the "system" provider that comes with all Windows operating systems
and, generally speaking, is the one that should be used to back up system
state. If you have more than one provider installed -- a hardware provider
or maybe another software provider -- then maybe that provider is
configured as the default provider but does not work well for system state.
In that case, you can try adding this option to dsm.opt:
vssusesystemprovider yes
This would force TSM to use the Microsoft system provider even if the OS is
configured to use a different provider as the default.
* Run the command:
vssadmin list shadowstorage
And make sure there is sufficient space for shadow copy creation.
* Check if you have any other products installed that might be taking
snapshots at the same time, as this could cause conflicts in the OS that
prevent successful snapshot creation.
* If all else fails, open a PMR with support so we can explore this in more
depth.
Regards,
- Andy
Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead |
stor...@us.ibm.com
IBM Tivoli Storage Manager links:
Product support:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager
Online documentation:
http://www.ibm.com/support/knowledgecenter/SSGSG7/welcome
Product Wiki:
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager
"ADSM: Dist Stor Manager" wrote on 2014-12-11
16:16:06:
> From: Zoltan Forray
> To: ADSM-L@VM.MARIST.EDU
> Date: 2014-12-11 16:17
> Subject: Backing up SystemState issues on Windows 2008 x32 SP2 box
> Sent by: "ADSM: Dist Stor Manager"
>
> The OS owner sent me this. Any suggestions on how to narrow down /
resolve
> this? My thought was to have them push for W2K8 R2 but I know there are
> some applications that have issues with R2.
>
> *The PentanaPAWS servers are both having issues with backing up the
system
> data. Restarting the VSS services sometimes fixes the issue but it’s
never
> a finalize solution. Do you have any insight on what can be done to fix
> this problem? I have attached the dsmerror.log. To temporary fix the
> issue, I have been restarting the VSS services having issues but it’s
only
> a temporary fix. Upgrading the TSM client to 7.1.1.0 didn’t fix the
> problem.*
>
>
>
> *PENTANAPAWS8VM*
>
> *12/10/2014 00:51:52 ANS5250E An unexpected error was encountered.*
>
> * TSM function name : BaStartSnapshot*
>
> * TSM function : failed to start the snapshot*
>
> * TSM return code : -1*
>
> * TSM file : ..\..\common\ba\backsnap.cpp (6730)*
>
> *12/10/2014 00:51:53 ANS5283E The operation was unsuccessful.*
>
> *12/10/2014 00:51:53 ANS1327W The snapshot operation for
> 'PENTANAPAWS8VM\SystemState\NULL\System State\SystemState' failed with
> error code: -1.*
>
> *12/10/2014 00:51:54 ANS1228E Sending of object
> 'PENTANAPAWS8VM\SystemState\NULL\System State\SystemState' failed.*
>
> *12/10/2014 00:51:54 ANS5283E The operation was unsuccessful.*
>
>
>
> *12/10/2014 00:52:20 ANS1512E Scheduled event 'ADMINSYSTEMS' failed.
> Return code = 12.*
>
>
>
>
>
> *PENTANAPAWS8VMDEV*
>
> *12/09/2014 14:44:17 ANS2250W A TSM core file or crash report was found:
> C:\Program Files\Tivoli\TSM\baclient\dsmcrash.dmp*
>
> *12/10/2014 00:35:16 ANS5250E An unexpected error was encountered.*
>
> * TSM function name : BaStartSnapshot*
>
> * TSM function : failed to start the snapshot*
>
> * TSM return code : -1*
>
> * TSM file : ..\..\common\ba\backsnap.cpp (6730)*
>
> *12/10/2014 00:35:17 ANS5283E The operation was unsuccessful.*
>
> *12/10/2014 00:35:17 ANS1327W The snapshot operation for
> 'PENTANAPAWS8VMD\SystemState\NULL\System State\SystemState' failed with
> error code: -1.*
>
> *12/10/2014 00:35:18 ANS1228E Sending of object
> 'PENTANAPAWS8VMD\SystemState\NULL\System State\SystemState' failed.*
>
> *12/10/2014 00:35:18 ANS5283E The operation was unsuccessful.*
>
>
>
> *12/10/2014 00:36:24 ANS1512E Scheduled event 'ADMINSYSTEMS' failed.
> Return code = 12.*
>
> *12/10/2014 23:47:19 ANS5250E An unexpected error was encountered.*
>
> * TSM function name : BaStartSnapshot*
>
> * TSM function : failed to start the snapshot*
>
> * TSM return code : -1*
>
> * TSM file :
Re: Windows Client OS Level decoded
Hi Zoltan, TSM uses the version of Windows as reported by Windows API functions. Although Microsoft uses product names such as "Windows Server 2008 R2" and "Windows Vista", under the covers, the OS uses numeric version, release, and build numbers that bear no apparent relationship to the externalized product name. You can see this by going to an OS command prompt (cmd.exe) and running this command: ver For example, from a Windows 7 machine: C:\>ver Microsoft Windows [Version 6.1.7601] C:\> This is version 6, release 1, build 7601. Thus TSM would report Windows 7 as version 6.1 (TSM does not report the build number). See http://msdn.microsoft.com/en-us/library/windows/desktop/ms724832%28v=vs.85%29.aspx for a more definitive reference that shows how OS names map to internal version.release numbers. Regards, - Andy Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: http://www.ibm.com/support/knowledgecenter/SSGSG7/welcome Product Wiki: https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager "ADSM: Dist Stor Manager" wrote on 2014-12-11 15:58:43: > From: Zoltan Forray > To: ADSM-L@VM.MARIST.EDU > Date: 2014-12-11 15:59 > Subject: Windows Client OS Level decoded > Sent by: "ADSM: Dist Stor Manager" > > Does some one have a complete list/magic decoder ring that translates the > Windows OS level to the TSM OS Client Level > > I found this: > > http://patrickv.info/wordpress/2011/09/tsm-windows-client-os-level- > demystified/ > > Has anyone seen the 7.1.1.1 update to the x32 client - only see an x64 > version. > > -- > *Zoltan Forray* > TSM Software & Hardware Administrator > BigBro / Hobbit / Xymon Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > zfor...@vcu.edu - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://infosecurity.vcu.edu/phishing.html >
