Hmm. I'm seeing if I can get a pre-script to run before a backup job that copies information from a mapped drive on another server using robocopy.

It basically uses robocopy to copy the files from the drive letter on Q: (for instance), to a removable HDD on F:.

Drive F: and it's target folder for files is selected for backup, so the script runs and backs up the files, the a post-script removes them off of it afterward.


I check it in the morning, 0.00 Bytes written. It's about 40 GB of information (Granted it's large) but I told the software to give 300 Minutes to complete the script, or give up and run the backup so time is not a large issue.


My Main question is, will Backup Exec support such an option, or will it disallow such a use of Robocopy (Or Xcopy) in a pre-script?

Hello Skill Hunter, Welcome to PCHF!

We have a fantastic staff of techs here who I am sure will be able to help you.

I have opened your thread so someone will be with you as soon as possible!

Thank you for your patience

Smokeycheech

Hi Skillhunter,

Is there any reason why you have to copy the data from Q to F then backup?

Can't you just backup the files/folders you want directly from Q. If not a little more information on what you're trying to achieve and why you have to copy first would be great.

Are you getting any errors on the robocopy job? Or are the files copied in full but just failing to be backed up by backup exec?

The situation is that;

Symantec Backup Exec 10.5 currently backs up three servers.

a 4th (non-critical) server, requires a small amount of information to be moved over to one of the three servers before the backup commences.

I figured use either XCOPY / ROBOCOPY in a pre-script, then after the backup is complete, a post-script to remove the information.


This if course, is a workaround for a company that does not wish to actually get another license for backup.

Upon testing the script, it runs with no errors. If the script is run manually and the folder (that the data is copied to) for backup is selected, the data is backed up.


If the script is placed in the pre-script section for the job, it does not execute.

Interesting, huh?

Try the new richcopy its the new replacement for robocopy and has multiple threads and is a lot faster. Could int be the files are lock as they are in use?

Interestingly not.

The files manually copy over if the script is run, regardless of open status.

ROBOCOPY is set to mirror the files, and suceeds even if the files are open.


Must admit, I was looking for something faster than Robocopy as well : /

^..^

If you set the script to run via an AT command does it work? You may find richcopy works better as there are all sort of new option like combining files from other dir etc.
I would create a cmd file called test.cmd and just put
dir c:\ > test.txt

then put that in the prescript of backup and see if it actually runs it will just give you a file c:\test.txt if it works also note the time stampt