Guest seanmig Posted April 1, 2008 Posted April 1, 2008 We are using NTBackup (in a batch command) as a PRE command (runs the batch file first before running actual Backup Exec job) on Backup Exec 10. If you run the batch file manually by double clicking or as a scheduled task you can see "backup.log" being created in "%Userprofile%\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\" folder. However there is no log file generated whenever the batch file was invoked (as pre-command) by running a Backup Exec job. Has anyone encountered something like this? Any assistance would be greatly appreciated. Thanks and regards, Charles
Guest Pegasus \(MVP\) Posted April 1, 2008 Posted April 1, 2008 Re: NTBACKUP log missing "seanmig" <seanmig@discussions.microsoft.com> wrote in message news:2D5CEAD9-19A6-4CA6-BFA2-7625BE9B80CD@microsoft.com... > > We are using NTBackup (in a batch command) as a PRE command (runs the > batch > file first before running actual Backup Exec job) on Backup Exec 10. If > you > run the batch file manually by double clicking or as a scheduled task you > can > see "backup.log" being created in > "%Userprofile%\Local Settings\Application Data\Microsoft\Windows > NT\NTBackup\data\" folder. However there is no log file generated > whenever > the batch file was invoked (as pre-command) by running a Backup Exec job. > > Has anyone encountered something like this? Any assistance would be > greatly > appreciated. > > > Thanks and regards, > > Charles > What is a "Pre-command backup exec job"?
Guest seanmig Posted April 1, 2008 Posted April 1, 2008 Re: NTBACKUP log missing When you define a job in Backup Exec 10 there is an option to run another independent program\script before actually running the Backup Exec job itself. In our case, we want to run a script which runs NTBackup. We use NTBackup to backup database\system state to a file then we use Backup Exec job to backup these files to a tape. Thanks, Charles "Pegasus (MVP)" wrote: > > "seanmig" <seanmig@discussions.microsoft.com> wrote in message > news:2D5CEAD9-19A6-4CA6-BFA2-7625BE9B80CD@microsoft.com... > > > > We are using NTBackup (in a batch command) as a PRE command (runs the > > batch > > file first before running actual Backup Exec job) on Backup Exec 10. If > > you > > run the batch file manually by double clicking or as a scheduled task you > > can > > see "backup.log" being created in > > "%Userprofile%\Local Settings\Application Data\Microsoft\Windows > > NT\NTBackup\data\" folder. However there is no log file generated > > whenever > > the batch file was invoked (as pre-command) by running a Backup Exec job. > > > > Has anyone encountered something like this? Any assistance would be > > greatly > > appreciated. > > > > > > Thanks and regards, > > > > Charles > > > > What is a "Pre-command backup exec job"? > > >
Guest Pegasus \(MVP\) Posted April 1, 2008 Posted April 1, 2008 Re: NTBACKUP log missing "seanmig" <seanmig@discussions.microsoft.com> wrote in message news:FE70966C-7419-45F6-8D8C-95BBDEBCC82B@microsoft.com... > > When you define a job in Backup Exec 10 there is an option to run another > independent program\script before actually running the Backup Exec job > itself. In our case, we want to run a script which runs NTBackup. We > use > NTBackup to backup database\system state to a file then we use Backup Exec > job to backup these files to a tape. Although your Subject line says "ntbackup log missing", your question appears to be about Backup Exec. This is a completely different product, first released by Veritas and then purchased by Symantec. You might attract knowlegeable respondents by reposting your question under "Backup Exec log missing". My own knowledge about Backup Exec is weak.
Guest Hank Arnold (MVP) Posted April 1, 2008 Posted April 1, 2008 Re: NTBACKUP log missing seanmig wrote: > When you define a job in Backup Exec 10 there is an option to run another > independent program\script before actually running the Backup Exec job > itself. In our case, we want to run a script which runs NTBackup. We use > NTBackup to backup database\system state to a file then we use Backup Exec > job to backup these files to a tape. > > Thanks, > > Charles > > > "Pegasus (MVP)" wrote: > >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message >> news:2D5CEAD9-19A6-4CA6-BFA2-7625BE9B80CD@microsoft.com... >>> We are using NTBackup (in a batch command) as a PRE command (runs the >>> batch >>> file first before running actual Backup Exec job) on Backup Exec 10. If >>> you >>> run the batch file manually by double clicking or as a scheduled task you >>> can >>> see "backup.log" being created in >>> "%Userprofile%\Local Settings\Application Data\Microsoft\Windows >>> NT\NTBackup\data\" folder. However there is no log file generated >>> whenever >>> the batch file was invoked (as pre-command) by running a Backup Exec job. >>> >>> Has anyone encountered something like this? Any assistance would be >>> greatly >>> appreciated. >>> >>> >>> Thanks and regards, >>> >>> Charles >>> >> What is a "Pre-command backup exec job"? >> >> >> As Pegasus says, this is really a Backup Exec problem. As a work around, though, I would: 1) Run the NTBACKUP job several times to get a good feel for how long it takes. Let's say it takes 3 minutes. 2) Create a scheduled job that will run NTBACKUP 5 or 10 minutes before the Backup Exec job. That should get you going until you can get Backup Exec working. I would suggest that you first look for any updates/fixes for your version... Symantec isn't the best support org if you don't have a contract. http://www.symantec.com/business/support/index.jsp -- Regards, Hank Arnold Microsoft MVP Windows Server - Directory Services
Guest seanmig Posted April 2, 2008 Posted April 2, 2008 Re: NTBACKUP log missing dThanks for responding. I'm not sure though if it is really Backup Exec 10 issue. It is not the BACKUP EXEC log that is missing but the NTBACKUP log. If I use AT.EXE command to schedule task to run the same script it doesn't create NTBACKUP log either. I did a bit of research before and I saw that other people experience this problem as well when using AT.EXE to schedule task. They never mentioned using Backup Exec as well so I can assume that they are not using Backup Exec and Backup Exec may have nothing to do with this problem at all. We also have several other servers using Backup Exec that's not experiencing this problem and they are configured exactly the same as the one I'm having problem with. Thanks again, Charles "Hank Arnold (MVP)" wrote: > seanmig wrote: > > When you define a job in Backup Exec 10 there is an option to run another > > independent program\script before actually running the Backup Exec job > > itself. In our case, we want to run a script which runs NTBackup. We use > > NTBackup to backup database\system state to a file then we use Backup Exec > > job to backup these files to a tape. > > > > Thanks, > > > > Charles > > > > > > "Pegasus (MVP)" wrote: > > > >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message > >> news:2D5CEAD9-19A6-4CA6-BFA2-7625BE9B80CD@microsoft.com... > >>> We are using NTBackup (in a batch command) as a PRE command (runs the > >>> batch > >>> file first before running actual Backup Exec job) on Backup Exec 10. If > >>> you > >>> run the batch file manually by double clicking or as a scheduled task you > >>> can > >>> see "backup.log" being created in > >>> "%Userprofile%\Local Settings\Application Data\Microsoft\Windows > >>> NT\NTBackup\data\" folder. However there is no log file generated > >>> whenever > >>> the batch file was invoked (as pre-command) by running a Backup Exec job. > >>> > >>> Has anyone encountered something like this? Any assistance would be > >>> greatly > >>> appreciated. > >>> > >>> > >>> Thanks and regards, > >>> > >>> Charles > >>> > >> What is a "Pre-command backup exec job"? > >> > >> > >> > > As Pegasus says, this is really a Backup Exec problem. As a work around, > though, I would: > > 1) Run the NTBACKUP job several times to get a good feel for how long it > takes. Let's say it takes 3 minutes. > > 2) Create a scheduled job that will run NTBACKUP 5 or 10 minutes before > the Backup Exec job. > > That should get you going until you can get Backup Exec working. I would > suggest that you first look for any updates/fixes for your version... > Symantec isn't the best support org if you don't have a contract. > > http://www.symantec.com/business/support/index.jsp > > > > -- > > Regards, > Hank Arnold > Microsoft MVP > Windows Server - Directory Services >
Guest Pegasus \(MVP\) Posted April 2, 2008 Posted April 2, 2008 Re: NTBACKUP log missing If you're looking for the ntbackup.exe log file then it would be best to leave out the any references to Backup Exec. They only confuse the issue. ntbackup will ***always*** create a backup log. It goes under the name of backup??.log and is stored in the profile folder of the accout used to run the job. To find the log file, simply check c:\Documents and Settings recursively for files "backup??.log". If you insist on using at.exe to schedule the job then you will find this log file in the "NetworkService" profile folder. It seems the "other people" you refer to after doing your research did not look in c:\Documents and Settings for these files. I recommend you stop using at.exe and use the Task Scheduler or schtasks.exe. "seanmig" <seanmig@discussions.microsoft.com> wrote in message news:2E6400CF-FA15-46B8-B0C7-A600C42E0171@microsoft.com... > dThanks for responding. I'm not sure though if it is really Backup Exec > 10 > issue. It is not the BACKUP EXEC log that is missing but the NTBACKUP > log. > If I use AT.EXE command to schedule task to run the same script it doesn't > create NTBACKUP log either. > > I did a bit of research before and I saw that other people experience this > problem as well when using AT.EXE to schedule task. They never mentioned > using Backup Exec as well so I can assume that they are not using Backup > Exec > and Backup Exec may have nothing to do with this problem at all. We also > have several other servers using Backup Exec that's not experiencing this > problem and they are configured exactly the same as the one I'm having > problem with. > > Thanks again, > > Charles > > > "Hank Arnold (MVP)" wrote: > >> seanmig wrote: >> > When you define a job in Backup Exec 10 there is an option to run >> > another >> > independent program\script before actually running the Backup Exec job >> > itself. In our case, we want to run a script which runs NTBackup. >> > We use >> > NTBackup to backup database\system state to a file then we use Backup >> > Exec >> > job to backup these files to a tape. >> > >> > Thanks, >> > >> > Charles >> > >> > >> > "Pegasus (MVP)" wrote: >> > >> >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message >> >> news:2D5CEAD9-19A6-4CA6-BFA2-7625BE9B80CD@microsoft.com... >> >>> We are using NTBackup (in a batch command) as a PRE command (runs the >> >>> batch >> >>> file first before running actual Backup Exec job) on Backup Exec 10. >> >>> If >> >>> you >> >>> run the batch file manually by double clicking or as a scheduled task >> >>> you >> >>> can >> >>> see "backup.log" being created in >> >>> "%Userprofile%\Local Settings\Application Data\Microsoft\Windows >> >>> NT\NTBackup\data\" folder. However there is no log file generated >> >>> whenever >> >>> the batch file was invoked (as pre-command) by running a Backup Exec >> >>> job. >> >>> >> >>> Has anyone encountered something like this? Any assistance would be >> >>> greatly >> >>> appreciated. >> >>> >> >>> >> >>> Thanks and regards, >> >>> >> >>> Charles >> >>> >> >> What is a "Pre-command backup exec job"? >> >> >> >> >> >> >> >> As Pegasus says, this is really a Backup Exec problem. As a work around, >> though, I would: >> >> 1) Run the NTBACKUP job several times to get a good feel for how long it >> takes. Let's say it takes 3 minutes. >> >> 2) Create a scheduled job that will run NTBACKUP 5 or 10 minutes before >> the Backup Exec job. >> >> That should get you going until you can get Backup Exec working. I would >> suggest that you first look for any updates/fixes for your version... >> Symantec isn't the best support org if you don't have a contract. >> >> http://www.symantec.com/business/support/index.jsp >> >> >> >> -- >> >> Regards, >> Hank Arnold >> Microsoft MVP >> Windows Server - Directory Services >>
Guest seanmig Posted April 2, 2008 Posted April 2, 2008 Re: NTBACKUP log missing I know that NTBACKUP is supposed to always create a log file in "%Userprofile%\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\" as you said but in this case it didn't create any "backup??.Log" file when NTBACKUP (through script) was invoked in a Backup Exec job. I can see that "backup??.log" is being created if I just ran the script (with NTBACKUP) manually or let it run as a Scheduled task. We are not really using AT.EXE. I just mentioned it to point out that the problem may not be with BACKUP EXEC because it also doesn't create a "backup??.log" file when you schedule the script to run using AT.EXE Hope this clear up everything. Thanks again, Charles "Pegasus (MVP)" wrote: > If you're looking for the ntbackup.exe log file then it would be > best to leave out the any references to Backup Exec. They > only confuse the issue. > > ntbackup will ***always*** create a backup log. It goes > under the name of backup??.log and is stored in the profile > folder of the accout used to run the job. To find the log file, > simply check c:\Documents and Settings recursively for files > "backup??.log". If you insist on using at.exe to schedule the > job then you will find this log file in the "NetworkService" > profile folder. It seems the "other people" you refer to after > doing your research did not look in c:\Documents and Settings > for these files. > > I recommend you stop using at.exe and use the Task Scheduler > or schtasks.exe. > > > "seanmig" <seanmig@discussions.microsoft.com> wrote in message > news:2E6400CF-FA15-46B8-B0C7-A600C42E0171@microsoft.com... > > dThanks for responding. I'm not sure though if it is really Backup Exec > > 10 > > issue. It is not the BACKUP EXEC log that is missing but the NTBACKUP > > log. > > If I use AT.EXE command to schedule task to run the same script it doesn't > > create NTBACKUP log either. > > > > I did a bit of research before and I saw that other people experience this > > problem as well when using AT.EXE to schedule task. They never mentioned > > using Backup Exec as well so I can assume that they are not using Backup > > Exec > > and Backup Exec may have nothing to do with this problem at all. We also > > have several other servers using Backup Exec that's not experiencing this > > problem and they are configured exactly the same as the one I'm having > > problem with. > > > > Thanks again, > > > > Charles > > > > > > "Hank Arnold (MVP)" wrote: > > > >> seanmig wrote: > >> > When you define a job in Backup Exec 10 there is an option to run > >> > another > >> > independent program\script before actually running the Backup Exec job > >> > itself. In our case, we want to run a script which runs NTBackup. > >> > We use > >> > NTBackup to backup database\system state to a file then we use Backup > >> > Exec > >> > job to backup these files to a tape. > >> > > >> > Thanks, > >> > > >> > Charles > >> > > >> > > >> > "Pegasus (MVP)" wrote: > >> > > >> >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message > >> >> news:2D5CEAD9-19A6-4CA6-BFA2-7625BE9B80CD@microsoft.com... > >> >>> We are using NTBackup (in a batch command) as a PRE command (runs the > >> >>> batch > >> >>> file first before running actual Backup Exec job) on Backup Exec 10. > >> >>> If > >> >>> you > >> >>> run the batch file manually by double clicking or as a scheduled task > >> >>> you > >> >>> can > >> >>> see "backup.log" being created in > >> >>> "%Userprofile%\Local Settings\Application Data\Microsoft\Windows > >> >>> NT\NTBackup\data\" folder. However there is no log file generated > >> >>> whenever > >> >>> the batch file was invoked (as pre-command) by running a Backup Exec > >> >>> job. > >> >>> > >> >>> Has anyone encountered something like this? Any assistance would be > >> >>> greatly > >> >>> appreciated. > >> >>> > >> >>> > >> >>> Thanks and regards, > >> >>> > >> >>> Charles > >> >>> > >> >> What is a "Pre-command backup exec job"? > >> >> > >> >> > >> >> > >> > >> As Pegasus says, this is really a Backup Exec problem. As a work around, > >> though, I would: > >> > >> 1) Run the NTBACKUP job several times to get a good feel for how long it > >> takes. Let's say it takes 3 minutes. > >> > >> 2) Create a scheduled job that will run NTBACKUP 5 or 10 minutes before > >> the Backup Exec job. > >> > >> That should get you going until you can get Backup Exec working. I would > >> suggest that you first look for any updates/fixes for your version... > >> Symantec isn't the best support org if you don't have a contract. > >> > >> http://www.symantec.com/business/support/index.jsp > >> > >> > >> > >> -- > >> > >> Regards, > >> Hank Arnold > >> Microsoft MVP > >> Windows Server - Directory Services > >> > > >
Guest Pegasus \(MVP\) Posted April 2, 2008 Posted April 2, 2008 Re: NTBACKUP log missing Start a Command Prompt, then type this command (verbatim!): dir /s "%AllUsersProfile%\..\backup*.log" What do you see? "seanmig" <seanmig@discussions.microsoft.com> wrote in message news:5D9B4D08-CD55-4F35-8336-DF04B8DD1DC1@microsoft.com... >I know that NTBACKUP is supposed to always create a log file in > "%Userprofile%\Local Settings\Application Data\Microsoft\Windows > NT\NTBackup\data\" as you said but in this case it didn't create any > "backup??.Log" file when NTBACKUP (through script) was invoked in a > Backup > Exec job. > > I can see that "backup??.log" is being created if I just ran the script > (with NTBACKUP) manually or let it run as a Scheduled task. > > We are not really using AT.EXE. I just mentioned it to point out that the > problem may not be with BACKUP EXEC because it also doesn't create a > "backup??.log" file when you schedule the script to run using AT.EXE > > Hope this clear up everything. > > Thanks again, > > Charles > > > > "Pegasus (MVP)" wrote: > >> If you're looking for the ntbackup.exe log file then it would be >> best to leave out the any references to Backup Exec. They >> only confuse the issue. >> >> ntbackup will ***always*** create a backup log. It goes >> under the name of backup??.log and is stored in the profile >> folder of the accout used to run the job. To find the log file, >> simply check c:\Documents and Settings recursively for files >> "backup??.log". If you insist on using at.exe to schedule the >> job then you will find this log file in the "NetworkService" >> profile folder. It seems the "other people" you refer to after >> doing your research did not look in c:\Documents and Settings >> for these files. >> >> I recommend you stop using at.exe and use the Task Scheduler >> or schtasks.exe. >> >> >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message >> news:2E6400CF-FA15-46B8-B0C7-A600C42E0171@microsoft.com... >> > dThanks for responding. I'm not sure though if it is really Backup >> > Exec >> > 10 >> > issue. It is not the BACKUP EXEC log that is missing but the NTBACKUP >> > log. >> > If I use AT.EXE command to schedule task to run the same script it >> > doesn't >> > create NTBACKUP log either. >> > >> > I did a bit of research before and I saw that other people experience >> > this >> > problem as well when using AT.EXE to schedule task. They never >> > mentioned >> > using Backup Exec as well so I can assume that they are not using >> > Backup >> > Exec >> > and Backup Exec may have nothing to do with this problem at all. We >> > also >> > have several other servers using Backup Exec that's not experiencing >> > this >> > problem and they are configured exactly the same as the one I'm having >> > problem with. >> > >> > Thanks again, >> > >> > Charles >> > >> > >> > "Hank Arnold (MVP)" wrote: >> > >> >> seanmig wrote: >> >> > When you define a job in Backup Exec 10 there is an option to run >> >> > another >> >> > independent program\script before actually running the Backup Exec >> >> > job >> >> > itself. In our case, we want to run a script which runs NTBackup. >> >> > We use >> >> > NTBackup to backup database\system state to a file then we use >> >> > Backup >> >> > Exec >> >> > job to backup these files to a tape. >> >> > >> >> > Thanks, >> >> > >> >> > Charles >> >> > >> >> > >> >> > "Pegasus (MVP)" wrote: >> >> > >> >> >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message >> >> >> news:2D5CEAD9-19A6-4CA6-BFA2-7625BE9B80CD@microsoft.com... >> >> >>> We are using NTBackup (in a batch command) as a PRE command (runs >> >> >>> the >> >> >>> batch >> >> >>> file first before running actual Backup Exec job) on Backup Exec >> >> >>> 10. >> >> >>> If >> >> >>> you >> >> >>> run the batch file manually by double clicking or as a scheduled >> >> >>> task >> >> >>> you >> >> >>> can >> >> >>> see "backup.log" being created in >> >> >>> "%Userprofile%\Local Settings\Application Data\Microsoft\Windows >> >> >>> NT\NTBackup\data\" folder. However there is no log file >> >> >>> generated >> >> >>> whenever >> >> >>> the batch file was invoked (as pre-command) by running a Backup >> >> >>> Exec >> >> >>> job. >> >> >>> >> >> >>> Has anyone encountered something like this? Any assistance would >> >> >>> be >> >> >>> greatly >> >> >>> appreciated. >> >> >>> >> >> >>> >> >> >>> Thanks and regards, >> >> >>> >> >> >>> Charles >> >> >>> >> >> >> What is a "Pre-command backup exec job"? >> >> >> >> >> >> >> >> >> >> >> >> >> As Pegasus says, this is really a Backup Exec problem. As a work >> >> around, >> >> though, I would: >> >> >> >> 1) Run the NTBACKUP job several times to get a good feel for how long >> >> it >> >> takes. Let's say it takes 3 minutes. >> >> >> >> 2) Create a scheduled job that will run NTBACKUP 5 or 10 minutes >> >> before >> >> the Backup Exec job. >> >> >> >> That should get you going until you can get Backup Exec working. I >> >> would >> >> suggest that you first look for any updates/fixes for your version... >> >> Symantec isn't the best support org if you don't have a contract. >> >> >> >> http://www.symantec.com/business/support/index.jsp >> >> >> >> >> >> >> >> -- >> >> >> >> Regards, >> >> Hank Arnold >> >> Microsoft MVP >> >> Windows Server - Directory Services >> >> >> >> >>
Guest seanmig Posted April 3, 2008 Posted April 3, 2008 Re: NTBACKUP log missing I get "The system cannot find the file specified" message. Thanks, Charles "Pegasus (MVP)" wrote: > Start a Command Prompt, then type this command (verbatim!): > dir /s "%AllUsersProfile%\..\backup*.log" > > What do you see? > > > "seanmig" <seanmig@discussions.microsoft.com> wrote in message > news:5D9B4D08-CD55-4F35-8336-DF04B8DD1DC1@microsoft.com... > >I know that NTBACKUP is supposed to always create a log file in > > "%Userprofile%\Local Settings\Application Data\Microsoft\Windows > > NT\NTBackup\data\" as you said but in this case it didn't create any > > "backup??.Log" file when NTBACKUP (through script) was invoked in a > > Backup > > Exec job. > > > > I can see that "backup??.log" is being created if I just ran the script > > (with NTBACKUP) manually or let it run as a Scheduled task. > > > > We are not really using AT.EXE. I just mentioned it to point out that the > > problem may not be with BACKUP EXEC because it also doesn't create a > > "backup??.log" file when you schedule the script to run using AT.EXE > > > > Hope this clear up everything. > > > > Thanks again, > > > > Charles > > > > > > > > "Pegasus (MVP)" wrote: > > > >> If you're looking for the ntbackup.exe log file then it would be > >> best to leave out the any references to Backup Exec. They > >> only confuse the issue. > >> > >> ntbackup will ***always*** create a backup log. It goes > >> under the name of backup??.log and is stored in the profile > >> folder of the accout used to run the job. To find the log file, > >> simply check c:\Documents and Settings recursively for files > >> "backup??.log". If you insist on using at.exe to schedule the > >> job then you will find this log file in the "NetworkService" > >> profile folder. It seems the "other people" you refer to after > >> doing your research did not look in c:\Documents and Settings > >> for these files. > >> > >> I recommend you stop using at.exe and use the Task Scheduler > >> or schtasks.exe. > >> > >> > >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message > >> news:2E6400CF-FA15-46B8-B0C7-A600C42E0171@microsoft.com... > >> > dThanks for responding. I'm not sure though if it is really Backup > >> > Exec > >> > 10 > >> > issue. It is not the BACKUP EXEC log that is missing but the NTBACKUP > >> > log. > >> > If I use AT.EXE command to schedule task to run the same script it > >> > doesn't > >> > create NTBACKUP log either. > >> > > >> > I did a bit of research before and I saw that other people experience > >> > this > >> > problem as well when using AT.EXE to schedule task. They never > >> > mentioned > >> > using Backup Exec as well so I can assume that they are not using > >> > Backup > >> > Exec > >> > and Backup Exec may have nothing to do with this problem at all. We > >> > also > >> > have several other servers using Backup Exec that's not experiencing > >> > this > >> > problem and they are configured exactly the same as the one I'm having > >> > problem with. > >> > > >> > Thanks again, > >> > > >> > Charles > >> > > >> > > >> > "Hank Arnold (MVP)" wrote: > >> > > >> >> seanmig wrote: > >> >> > When you define a job in Backup Exec 10 there is an option to run > >> >> > another > >> >> > independent program\script before actually running the Backup Exec > >> >> > job > >> >> > itself. In our case, we want to run a script which runs NTBackup. > >> >> > We use > >> >> > NTBackup to backup database\system state to a file then we use > >> >> > Backup > >> >> > Exec > >> >> > job to backup these files to a tape. > >> >> > > >> >> > Thanks, > >> >> > > >> >> > Charles > >> >> > > >> >> > > >> >> > "Pegasus (MVP)" wrote: > >> >> > > >> >> >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message > >> >> >> news:2D5CEAD9-19A6-4CA6-BFA2-7625BE9B80CD@microsoft.com... > >> >> >>> We are using NTBackup (in a batch command) as a PRE command (runs > >> >> >>> the > >> >> >>> batch > >> >> >>> file first before running actual Backup Exec job) on Backup Exec > >> >> >>> 10. > >> >> >>> If > >> >> >>> you > >> >> >>> run the batch file manually by double clicking or as a scheduled > >> >> >>> task > >> >> >>> you > >> >> >>> can > >> >> >>> see "backup.log" being created in > >> >> >>> "%Userprofile%\Local Settings\Application Data\Microsoft\Windows > >> >> >>> NT\NTBackup\data\" folder. However there is no log file > >> >> >>> generated > >> >> >>> whenever > >> >> >>> the batch file was invoked (as pre-command) by running a Backup > >> >> >>> Exec > >> >> >>> job. > >> >> >>> > >> >> >>> Has anyone encountered something like this? Any assistance would > >> >> >>> be > >> >> >>> greatly > >> >> >>> appreciated. > >> >> >>> > >> >> >>> > >> >> >>> Thanks and regards, > >> >> >>> > >> >> >>> Charles > >> >> >>> > >> >> >> What is a "Pre-command backup exec job"? > >> >> >> > >> >> >> > >> >> >> > >> >> > >> >> As Pegasus says, this is really a Backup Exec problem. As a work > >> >> around, > >> >> though, I would: > >> >> > >> >> 1) Run the NTBACKUP job several times to get a good feel for how long > >> >> it > >> >> takes. Let's say it takes 3 minutes. > >> >> > >> >> 2) Create a scheduled job that will run NTBACKUP 5 or 10 minutes > >> >> before > >> >> the Backup Exec job. > >> >> > >> >> That should get you going until you can get Backup Exec working. I > >> >> would > >> >> suggest that you first look for any updates/fixes for your version... > >> >> Symantec isn't the best support org if you don't have a contract. > >> >> > >> >> http://www.symantec.com/business/support/index.jsp > >> >> > >> >> > >> >> > >> >> -- > >> >> > >> >> Regards, > >> >> Hank Arnold > >> >> Microsoft MVP > >> >> Windows Server - Directory Services > >> >> > >> > >> > >> > > >
Guest Pegasus \(MVP\) Posted April 4, 2008 Posted April 4, 2008 Re: NTBACKUP log missing You previously reported "If I use AT.EXE command to schedule task to run the same script it doesn't create NTBACKUP log either", thus implying that you DO get a log file when you run ntbackup.exe directly. Your latest report appears to contradict this statement. It might be useful to build things up in simple steps: 1. Run ntbackup.exe by itself in a foreground session. 2. Check for the existence of the log file. 3. Run ntbackup.exe as a scheduled job. 4. Check for the existence of the log file. 5. Run ntbackup.exe in a foreground session, invoked from within backup exec. 6. Check for the existence of the log file. 7. Run ntbackup.exe as a scheduled task, invoked from within backup exec. 8. Check for the existence of the log file. "seanmig" <seanmig@discussions.microsoft.com> wrote in message news:4529E091-8FF2-4870-B134-B13B70BF3361@microsoft.com... >I get "The system cannot find the file specified" message. > > Thanks, > > Charles > > "Pegasus (MVP)" wrote: > >> Start a Command Prompt, then type this command (verbatim!): >> dir /s "%AllUsersProfile%\..\backup*.log" >> >> What do you see? >> >> >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message >> news:5D9B4D08-CD55-4F35-8336-DF04B8DD1DC1@microsoft.com... >> >I know that NTBACKUP is supposed to always create a log file in >> > "%Userprofile%\Local Settings\Application Data\Microsoft\Windows >> > NT\NTBackup\data\" as you said but in this case it didn't create any >> > "backup??.Log" file when NTBACKUP (through script) was invoked in a >> > Backup >> > Exec job. >> > >> > I can see that "backup??.log" is being created if I just ran the script >> > (with NTBACKUP) manually or let it run as a Scheduled task. >> > >> > We are not really using AT.EXE. I just mentioned it to point out that >> > the >> > problem may not be with BACKUP EXEC because it also doesn't create a >> > "backup??.log" file when you schedule the script to run using AT.EXE >> > >> > Hope this clear up everything. >> > >> > Thanks again, >> > >> > Charles >> > >> > >> > >> > "Pegasus (MVP)" wrote: >> > >> >> If you're looking for the ntbackup.exe log file then it would be >> >> best to leave out the any references to Backup Exec. They >> >> only confuse the issue. >> >> >> >> ntbackup will ***always*** create a backup log. It goes >> >> under the name of backup??.log and is stored in the profile >> >> folder of the accout used to run the job. To find the log file, >> >> simply check c:\Documents and Settings recursively for files >> >> "backup??.log". If you insist on using at.exe to schedule the >> >> job then you will find this log file in the "NetworkService" >> >> profile folder. It seems the "other people" you refer to after >> >> doing your research did not look in c:\Documents and Settings >> >> for these files. >> >> >> >> I recommend you stop using at.exe and use the Task Scheduler >> >> or schtasks.exe. >> >> >> >> >> >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message >> >> news:2E6400CF-FA15-46B8-B0C7-A600C42E0171@microsoft.com... >> >> > dThanks for responding. I'm not sure though if it is really Backup >> >> > Exec >> >> > 10 >> >> > issue. It is not the BACKUP EXEC log that is missing but the >> >> > NTBACKUP >> >> > log. >> >> > If I use AT.EXE command to schedule task to run the same script it >> >> > doesn't >> >> > create NTBACKUP log either. >> >> > >> >> > I did a bit of research before and I saw that other people >> >> > experience >> >> > this >> >> > problem as well when using AT.EXE to schedule task. They never >> >> > mentioned >> >> > using Backup Exec as well so I can assume that they are not using >> >> > Backup >> >> > Exec >> >> > and Backup Exec may have nothing to do with this problem at all. >> >> > We >> >> > also >> >> > have several other servers using Backup Exec that's not experiencing >> >> > this >> >> > problem and they are configured exactly the same as the one I'm >> >> > having >> >> > problem with. >> >> > >> >> > Thanks again, >> >> > >> >> > Charles >> >> > >> >> > >> >> > "Hank Arnold (MVP)" wrote: >> >> > >> >> >> seanmig wrote: >> >> >> > When you define a job in Backup Exec 10 there is an option to run >> >> >> > another >> >> >> > independent program\script before actually running the Backup >> >> >> > Exec >> >> >> > job >> >> >> > itself. In our case, we want to run a script which runs >> >> >> > NTBackup. >> >> >> > We use >> >> >> > NTBackup to backup database\system state to a file then we use >> >> >> > Backup >> >> >> > Exec >> >> >> > job to backup these files to a tape. >> >> >> > >> >> >> > Thanks, >> >> >> > >> >> >> > Charles >> >> >> > >> >> >> > >> >> >> > "Pegasus (MVP)" wrote: >> >> >> > >> >> >> >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message >> >> >> >> news:2D5CEAD9-19A6-4CA6-BFA2-7625BE9B80CD@microsoft.com... >> >> >> >>> We are using NTBackup (in a batch command) as a PRE command >> >> >> >>> (runs >> >> >> >>> the >> >> >> >>> batch >> >> >> >>> file first before running actual Backup Exec job) on Backup >> >> >> >>> Exec >> >> >> >>> 10. >> >> >> >>> If >> >> >> >>> you >> >> >> >>> run the batch file manually by double clicking or as a >> >> >> >>> scheduled >> >> >> >>> task >> >> >> >>> you >> >> >> >>> can >> >> >> >>> see "backup.log" being created in >> >> >> >>> "%Userprofile%\Local Settings\Application >> >> >> >>> Data\Microsoft\Windows >> >> >> >>> NT\NTBackup\data\" folder. However there is no log file >> >> >> >>> generated >> >> >> >>> whenever >> >> >> >>> the batch file was invoked (as pre-command) by running a >> >> >> >>> Backup >> >> >> >>> Exec >> >> >> >>> job. >> >> >> >>> >> >> >> >>> Has anyone encountered something like this? Any assistance >> >> >> >>> would >> >> >> >>> be >> >> >> >>> greatly >> >> >> >>> appreciated. >> >> >> >>> >> >> >> >>> >> >> >> >>> Thanks and regards, >> >> >> >>> >> >> >> >>> Charles >> >> >> >>> >> >> >> >> What is a "Pre-command backup exec job"? >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> As Pegasus says, this is really a Backup Exec problem. As a work >> >> >> around, >> >> >> though, I would: >> >> >> >> >> >> 1) Run the NTBACKUP job several times to get a good feel for how >> >> >> long >> >> >> it >> >> >> takes. Let's say it takes 3 minutes. >> >> >> >> >> >> 2) Create a scheduled job that will run NTBACKUP 5 or 10 minutes >> >> >> before >> >> >> the Backup Exec job. >> >> >> >> >> >> That should get you going until you can get Backup Exec working. I >> >> >> would >> >> >> suggest that you first look for any updates/fixes for your >> >> >> version... >> >> >> Symantec isn't the best support org if you don't have a contract. >> >> >> >> >> >> http://www.symantec.com/business/support/index.jsp >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> >> Regards, >> >> >> Hank Arnold >> >> >> Microsoft MVP >> >> >> Windows Server - Directory Services >> >> >> >> >> >> >> >> >> >> >> >>
Guest seanmig Posted April 4, 2008 Posted April 4, 2008 Re: NTBACKUP log missing I never said NTBACKUP.exe does not create a log file when run directly (by double clicking the batch script "backup.cmd" containing NTBACKUP command). In fact if you read my first post I said that "If you run the batch file manually by double clicking or as a scheduled task you can see "backup.log" being created in "%Userprofile%\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\" folder. However there is no log file generated whenever the batch file was invoked (as pre-command) by running a Backup Exec job." and by Scheduled task I don't mean using AT.EXE but the other one in the Control Panel. If I follow the steps you recommend the results are 1. NTBACKUP.EXE is run manually ( as part of a script called "backup.cmd") 2. I can see backup??.log is created 3 Schedule "backup.cmd" (NTBACKUP) to run automatically 4. I can see backup??.log is created 5. Invoke "backup.cmd" to run by running a Backup Exec Job 6. This time NO backup??.log file is created 7. Not sure what you mean by this "Run ntbackup.exe as a scheduled task, invoked from within backup exec" can't do it from backup exec Thanks again, Charles "Pegasus (MVP)" wrote: > You previously reported "If I use AT.EXE command to schedule > task to run the same script it doesn't create NTBACKUP log either", > thus implying that you DO get a log file when you run ntbackup.exe > directly. > > Your latest report appears to contradict this statement. > > It might be useful to build things up in simple steps: > 1. Run ntbackup.exe by itself in a foreground session. > 2. Check for the existence of the log file. > 3. Run ntbackup.exe as a scheduled job. > 4. Check for the existence of the log file. > 5. Run ntbackup.exe in a foreground session, invoked from > within backup exec. > 6. Check for the existence of the log file. > 7. Run ntbackup.exe as a scheduled task, invoked from > within backup exec. > 8. Check for the existence of the log file. > > "seanmig" <seanmig@discussions.microsoft.com> wrote in message > news:4529E091-8FF2-4870-B134-B13B70BF3361@microsoft.com... > >I get "The system cannot find the file specified" message. > > > > Thanks, > > > > Charles > > > > "Pegasus (MVP)" wrote: > > > >> Start a Command Prompt, then type this command (verbatim!): > >> dir /s "%AllUsersProfile%\..\backup*.log" > >> > >> What do you see? > >> > >> > >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message > >> news:5D9B4D08-CD55-4F35-8336-DF04B8DD1DC1@microsoft.com... > >> >I know that NTBACKUP is supposed to always create a log file in > >> > "%Userprofile%\Local Settings\Application Data\Microsoft\Windows > >> > NT\NTBackup\data\" as you said but in this case it didn't create any > >> > "backup??.Log" file when NTBACKUP (through script) was invoked in a > >> > Backup > >> > Exec job. > >> > > >> > I can see that "backup??.log" is being created if I just ran the script > >> > (with NTBACKUP) manually or let it run as a Scheduled task. > >> > > >> > We are not really using AT.EXE. I just mentioned it to point out that > >> > the > >> > problem may not be with BACKUP EXEC because it also doesn't create a > >> > "backup??.log" file when you schedule the script to run using AT.EXE > >> > > >> > Hope this clear up everything. > >> > > >> > Thanks again, > >> > > >> > Charles > >> > > >> > > >> > > >> > "Pegasus (MVP)" wrote: > >> > > >> >> If you're looking for the ntbackup.exe log file then it would be > >> >> best to leave out the any references to Backup Exec. They > >> >> only confuse the issue. > >> >> > >> >> ntbackup will ***always*** create a backup log. It goes > >> >> under the name of backup??.log and is stored in the profile > >> >> folder of the accout used to run the job. To find the log file, > >> >> simply check c:\Documents and Settings recursively for files > >> >> "backup??.log". If you insist on using at.exe to schedule the > >> >> job then you will find this log file in the "NetworkService" > >> >> profile folder. It seems the "other people" you refer to after > >> >> doing your research did not look in c:\Documents and Settings > >> >> for these files. > >> >> > >> >> I recommend you stop using at.exe and use the Task Scheduler > >> >> or schtasks.exe. > >> >> > >> >> > >> >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message > >> >> news:2E6400CF-FA15-46B8-B0C7-A600C42E0171@microsoft.com... > >> >> > dThanks for responding. I'm not sure though if it is really Backup > >> >> > Exec > >> >> > 10 > >> >> > issue. It is not the BACKUP EXEC log that is missing but the > >> >> > NTBACKUP > >> >> > log. > >> >> > If I use AT.EXE command to schedule task to run the same script it > >> >> > doesn't > >> >> > create NTBACKUP log either. > >> >> > > >> >> > I did a bit of research before and I saw that other people > >> >> > experience > >> >> > this > >> >> > problem as well when using AT.EXE to schedule task. They never > >> >> > mentioned > >> >> > using Backup Exec as well so I can assume that they are not using > >> >> > Backup > >> >> > Exec > >> >> > and Backup Exec may have nothing to do with this problem at all. > >> >> > We > >> >> > also > >> >> > have several other servers using Backup Exec that's not experiencing > >> >> > this > >> >> > problem and they are configured exactly the same as the one I'm > >> >> > having > >> >> > problem with. > >> >> > > >> >> > Thanks again, > >> >> > > >> >> > Charles > >> >> > > >> >> > > >> >> > "Hank Arnold (MVP)" wrote: > >> >> > > >> >> >> seanmig wrote: > >> >> >> > When you define a job in Backup Exec 10 there is an option to run > >> >> >> > another > >> >> >> > independent program\script before actually running the Backup > >> >> >> > Exec > >> >> >> > job > >> >> >> > itself. In our case, we want to run a script which runs > >> >> >> > NTBackup. > >> >> >> > We use > >> >> >> > NTBackup to backup database\system state to a file then we use > >> >> >> > Backup > >> >> >> > Exec > >> >> >> > job to backup these files to a tape. > >> >> >> > > >> >> >> > Thanks, > >> >> >> > > >> >> >> > Charles > >> >> >> > > >> >> >> > > >> >> >> > "Pegasus (MVP)" wrote: > >> >> >> > > >> >> >> >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message > >> >> >> >> news:2D5CEAD9-19A6-4CA6-BFA2-7625BE9B80CD@microsoft.com... > >> >> >> >>> We are using NTBackup (in a batch command) as a PRE command > >> >> >> >>> (runs > >> >> >> >>> the > >> >> >> >>> batch > >> >> >> >>> file first before running actual Backup Exec job) on Backup > >> >> >> >>> Exec > >> >> >> >>> 10. > >> >> >> >>> If > >> >> >> >>> you > >> >> >> >>> run the batch file manually by double clicking or as a > >> >> >> >>> scheduled > >> >> >> >>> task > >> >> >> >>> you > >> >> >> >>> can > >> >> >> >>> see "backup.log" being created in > >> >> >> >>> "%Userprofile%\Local Settings\Application > >> >> >> >>> Data\Microsoft\Windows > >> >> >> >>> NT\NTBackup\data\" folder. However there is no log file > >> >> >> >>> generated > >> >> >> >>> whenever > >> >> >> >>> the batch file was invoked (as pre-command) by running a > >> >> >> >>> Backup > >> >> >> >>> Exec > >> >> >> >>> job. > >> >> >> >>> > >> >> >> >>> Has anyone encountered something like this? Any assistance > >> >> >> >>> would > >> >> >> >>> be > >> >> >> >>> greatly > >> >> >> >>> appreciated. > >> >> >> >>> > >> >> >> >>> > >> >> >> >>> Thanks and regards, > >> >> >> >>> > >> >> >> >>> Charles > >> >> >> >>> > >> >> >> >> What is a "Pre-command backup exec job"? > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> > >> >> >> As Pegasus says, this is really a Backup Exec problem. As a work > >> >> >> around, > >> >> >> though, I would: > >> >> >> > >> >> >> 1) Run the NTBACKUP job several times to get a good feel for how > >> >> >> long > >> >> >> it > >> >> >> takes. Let's say it takes 3 minutes. > >> >> >> > >> >> >> 2) Create a scheduled job that will run NTBACKUP 5 or 10 minutes > >> >> >> before > >> >> >> the Backup Exec job. > >> >> >> > >> >> >> That should get you going until you can get Backup Exec working. I > >> >> >> would > >> >> >> suggest that you first look for any updates/fixes for your > >> >> >> version... > >> >> >> Symantec isn't the best support org if you don't have a contract. > >> >> >> > >> >> >> http://www.symantec.com/business/support/index.jsp > >> >> >> > >> >> >> > >> >> >> > >> >> >> -- > >> >> >> > >> >> >> Regards, > >> >> >> Hank Arnold > >> >> >> Microsoft MVP > >> >> >> Windows Server - Directory Services > >> >> >> > >> >> > >> >> > >> >> > >> > >> > >> > > >
Guest Pegasus \(MVP\) Posted April 4, 2008 Posted April 4, 2008 Re: NTBACKUP log missing We appear to have closed the circle: Your problem is related to BackupExec, not to ntbackup.exe. Best to try a BackupExec newsgroup. "seanmig" <seanmig@discussions.microsoft.com> wrote in message news:278165B9-A393-4A31-B899-DF25F7A335FC@microsoft.com... >I never said NTBACKUP.exe does not create a log file when run directly (by > double clicking the batch script "backup.cmd" containing NTBACKUP > command). > In fact if you read my first post I said that > > "If you run the batch file manually by double clicking or as a scheduled > task you can > see "backup.log" being created in "%Userprofile%\Local > Settings\Application > Data\Microsoft\Windows NT\NTBackup\data\" folder. However there is no log > file generated whenever the batch file was invoked (as pre-command) by > running a Backup Exec job." > > and by Scheduled task I don't mean using AT.EXE but the other one in the > Control Panel. > > If I follow the steps you recommend the results are > 1. NTBACKUP.EXE is run manually ( as part of a script called > "backup.cmd") > 2. I can see backup??.log is created > 3 Schedule "backup.cmd" (NTBACKUP) to run automatically > 4. I can see backup??.log is created > 5. Invoke "backup.cmd" to run by running a Backup Exec Job > 6. This time NO backup??.log file is created > 7. Not sure what you mean by this "Run ntbackup.exe as a scheduled task, > invoked from within backup exec" can't do it from backup exec > > Thanks again, > > Charles > > "Pegasus (MVP)" wrote: > >> You previously reported "If I use AT.EXE command to schedule >> task to run the same script it doesn't create NTBACKUP log either", >> thus implying that you DO get a log file when you run ntbackup.exe >> directly. >> >> Your latest report appears to contradict this statement. >> >> It might be useful to build things up in simple steps: >> 1. Run ntbackup.exe by itself in a foreground session. >> 2. Check for the existence of the log file. >> 3. Run ntbackup.exe as a scheduled job. >> 4. Check for the existence of the log file. >> 5. Run ntbackup.exe in a foreground session, invoked from >> within backup exec. >> 6. Check for the existence of the log file. >> 7. Run ntbackup.exe as a scheduled task, invoked from >> within backup exec. >> 8. Check for the existence of the log file. >> >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message >> news:4529E091-8FF2-4870-B134-B13B70BF3361@microsoft.com... >> >I get "The system cannot find the file specified" message. >> > >> > Thanks, >> > >> > Charles >> > >> > "Pegasus (MVP)" wrote: >> > >> >> Start a Command Prompt, then type this command (verbatim!): >> >> dir /s "%AllUsersProfile%\..\backup*.log" >> >> >> >> What do you see? >> >> >> >> >> >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message >> >> news:5D9B4D08-CD55-4F35-8336-DF04B8DD1DC1@microsoft.com... >> >> >I know that NTBACKUP is supposed to always create a log file in >> >> > "%Userprofile%\Local Settings\Application Data\Microsoft\Windows >> >> > NT\NTBackup\data\" as you said but in this case it didn't create any >> >> > "backup??.Log" file when NTBACKUP (through script) was invoked in a >> >> > Backup >> >> > Exec job. >> >> > >> >> > I can see that "backup??.log" is being created if I just ran the >> >> > script >> >> > (with NTBACKUP) manually or let it run as a Scheduled task. >> >> > >> >> > We are not really using AT.EXE. I just mentioned it to point out >> >> > that >> >> > the >> >> > problem may not be with BACKUP EXEC because it also doesn't create a >> >> > "backup??.log" file when you schedule the script to run using AT.EXE >> >> > >> >> > Hope this clear up everything. >> >> > >> >> > Thanks again, >> >> > >> >> > Charles >> >> > >> >> > >> >> > >> >> > "Pegasus (MVP)" wrote: >> >> > >> >> >> If you're looking for the ntbackup.exe log file then it would be >> >> >> best to leave out the any references to Backup Exec. They >> >> >> only confuse the issue. >> >> >> >> >> >> ntbackup will ***always*** create a backup log. It goes >> >> >> under the name of backup??.log and is stored in the profile >> >> >> folder of the accout used to run the job. To find the log file, >> >> >> simply check c:\Documents and Settings recursively for files >> >> >> "backup??.log". If you insist on using at.exe to schedule the >> >> >> job then you will find this log file in the "NetworkService" >> >> >> profile folder. It seems the "other people" you refer to after >> >> >> doing your research did not look in c:\Documents and Settings >> >> >> for these files. >> >> >> >> >> >> I recommend you stop using at.exe and use the Task Scheduler >> >> >> or schtasks.exe. >> >> >> >> >> >> >> >> >> "seanmig" <seanmig@discussions.microsoft.com> wrote in message >> >> >> news:2E6400CF-FA15-46B8-B0C7-A600C42E0171@microsoft.com... >> >> >> > dThanks for responding. I'm not sure though if it is really >> >> >> > Backup >> >> >> > Exec >> >> >> > 10 >> >> >> > issue. It is not the BACKUP EXEC log that is missing but the >> >> >> > NTBACKUP >> >> >> > log. >> >> >> > If I use AT.EXE command to schedule task to run the same script >> >> >> > it >> >> >> > doesn't >> >> >> > create NTBACKUP log either. >> >> >> > >> >> >> > I did a bit of research before and I saw that other people >> >> >> > experience >> >> >> > this >> >> >> > problem as well when using AT.EXE to schedule task. They never >> >> >> > mentioned >> >> >> > using Backup Exec as well so I can assume that they are not using >> >> >> > Backup >> >> >> > Exec >> >> >> > and Backup Exec may have nothing to do with this problem at all. >> >> >> > We >> >> >> > also >> >> >> > have several other servers using Backup Exec that's not >> >> >> > experiencing >> >> >> > this >> >> >> > problem and they are configured exactly the same as the one I'm >> >> >> > having >> >> >> > problem with. >> >> >> > >> >> >> > Thanks again, >> >> >> > >> >> >> > Charles >> >> >> > >> >> >> > >> >> >> > "Hank Arnold (MVP)" wrote: >> >> >> > >> >> >> >> seanmig wrote: >> >> >> >> > When you define a job in Backup Exec 10 there is an option to >> >> >> >> > run >> >> >> >> > another >> >> >> >> > independent program\script before actually running the Backup >> >> >> >> > Exec >> >> >> >> > job >> >> >> >> > itself. In our case, we want to run a script which runs >> >> >> >> > NTBackup. >> >> >> >> > We use >> >> >> >> > NTBackup to backup database\system state to a file then we use >> >> >> >> > Backup >> >> >> >> > Exec >> >> >> >> > job to backup these files to a tape. >> >> >> >> > >> >> >> >> > Thanks, >> >> >> >> > >> >> >> >> > Charles >> >> >> >> > >> >> >> >> > >> >> >> >> > "Pegasus (MVP)" wrote: >> >> >> >> > >> >> >> >> >> "seanmig" <seanmig@discussions.microsoft.com> wrote in >> >> >> >> >> message >> >> >> >> >> news:2D5CEAD9-19A6-4CA6-BFA2-7625BE9B80CD@microsoft.com... >> >> >> >> >>> We are using NTBackup (in a batch command) as a PRE command >> >> >> >> >>> (runs >> >> >> >> >>> the >> >> >> >> >>> batch >> >> >> >> >>> file first before running actual Backup Exec job) on Backup >> >> >> >> >>> Exec >> >> >> >> >>> 10. >> >> >> >> >>> If >> >> >> >> >>> you >> >> >> >> >>> run the batch file manually by double clicking or as a >> >> >> >> >>> scheduled >> >> >> >> >>> task >> >> >> >> >>> you >> >> >> >> >>> can >> >> >> >> >>> see "backup.log" being created in >> >> >> >> >>> "%Userprofile%\Local Settings\Application >> >> >> >> >>> Data\Microsoft\Windows >> >> >> >> >>> NT\NTBackup\data\" folder. However there is no log file >> >> >> >> >>> generated >> >> >> >> >>> whenever >> >> >> >> >>> the batch file was invoked (as pre-command) by running a >> >> >> >> >>> Backup >> >> >> >> >>> Exec >> >> >> >> >>> job. >> >> >> >> >>> >> >> >> >> >>> Has anyone encountered something like this? Any assistance >> >> >> >> >>> would >> >> >> >> >>> be >> >> >> >> >>> greatly >> >> >> >> >>> appreciated. >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> >>> Thanks and regards, >> >> >> >> >>> >> >> >> >> >>> Charles >> >> >> >> >>> >> >> >> >> >> What is a "Pre-command backup exec job"? >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> As Pegasus says, this is really a Backup Exec problem. As a work >> >> >> >> around, >> >> >> >> though, I would: >> >> >> >> >> >> >> >> 1) Run the NTBACKUP job several times to get a good feel for how >> >> >> >> long >> >> >> >> it >> >> >> >> takes. Let's say it takes 3 minutes. >> >> >> >> >> >> >> >> 2) Create a scheduled job that will run NTBACKUP 5 or 10 minutes >> >> >> >> before >> >> >> >> the Backup Exec job. >> >> >> >> >> >> >> >> That should get you going until you can get Backup Exec working. >> >> >> >> I >> >> >> >> would >> >> >> >> suggest that you first look for any updates/fixes for your >> >> >> >> version... >> >> >> >> Symantec isn't the best support org if you don't have a >> >> >> >> contract. >> >> >> >> >> >> >> >> http://www.symantec.com/business/support/index.jsp >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> >> >> >> Regards, >> >> >> >> Hank Arnold >> >> >> >> Microsoft MVP >> >> >> >> Windows Server - Directory Services >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >>
Recommended Posts