Backups fail when file names change

[mcrampton]

Hi everyone, glad to find this place. We are running CA Brightstor Arcserver for our backup solution, but I am having some problems. We run a 7 day incremental backup, with a full backup each Sunday. There are a number of database servers which are included in the backup job, however the file names in each backup directory change slightly each night. It seems that Arcserve looks for the previous file names and completely ignores the new files. In the job log, it says "Unable to find file (File=XXX.XXX.XXX.XXX\backups\... EC=the system cannot find the file specified" and it shows all the directories as backed up, but 0 files backed up. I have reconfigured the preferred share several times to backup the entire directory, and it seems to work for 1 night, until the file names change again. We also backup a number of web servers, and these seem to back up fine, as the files are not changing on a daily basis. Anyway, if anyone has any suggestions I would really appreciate it.

Thanks.

 

[speshalyst]

Hi,

This is normal if you have made Static selection( half shaded check box) of the source. This is more of a snap shot and does not take modifications on the fly.

Ensure that the check box against the source object is fully shaded(solid green)..

Hope this helps..



So it Shall be Written!
So it Shall be Done!!

 

[mcrampton]

I do click it to solid green, but then when I come back to look at it the next day, it is half shaded green, and all the new files are not green in the file list. The old files (which no longer exist in many cases) show up with the shaded green box. So, it tries to back up the old files and completely ignores the new ones.

 

[vschumpy]

Re-create the backup jobs with full green checkboxes. It will save you time and hassle in the long run.

 

[mcrampton]

Hi, thanks for the reply. I recreated the job today and checked the directory that I wanted to backup on each server, no specific files. We'll see how it runs over the next two days, but I am not optimistic. When I look at the job detail, it shows all the specific files under each server/share that it is going to backup. That means it will probably work tonight, then when the file names change tomorrow, those servers will fail tomorrow night, because it will still be trying to back up the old file names. I'm not sure how to get around this problem.

 

[vschumpy]

Once the job is created dynamically (full green) this forces the backup to enumerate the file and directory list each time the backup is run, unlike what you had before which is a static list. I'm sure this will work out fine, it's a very common question:

http://supportconnect.ca.com/sc/redir.jsp?reqPage=search&searchID=FAQ379747