Dear All
I think I have resolved this issue.
My mistake was to use a different FileSet for the migration job - it MUST
match the original FileSet used to create the disc file.
The reason some jobs were getting promoted from incremental to full and
others were not was due to a FileSet mismatch -
On Tuesday 20 February 2007 04:10, Support wrote:
> Dear All
>
> I have adopted job migration and all seems to work well with clients that
> were already in the Catalog when the backup was direct to tape (after
> spooling).
>
> I have an old client that had not been backed up for 6 weeks and so had
Dear All
I have adopted job migration and all seems to work well with clients that
were already in the Catalog when the backup was direct to tape (after
spooling).
I have an old client that had not been backed up for 6 weeks and so had no
Full backup in the catalog. The incremental Job on the Cli
