Moses, You need to name each file shown in the metadata in the relocate parameter only if you don't want the location listed in the metadata for that file to be used by the restore command. For example, several of the files listed a location on the E: drive (sorry, don't have the details in front of me any more), meaning they were on the source server's E: drive someplace. If you want those files to be restored to the *same* location on the *target* server, then you can omit them from the /RELOCATE and /TO clauses.
Another way of putting this is that, for each file, the metadata supplies the file location that will be used by a restore unless you override that specific file's location with the /RELOCATE and /TO clauses. Make sense? Hope so. :o) -Chris _____ From: Moses Show [mailto:[EMAIL PROTECTED] Sent: Friday, August 27, 2004 9:23 AM To: Leonard, Christopher Subject: Re: SQL database restore question Does this mean I have to include each of the files shown in meta data in the relocate parameter and then for each of these files specify a location for them individually on the to parameter. (i.e have the locations I would like the files to be restored to tbe set for each of the files which showed up under meta data listing so the relocate and to parameters should look something like this /relocate=DWH_Data,DWH_Log,DWH_1_Data,DHWPROD_Log,DWH_2_Data, DWHPROD_Log1 /to=E:MSSQL\Data\DWHPROD.mdf,E:\MSSQL\Data\DWHPROD_Log.ldf,E:\MSSQL\Data\DWH PROD1.mdf,E:\MSSQL\Data\DHWPROD_Log.ldf,E:\MSSQL\Data\DWHPROD_Log1_Log.ldf "Leonard, Christopher" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 27/08/2004 15:05 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Re: SQL database restore question Moses, Your metadata shows the following 6 files: 3 data files named DWH_Data, DWH_1_Data, and DWH_2_Data and 3 log files named DWH_Log, DWHPROD_Log, and DWHPROD_Log1. However, your TDPSQLC RESTORE command is only relocating two of them, DWH_Data and DWH_Log. Therefore, the other 4 files are trying to restore themselves to locations that are determined from the metadata stored with the backup set. In the case of DHWPROD_Log, the file was located on the F: drive on the original SQL Server, as you can see from your /FILEINFO query. Therefore, since your TDPSQLC RESTORE command does not RELOCATE the file, TDPSQLC is trying to restore it on the F: drive on the target server as well. The solution is that you need to RELOCATE _all_ the files that should have different physical names on the target server. Hope this helps, Chris _________________________________ Chris Leonard MCSE, MCDBA, OCP, CIW _________________________________ The Database Guy http://www.databaseguy.com Brainbench MVP for Oracle Admin http://www.brainbench.com _________________________________ ============================================================================ == This communication, together with any attachments hereto or links contained herein, is for the sole use of the intended recipient(s) and may contain information that is confidential or legally protected. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, dissemination, distribution or use of this communication is STRICTLY PROHIBITED. If you have received this communication in error, please notify the sender immediately by return e-mail message and delete the original and all copies of the communication, along with any attachments hereto or links herein, from your system. ============================================================================ == The St. Paul Travelers e-mail system made this annotation on 08/27/2004, 10:24:50 AM.
smime.p7s
Description: S/MIME cryptographic signature
