Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Boot\s+Path\s+Not\s+Found\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Boot\s+Path\s+Not\s+Found\s*$/: 5 ]

Total 5 documents matching your query.

1. Re: [ADSM-L] Boot Path Not Found (score: 1): Author: "Kinder, Kevin P" <Kevin.P.Kinder AT WV DOT GOV>; Date: Mon, 3 Jun 2013 11:14:03 -0400; I had already done all of these troubleshooting steps (as well as some others), but here are the particulars: q sched f=d: Policy Domain Name: SERVER_SEVEN_DAY_POOL_1 Schedule Name: NORMAL_DAILY Desc; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2013-06/msg00001.html (15,546 bytes)
2. [ADSM-L] Boot Path Not Found (score: 1): Author: "Kinder, Kevin P" <Kevin.P.Kinder AT WV DOT GOV>; Date: Thu, 30 May 2013 13:49:24 -0400; TSM 5.5.1.0 Windows client backing up to TSM running on z\OS. The TSM client software is running on Windows Server 2007 SP2 64 bit. A couple of days ago, the motherboard on the Windows client was rep; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2013-05/msg00191.html (12,442 bytes)
3. Re: [ADSM-L] Boot Path Not Found (score: 1): Author: Andrew Raibeck <storman AT US.IBM DOT COM>; Date: Fri, 31 May 2013 13:56:37 -0400; Kevin, TSM tries to identify the boot drive, and if it can't, it writes that message about "Boot path was not found". However it should continue, and it will assume C: is the boot drive. Can you do m; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2013-05/msg00198.html (14,833 bytes)
4. Re: [ADSM-L] Boot Path Not Found (score: 1): Author: "Kinder, Kevin P" <Kevin.P.Kinder AT WV DOT GOV>; Date: Fri, 31 May 2013 14:15:42 -0400; Thanks for the reply Andy. I can do manual backups. When I do a manual backup, I get the boot path error, but I can still execute the backup. It's just the scheduled items that appear to fail. I am t; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2013-05/msg00199.html (16,088 bytes)
5. Re: [ADSM-L] Boot Path Not Found (score: 1): Author: Andrew Raibeck <storman AT US.IBM DOT COM>; Date: Fri, 31 May 2013 15:08:20 -0400; Hi Kevin, For the scheduler issue: Check the schedule on the TSM server using QUERY SCHEDULE with the F=D parameter. Make sure it has not expired and that the node still has an association for it. Us; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2013-05/msg00200.html (18,792 bytes)

Current List: 1 - 5
Page: [1]