title: SVN Load to older repository, but SVN Clients can't commit newer files
body: <p>So our SVN server died overnight and the most recent dump was performed and copied off the server the day before.</p>
  
  <p>Got a new SVN server up and going and loaded all the repositry backups from the last successfull dump. However there were commits made to the old server after the dump was performed. Testing the new server, I see that TortoiseSVN identifies that the local client files are being the lastest and there are no commits needed, however I know the server is outdated and those most recent commits need to be committed again. </p>
  
  <p>I want to do this as efficiently as possible. Is there a way to increase the server repository number somehow and force the client machines to perform an update? ( like run a cleanup command within Tortoise and it will then identify which files need to be re-committed ). There are a number of developers all using/accessing different repositories that we have setup for each client/project.</p>
  
  <p>Thanks for any advice/help. I am brand new to SVN administration and this is the first time I had to perform a restore.</p>
  
  <p>Derek</p>