May 16, 2002 at 8:52 pm
Dear Experts,
I just restored the backup for one of the databases from Tape to one another harddisk of a PC which are all connected under the single domain. ( restored to PC because of the insufficient space on the server ) And I can see the PC from the server.
When I go to the server and restoration of that database, after adding the file I couldn't able to see the backup information. When I tried in some other test server, I can able to see the backup information. ( nothing wrong with the backup ). And I specified the filename correctly. ( I know that one possible reason is incorrect filename )
Could you please help me to see what is the problem here ? Any additional config needed to be done on that server ? or any problem with the network config and traffic.
Would be really appreciated your immediate help ?
Thanks Guys
May 17, 2002 at 5:39 am
WHen you create your DB you must not only the fiole size but the device fragment allocations. Ex.
I create a 100 MB database and 25MB Transaction log.
Then as I near capacity I realize I must add more space so I add 100MB additional database and another 25MB of transaction log space. Unfortunately the size of the DB is not an issue but the tranascation log frequently is near capacity so I add yet another 25MB for the Transaction log.
This would look like this
Data 100
Log 25
Data 100
Log 25
Log 25
Total 275MB so I will need at least a 275MB file to restore except I must also account for the device fragments or the 100, 25, 100, 25, 25 each must be at least that size but must be that many for the restore to take place.
This is the major reason for failure not the filename. Sorry it has been a while since I even had to think about this and took a bit to find the information again. But you will have to know basically the history of the device fragment allocations to accomplish the restore.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
May 17, 2002 at 5:41 am
Oops just found this, should help get the info. At http://buku.ti.itb.ac.id/SQL-Server/ch15.htm#Heading11
quote:
To load or recover a database from a backup, the actual device on which the database is located is not important. However, the size and type of device fragmentation allocation is. The actual device(s) on which a database resides is important if the device fails and must be re-created.To manually determine the device allocation for a database, perform the following device fragment query in the master database. (Note that the following query is for the database test1. Substitute your database name for test1):
select segmap `fragment type', size `fragment size'
from sysusages
where dbid = (select dbid
from sysdatabases
where name = "test1")
Running the query on SQL Server displays the following output:
Fragment Type Fragment Size
3 1024
4 512
The Fragment Type column translates as follows:
3 = Data device
4 = Log device
7 = Log and data are on the same device
Any other values are user-defined segments
The fragment size is displayed in 2K blocks (512 = 1M). If you don't want to compute the size of the device segment, execute the system stored procedure sp_helpdb, which has the following syntax:
sp_helpdb [database name]
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
May 19, 2002 at 9:10 pm
Dear Friend,
Thanks for your prompt reply. I am really wondering about this.
If I want to restore the DB of 275MB ( both data and log size ), then I need to create the database of this capacity ( 275 MB ) irrespective of the sizes of the data and log of the original DB.
Suppose I have the original production DB of data 1000 MB and Log 250 MB. I have taken the backup and restoring in an another DB in the same or some other server. Then the database capacity must be at least of 1250 MB. Even It can be of 1100 MB of data size and 150 MB of Log device.
Am I wrong to say this ?
But my actual problem which I have indicated below is, I couldn't find the backup information in the restoration if the actual data base backup file is in some other location in the network ( not in the same hard disk ). But I can find the bakcup information and even I can restore the DB if I copied the that file to the hard disk of the server instead of the network.
Any reasons for this. Pls. help me to understand what went wrong here.
Thanks again for your interest to help me on this.
May 20, 2002 at 5:07 am
quote:
Suppose I have the original production DB of data 1000 MB and Log 250 MB. I have taken the backup and restoring in an another DB in the same or some other server. Then the database capacity must be at least of 1250 MB. Even It can be of 1100 MB of data size and 150 MB of Log device.
Incorrect, the 1100MB data size is fine but the log device must be at least 250MB. However if the data device was originally 500MB and then later another fragement of 500MB was added then you have to create the database that way. At least 500MB for the data device then add another fragment to the data device of at least 500MB, they both can be 600MB but they have to at least be 500MB a piece.
quote:
But my actual problem which I have indicated below is, I couldn't find the backup information in the restoration if the actual data base backup file is in some other location in the network ( not in the same hard disk ). But I can find the bakcup information and even I can restore the DB if I copied the that file to the hard disk of the server instead of the network.
Don't quite understand you here. Can you rephrase.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
May 20, 2002 at 10:00 am
Are your browsing? If the extension is not the same, it won't appear. Try copying to the root of a drive and manually typing the file name in.
Steve Jones
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply