|
|
|
|
|
Backup Overview 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 sp_addumpdevice [@devtype =]
'device_type', [@logicalname =] 'logical_name',[@physicalname =] 'physical_name'[,
{[@cntrltype =] controller_type | [@devstatus =] 'device_status'}]
The physical name for the device can refer to a tape device. Alternatively, it can refer to a filename on the local drive or a network drive. To specify a network location, you must specify the full UNC path name. The create a disk device on the local disk: The create a network device: Now when you execute a backup and send it to fulldiskdump, a file named fulldump.bak will be created in the file location that you specified containing all of the databases that you backed up to that device. To remove a backup device, you utilize the sp_dropdevice procedure.
It should be noted that SQL Server 7.0 nows conforms to MFT, Microsoft Tape Format. This means that SQL Server 7.0 and Windows NT backups can now reside within the same backup file or on the same tape. Database Storage Recap In order to fully understand backups and restoration, you must have a solid understanding of how databases are stored and where the information that your users enter goes.
Backup Overview 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 |
All content on this site, except where noted, represents an original work of Michael R. Hotek and is protected by applicable copyright laws. The SQL Server FAQ is the sole work of Neil Pike. No page, portion of a page, or download may be used for commercial purposes in whole or in part without the express, written permission of the applicable author.