Skip to main content

Backup-Restore on Network Shared drive

Hi friends,

This is my post on Backup-Restore on Network Shared drive. After 2 days holidays coming back on job is difficult task and today I am not well due to cold. I did some wrong with myself eaten sweets more and after that cold water. SO my throat is not working properly.

Actually Every Enterprise is facing with Crunch of resources for running application and keeping backups. Sometime we require to restore database and we have no more space on local server drive. We all facing in our life as a SQL-DBA. If you have space on Shared drive then we can use it for our backup-restore task test activity. I am sharing you how to do on Network shared drive below tasks but be sure SQL have proper access on such drive or shares :-

  1. How to do backup on Shared Location.
  2. How to Restore from Shared Location to Local System
  3. How to Restore from Shared Location to another shared location by new database.

    1.)   How to Backup Database on Network Shares?

       BACKUP DATABASE world TO  DISK = N'\\192.168.X.XX\ITDev\suman\bak\abc.bak' WITH NOFORMATNOINIT,  NAME = N'FileStreamDB-Full Database ackup', SKIP, NOREWIND, NOUNLOAD,  STATS = 10

2.)   How to Restore Database Backup from Network Shares to Local System?
RESTORE DATABASE [world] FROM  DISK = N'\\192.168.X.XX\ITDev\suman\bak\abc.bak' WITH  FILE = 1, 
MOVE N'world' TO N'C:\Program Files\Microsoft SQL Server\MSSQL11.MYSERVER\MSSQL\DATA\world1.mdf', 
MOVE N'world_log' TO N'C:\Program Files\Microsoft SQL Server\MSSQL11.MYSERVER\MSSQL\DATA\world_log2.ldf',  NOUNLOAD,  STATS  

    3.)   How to Restore Database Backup from Network Shares to Share Location?
RESTORE DATABASE [world] FROM  DISK = N'\\192.168.X.XX\ITDev\suman\bak\abc.bak' WITH  FILE = 1, 
MOVE N'world' TO \\192.168.X.XX\ITDev\suman\bak\world1.mdf', 
MOVE N'world_log' TO \\192.168.X.XX\ITDev\suman\bak\world_log2.ldf',  NOUNLOAD,  STATS = 5

6 percent processed.
11 percent processed.
15 percent processed.
22 percent processed.
26 percent processed.
30 percent processed.
35 percent processed.
41 percent processed.
46 percent processed.
50 percent processed.
55 percent processed.
61 percent processed.
66 percent processed.
70 percent processed.
75 percent processed.
81 percent processed.
86 percent processed.
90 percent processed.
97 percent processed.
100 percent processed.
Processed 360 pages for database 'world', file 'world' on file 1.
Processed 3 pages for database 'world', file 'world_log' on file 1.
RESTORE DATABASE successfully processed 363 pages in 0.342 seconds (8.280 MB/sec).

use world2
select * from City


Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription