Can anyone see anything wrong with this scenario

We perform an incremental backup against an existing filespace, that regularly
reports
thousands of file errors
This is because it is trying to backup thousands of files that no longer exist
on the client, were
in fact deleted last year.
I cannot find any trace of the suspect files via sql against the database
What I propose is

1)  RENAME FILESPACE
2) RUN INCREMENTAL BACKUP AGAINST THE CLIENT
3) EXAMINE ACTIVITY LOG TO SEE WHETHER ERRORS ARE STILL REPORTED
4) DELETE NEWLY CREATED FILESPACE
5) RENAME FILESPACE FROM STEP "1"  BACK TO ORIGINAL NAME.

This should tell me if the original problem is server or client related , but I
want to be sure that
the database will be back to the same state as if I had not done the test.

Is there any gotcha I have missed

Tia
John







**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**********************************************************************