당신은 주제를 찾고 있습니까 “dsmserv restore db – Làm chủ SQL Server – Bài 8: Hướng dẫn Restore Database. Cực dễ hiểu“? 다음 카테고리의 웹사이트 https://chewathai27.com/you 에서 귀하의 모든 질문에 답변해 드립니다: https://chewathai27.com/you/blog. 바로 아래에서 답을 찾을 수 있습니다. 작성자 Học cơ sở dữ liệu cùng Trần Quốc Huy 이(가) 작성한 기사에는 조회수 1,427회 및 좋아요 24개 개의 좋아요가 있습니다.
dsmserv restore db 주제에 대한 동영상 보기
여기에서 이 주제에 대한 비디오를 시청하십시오. 주의 깊게 살펴보고 읽고 있는 내용에 대한 피드백을 제공하세요!
d여기에서 Làm chủ SQL Server – Bài 8: Hướng dẫn Restore Database. Cực dễ hiểu – dsmserv restore db 주제에 대한 세부정보를 참조하세요
Xin chào các bạn ở bài trước mình có hướng dẫn backup database và đặt lịch cho backup database. Ở bài này mình sẽ hướng dẫn các bạn Restore Database. Theo 2 cách:
+ Restore đến một bản backup bất kì.
+ Restore đến bản backup gần nhất.
Nếu thấy hay hãy để lại 1 like và 1 lượt đăng kí kênh để mình có động lực tiếp tục ra nhiều nội dung bổ ích hơn:
+ Video Bài 7: Hướng dẫn backup và đặt lịch backup: https://www.youtube.com/watch?v=AO79NjGRH3A\u0026list=PLEzgItGwNvPvVXXewk1RS3eJSd_FvVBUN\u0026index=9
Nếu có bất kì câu hỏi nào hãy liên hệ với tôi qua
+ Fanpage: https://www.facebook.com/ora.huytran/
+ Blog : https://tranquochuy.org/
+Website: https://wecommit.com.vn/
#Tranquochuy #restoredatabase #database #wecommit #dangxuanduy
#oracle #dba #python #deeplearning #linux #sql #sqlserver #sqlserverdatabase #oracledatabase #bigdata #hadoop #oraclegoldengate #dataguard
Tôi đang làm trong các lĩnh vực liên quan tới cơ sở dữ liệu, deep learning, bigdata, trí tuệ nhân tạo AINếu muốn tìm hiểu thêm về tôi hãy xem fanpage: https://www.facebook.com/ora.huytran/ Fanpage công ty: https://www.facebook.com/hocvientalent5/
Nếu muốn tham gia group học viên của tôi thì đây là link: https://www.facebook.com/groups/3376347132378919/Nếu muốn học chuyên sâu hơn các bài giảng của tôi thì đây là link các khóa học có phí: https://talent5.com.vn/
dsmserv restore db 주제에 대한 자세한 내용은 여기를 참조하세요.
14.7.3 Restoring the TSM backup environment – Fujitsu
For details of the dsmserv restore db command, refer to “DSMSERV RESTGORE DB (Restore database)” in “IBM Tivoli Storage Manager Utility” of the “ETERNUS SF …
Source: software.fujitsu.com
Date Published: 2/14/2021
View: 4502
DSMSERV RESTORE DB (Restore the Database)
If the original database or recovery log volumes are available, you issue only the DSMSERV RESTORE DB command. However, if those volumes have been lost, you …
Source: www.cenapad.unicamp.br
Date Published: 2/21/2021
View: 9273
Dsmserv Restore DB -k? – Backup Central
I’m doing a TSM Server Database recovery on a server right now where I have multiple Server Instance. When I run dsmserv.exe restore db from the directory where …
Source: www.backupcentral.com
Date Published: 5/4/2022
View: 8224
??? Dsmserv Restore DB Password ??? | ADSM.ORG
2, and 8.1.3 levels. Please review the following material and test in a test environment (including a dsmserv restore DB) before upgrading your …
Source: adsm.org
Date Published: 2/10/2021
View: 5700
IBM Tivoli Storage Manager for AIX: Administrator’s Reference
If the original database or recovery log volumes are available, issue only the DSMSERV RESTORE DB command. If those volumes are not available, issue the …
Source: www.meduniwien.ac.at
Date Published: 9/26/2021
View: 1396
Manually backing up a server database
Back up the IBM Spectrum Protect server database regularly to protect the server. … To restore a server database, use the DSMSERV RESTORE DB utility.
Source: demo.tsm.ibmserviceengage.com:11090
Date Published: 12/24/2022
View: 2015
subject:”dsmserv restore db” – The Mail Archive
Hi Everyone, I’m doing a TSM Server Database recovery on a server right now where I have multiple Server Instance. When I run dsmserv.exe restore db from the …
Source: www.mail-archive.com
Date Published: 1/5/2022
View: 3062
TSM 6.x DB Restore – PDFSLIDE.NET
… files\tivoli\tsm\server\dsmserv” restore db source=dbsnapshot todate=today on=c:\tsm\server1\dbdir.txt if dsmicfgx was used to create tsm server …
Source: pdfslide.net
Date Published: 6/11/2022
View: 7116
주제와 관련된 이미지 dsmserv restore db
주제와 관련된 더 많은 사진을 참조하십시오 Làm chủ SQL Server – Bài 8: Hướng dẫn Restore Database. Cực dễ hiểu. 댓글에서 더 많은 관련 이미지를 보거나 필요한 경우 더 많은 관련 기사를 볼 수 있습니다.
주제에 대한 기사 평가 dsmserv restore db
- Author: Học cơ sở dữ liệu cùng Trần Quốc Huy
- Views: 조회수 1,427회
- Likes: 좋아요 24개
- Date Published: 2020. 2. 7.
- Video Url link: https://www.youtube.com/watch?v=CB6Fj-9iYFY
14.7.3 Restoring the TSM backup environment
The devconfig file restored as described in Item 1 of “14.7.2 Preparing TSM management information” will be used in the TSM database restoration process.
The contents, therefore, must be edited to match the configuration of the ETERNUS tape library used at the disaster recovery site.
Do not change areas other than shaded or boxed areas of each command.
The details of changes are as followed.
Changing the library definition Change the library type of the DEFINE LIBRARY command from SCSI to MANUAL, and delete operands that come after the LIBTYPE operand. The library name of this command may not be changed. Delete the DEFINE PATH command where DESTTYPE=LIBRARY is specified. Subsequent to the above actions, the library control function may not be used during the restoration process of the TSM database.
Changing the drive definition Change the DEFINE DRIVE and DEFINE PATH commands defined in this file to that applicable to a single drive unit. Even if the ETERNUS tape library is a model with multiple drive units, this drive unit definition must be set as a single unit. Do not change the library name and drive name. Delete the operands that come after the drive name parameters in the DEFINE DRIVE command. In the device parameter of the DEFINE PATH command, define the device file of the drive unit connected to the tape server of the disaster recovery site that was recognized as described in “14.7.3 Restoring the TSM backup environment”.
Administrator’s Reference
Administrator’s Reference
Use the DSMSERV RESTORE DB command to:
To restore an ADSM database, you can use one of the following:
Roll-forward recovery Restores the database or a single database backup volume to its most current state by loading the most recent database backup series (the last full backup and any incremental backups that apply to that full backup) and using recovery log records to apply any changes made to the database since the last backup was created Point-in-time recovery Restores the database to the point in time when a specific backup version was created
Notes:
If the original database or recovery log volumes are available, you issue only the DSMSERV RESTORE DB command. However, if those volumes have been lost, you must first issue the DSMSERV FORMAT command to initialize the database and recovery log, then issue the DSMSERV RESTORE DB command. The DSMSERV RESTORE DB command uses backup versions of the database you create using the BACKUP DB command or backup versions created automatically by ADSM based on the settings you specify with the DEFINE DBBACKUPTRIGGER command. You cannot use the DSMSERV RESTORE DB command to load an offline salvage dump created with the DSMSERV DUMP DB command. After a point-in-time recovery, issue the AUDIT VOLUME command to audit all DISK volumes and resolve any inconsistencies between database information and storage pool volumes. If you saved a copy of the volume history file before restoring the database, examine that file to find out about sequential access storage pool volumes that were deleted or reused since the point in time to which the database was restored.
Syntax for Restoring a Database to Its Most Current State
You can perform a roll-forward recovery for an entire database, using the syntax that follows, if the following are true:
The log mode was set to ROLLFORWARD continuously from the time that the last backup series was created, until the time that the database was damaged or lost.
The recovery log is available and intact.
A volume history file is available and intact.
When you enter the DSMSERV RESTORE DB command with no parameters, ADSM restores the database to its most current state as follows:
Reads the recovery log to determine which volumes contain the most recent database backup series. Requests volume mounts to load the most recent backup series (the last full backup and any incremental backups that apply to that full backup) until the entire backup series is loaded. Uses the recovery log to update the database to its most current state.
.-Preview–=–No——-. >>-DSMSERV RESTORE DB—+———————-+—————>< '-Preview--=--+-No--+--' '-Yes-' Parameters for Restoring a Database to Its Most Current State Preview= value Specifies whether you want ADSM to display a list of the volumes needed to restore the database to its most current state, without performing the restore operation. This parameter is optional. The default value is NO. Possible values are: No Specifies that you want to restore the database. Yes Specifies that you want to display the list of database backup volumes but not restore the database. Syntax for Restoring a Single Database Volume to Its Most Current State You can perform a roll-forward recovery for a single database volume, using the syntax that follows, if both of the following are true: The log mode was set to ROLLFORWARD continuously from the time that the last backup series was created, until the time that the database volume was damaged or lost. The recovery log is available and intact. When you use the DSMSERV RESTORE DB command to restore a single database volume, ADSM performs the steps described in Syntax for Restoring a Database to Its Most Current State, but only the pages for the specified database volume are restore. When ADSM restores a mirrored database volume, only one copy of the volume is restored. You must use the VARY command with the ONLINE parameter to make the mirrored volumes available again. ADSM then synchronizes the mirrored volumes with the restored volume. >>-DSMSERV RESTORE DB——————————————-> .-Preview–=–No——-. >—DBVol–=–volname–+———————-+—————->< '-Preview--=--+-No--+--' '-Yes-' Parameters for Restoring a Single Database Volume to Its Most Current State DBVol= volname Specifies the name of the database volume to restore. This parameter is required. If the database volume is mirrored, you can specify the name of any volume that contains a mirrored copy of the volume you want to restore. Use the DSMSERV DISPLAY DBVOLUMES command to find the volume names. Preview= value Specifies whether you want ADSM to display a list of the database backup volumes needed to restore the database volume you specify, without performing the restore. This parameter is optional. The default value is NO. Possible values are: No Specifies that you want to restore the database volume. Yes Specifies that you want to display the list of database backup volumes but not restore the database. Syntax for Restoring a Database to a Specific Point in Time--History File Available If a backup copy of volume history information is available, you can restore a database to a specific point in time using the syntax defined below. At least one volume history file must be defined with the VOLUMEHISTORY option in the dsmserv.opt file, and at least one device configuration file must be defined with the DEVCONFIG option in the dsmserv.opt file. The server program must be able to open and read the files successfully when running the DSMSERV RESTORE DB command. If the volume history file is not available, and you want to perform a point-in-time recovery, you can use the recovery method described in Syntax for Restoring a Database to a Specific Point in Time--History File Unavailable. If a device configuration file is not available, you can manually create one. See ADSM Administrator's Guide . ADSM restores the database as follows: Uses the volume history file to locate the database backup volumes needed Requests mounts and loads data from database backup volumes as required to restore the database volume to the specified time >>-DSMSERV RESTORE DB—TODate–=–date—+————-+——-> ‘-TOTime=time-‘ .-Preview–=–No——-. >—+———————-+———————————–>< '-Preview--=--+-No--+--' '-Yes-' Parameters for Restoring a Database to a Specific Point in Time--History File Available TODate= date Specifies the date to which to restore the database. This parameter is required. Possible values are: MM/DD/YYYY Specifies that you want to restore a database using the most recent backup series that was created prior to a specific date. TODAY Specifies that you want to restore a database using the most recent backup series that was created prior to the current date. TODAY- numdays or - numdays Specifies that you want to restore a database using the most recent backup series that was created prior to a specific number of days before the current date. For example, to restore a database using the most recent backup series that was created prior to one week ago, you can enter either of the following: dsmserv restore db todate=today-7 dsmserv restore db todate=-7 TOTime= time Specifies the time of day to which to restore the database. This parameter is optional. The default is the end of the day (23:59:59). Possible values are: HH:MM:SS Specifies that you want to restore the database using the last backup series created on or before a specific time on the specified date. NOW Specifies that you want to restore the database using a backup series created on or before the current time on the specified date. For example, if you issue the DSMSERV RESTORE DB command at 9:00 with TOTIME=NOW, ADSM restores the database using the last backup series created on or prior to 9:00 on the specified date. NOW- numhours:numminutes or - numhours:numminutes Specifies that you want to restore the database using a backup series created on or before the current time minus a specified number of hours (and optionally, minutes) on the specified date. For example, if you issue the DSMSERV RESTORE DB command at 9:00 with TOTIME=NOW-3:30 or TOTIME=-3:30, ADSM restores the database using the last backup series created on or prior to 5:30 on the specified date. The following are sample commands to perform that task: dsmserv restore db todate=today-7 totime=now-3:30 dsmserv restore db todate=-7 totime=-3:30 Preview= value Specifies whether you want ADSM to display a list of the volumes needed to restore the database to the date and time you specify, without actually performing the restore operation. This parameter is optional. The default value is NO. Possible values are: No Specifies that you want to perform the restore operation. Yes Specifies that you want to display the list of database backup volumes to the specified time but not restore the database. Syntax for Restoring a Database to a Specific Point in Time--History File Unavailable If the volume history file is unavailable, you can use one or more DSMSERV RESTORE DB commands with the syntax shown below to restore an ADSM database to a specific point in time. For example, if you need to load a full backup and one or more incremental backups, you can issue a DSMSERV RESTORE DB command to restore the full backup, then issue an additional DSMSERV RESTORE DB command for each incremental backup. When you use multiple DSMSERV RESTORE DB commands, you must specify COMMIT=NO for each command except the last one you issue. For the last DSMSERV RESTORE DB command, you must specify COMMIT=YES to place the database in a consistent and usable state. If you issue a DSMSERV RESTORE DB command with a COMMIT=NO parameter, and you decide not to load additional incremental backups, you must reissue the last DSMSERV RESTORE DB command you issued and specify COMMIT=YES. If you issue a DSMSERV RESTORE DB command with a COMMIT=YES parameter, and you decide that you need to load one or more additional incremental backups, you must reissue all of the DSMSERV RESTORE DB commands in order, starting with the restore of the full backup and specifying COMMIT=NO for each one. Then, you can enter one or more additional DSMSERV RESTORE DB commands, and specify COMMIT=YES for the last one. >>-DSMSERV RESTORE DB—DEVclass–=–devclassname—————> .-,——–. V | .-COMMIT–=–No——-. >—VOLumenames–=–+—volname—+–+–+———————+->< '-FILE:filename--' '-COMMIT--=--+-No--+--' '-Yes-' Parameters for Restoring a Database to a Specific Point in Time--History File Unavailable DEVclass= devclassname Specifies the name of the sequential access device class to use. Any device class you specify for a restore must be defined in an external device configuration file specified with the DEVCONFIG option in the dsmserv.opt file. This parameter is required. If the device configuration file does not exist or has been lost, you can manually create one. See ADSM Administrator's Guide . VOLumenames= volname Specifies the backup volumes to use to restore the database. This parameter is required. Possible values are: volname Specifies the names of one or more volumes to use to restore the database. You can specify more than one backup volume by separating each volume name with a comma, with no intervening spaces. You must list the volumes in the order in which the backup was stored. For example, if you want to use the backup volumes TAPE01, TAPE02, and TAPE03, specify the following: volumenames=tape01,tape02,tape03 FILE: filename Specifies the name of a file that contains a list of the volumes to use to restore the database. The file name can be any valid file name. In the file, each volume name must be on a separate line. You must list the volumes in the order in which the backup was stored. For example, if you want to use the backup volumes TAPE01, TAPE02, and TAPE03, create a file named VOLLIST that contains these lines: TAPE01 TAPE02 TAPE03 You can then specify the volumes for the restore command as follows: volumenames=file:vollist COMMIT= commitvalue Specifies whether this is the last restore command you intend to use to restore the database. This parameter is optional. The default value is NO. Possible values are: No Specifies that you intend to issue one or more additional DSMSERV RESTORE DB commands that list additional volumes. The database remains in an inconsistent and unusable state until you issue a DSMSERV RESTORE DB command with a COMMIT=YES parameter. Specify COMMIT=NO if you plan to load additional backup volumes that contain one or more incremental backups. Yes Specifies that this is the last restore command you intend to use to restore the database. With this command, you are specifying the last backup volumes you want to use for the restore operation. Specify COMMIT=YES only when you want to restore the database to the end of the last volume specified, and you do not plan to restore any additional backup volumes that contain incremental backups. Examples Task 1 Preview the list of volumes required to restore the database to its most current state. Command: dsmserv restore db preview=yes Task 2 Restore the database to its state on March 31, 1995 at 2 pm. The volume history file is available.
Dsmserv Restore DB -k?
Hi Bill,That what I did and some how the first line that comes up wasUsing C:Program FilesTivoliTSMServer1dsmserv.opt……Can not access D:TSMServer1DB1.dsmand so on.I solved last night by shutdown TSM Server 1 and rename the directory to Server1 to Server1_old and rename Server2 to Server1.When in to Server1 directory and ran the same command and now did it work fine and I could recovery the TSM Server.In mean wild did I rename Server1_old directory to Server2 and ran dsmserv -k server2 and the old server started fine during the recovery of the other server.When the recovery was finish I ran dsmserv .-k server1 and the server that I just recovered did start up successfully.Strange problem and I will probably continue talking to IBM Support in UK about this and not IBM India did I talk to last night European Time.Best RegardsChristian SvenssonCell: +46-70-325 1577E-mail: Christian.Svensson < at > cristie.seSkype: cristie.christian.svenssonSupported Platform for CPU2TSM:: http://www.cristie.se/cpu2tsm-supported-platforms________________________________________Från: ADSM: Dist Stor Manager [ADSM-L < at > VM.MARIST.EDU] för Bill Smoldt [smoldt < at > STORSERVER.COM]Skickat: den 15 januari 2010 00:57Till: ADSM-L < at > VM.MARIST.EDUÄmne: Re: Dsmserv Restore DB -k?Christian,I do this frequently and have no problem when I cd to the server2 directory and run the following:..serverdsmserv -k server2 restore db todate=todayDuring the restore dsmserv uses the directory you’re in to create registry entries for the paths to the instance.Bill SmoldtSTORServer, Inc.On Jan 14, 2010, at 4:48 PM, Wanda Prather wrote:[quote]I ran into that a while ago. It just plain doesn’t work like it should.Got some responses from this list, but lost my test server and never gotaround to trying it again:http://www.mail-archive.com/adsm-l < at > vm.marist.edu/msg76823.htmlOn Thu, Jan 14, 2010 at 4:24 PM, Christian Svensson cristie.se> wrote:[quote]Hi Everyone,I’m doing a TSM Server Database recovery on a server right now where I havemultiple Server Instance.When I run dsmserv.exe restore db from the directory where I have thecorrect dsmserv.opt and dsmserv.dsk, then some how does TSM try to restoremy other instance that is also instance server1 in my tsm environment.When I normally start TSM I will type dsmserv.exe -k server2 but somehowdoesn’t dsmserv restore db working with the switch -kDoes anyone have any other ideas how to restore on a dedicated serverinstance?TSM Server 5.5.2 on Windows Server 2003 x64Best RegardsChristian SvenssonCell: +46-70-325 1577E-mail: Christian.Svensson < at > cristie.seSkype: cristie.christian.svenssonSupported Platform for CPU2TSM::http://www.cristie.se/cpu2tsm-supported-platforms[/quote][/quote]
??? Dsmserv Restore DB Password ???
There are a few security enhancements that everyone needs to be aware of at V7.1.8, 8.1.2, and 8.1.3 levels.Please review the following material and test in a test environment (including a dsmserv restore DB) before upgrading your production systems to V7.1.8, 8.1.2, and 8.1.3 levels to make sure that you are ready for the SSL/TLS changes. If you have already upgraded to these levels, then please keep reading the following information.Please review the product documentation, including the following topics:Protect your storage environment with an improved security protocolOptimize security with the automatically generated master encryption keyFor the latest information about security updates, see:Per the above “master encryption key” documentation, you need to set a password to protect the master encryption key during DB backup.Following an upgrade, BACKUP DB will fail until a password has been specified on either the SET DBRECOVERY command or the BACKUP DB command itself.Do not forget the password — the master encryption key cannot be restored without it!Per the following document link, the default password is the password of the SET DBRECOVERY setting: https://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.8/srv.reference/r_cmd_db_backup.html So, if you don’t remember what you set, then do a new SET DBRECOVERY to set a new password.Keep this password in a safe location, so that you can always recover your master key.If your Q DB F=D output shows “Protect Master Encryption Key = No.”, then the master key is not being backed up by the Backup DB process. With this set to NO, the Backup DB is not protecting the Master Key in case there is a disaster and you must do a Restore DB. In this case, the DB will be restored, but without the Master Key.Please follow the above steps and keep your password in a offsite secure location that can be accessed by your team during a recovery of the database.
IBM Tivoli Storage Manager for AIX: Administrator’s Reference
Tivoli Header
IBM Tivoli Storage Manager for AIX: Administrator’s Reference
Use this command for the following tasks:
Before you perform any of these operations, you should be familiar with the procedures as they are described in the Administrator’s Guide .
|The restore operation uses database backups created with the BACKUP |DB command or created automatically based on the settings specified in the |DEFINE DBBACKUPTRIGGER command. You cannot use the DSMSERV RESTORE DB |command to load a dump created with the DSMSERV DUMPDB or DSMSERV UNLOADDB |commands.
Notes:
To restore a database or volume to its most current state, the log mode must have been set to roll-forward continuously from the time that the last backup series was created. To perform a DSMSERV RESTORE DB operation, the database backup volumes must be in a library of a library type of MANUAL or SCSI. If the original database or recovery log volumes are available, issue only the DSMSERV RESTORE DB command. If those volumes are not available, issue the DSMSERV LOADFORMAT to initialize the database and recovery log, then issue the DSMSERV RESTORE DB command. During a point-in-time restore, the recovery log is reformatted. If your recovery log is large, this may take a while. After a point-in-time restore, issue the AUDIT VOLUME command to audit all DISK volumes and resolve any inconsistencies between database information and storage pool volumes. If you saved a copy of the volume history file before restoring the database, examine that file to find out about sequential access storage pool volumes that were deleted or reused since the point in time to which the database was restored. Attention: If the log mode is set to roll-forward after a point-in-time database restoration, a database backup starts when the server is brought up for the first time. This can cause loss of data: a tape can have current data on it, but because of the point-in-time restoration, it can be marked as scratch. When the server starts for the first time, it may use this tape to write the database backup, thus destroying the original data on this tape. This situation could occur if roll-forward mode is enabled, but the administrator restored the database as if the server was operating in normal mode, not roll-forward mode. For example: the database is to be backed up at midnight everyday Monday through Friday. On Friday, the database was restored to a point in time of midnight Wednesday. Thursday’s database backup was not used; this tape exists and does contain valid data. But because the database was restored to Wednesday at midnight, the Thursday’s tape was marked as scratch. This tape was then inadvertently chosen and written with the database backup information. Therefore, the data for Thursday was lost.
You can restore a database to its most current state (roll-forward recovery) only if the following are true:
The log mode was set to roll-forward continuously from the time that the last backup series was created.
An intact recovery log is available.
An intact volume history file is available.
|
|
|
Administrator’s | Guide
Tivoli Storage Manager requests volume mounts to load the most recent backup series and then uses the recovery log to update the database to its most current state.
Snapshot database backups cannot be used to restore a database to its most current state.
Syntax
.-Preview–=–No——. >>-DSMSERV RESTORE DB–+———————+—————–>< '-Preview--=--+-No--+-' '-Yes-' Parameters Preview Specifies whether you want the server to display a list of the volumes needed to restore the database to its most current state, but not to perform the restore. This parameter is optional. The default value is NO. Possible values are: No Specifies that you want to restore the database. Yes Specifies that you only want to display the list of database backup volumes. Examples Task Preview the list of volumes required to restore the database to its most current state. Command: dsmserv restore db preview=yes You can restore a single database volume to its most current state (roll-forward recovery) only if the following are true: The log mode was set to roll-forward continuously from the time that the last backup series was created, until the database volume was damaged or lost. An intact recovery log is available. Administrator's Guide Tivoli Storage Manager requests volume mounts to load the most recent backup series and then uses the recovery log to update the volume to its most current state. When Tivoli Storage Manager restores a mirrored database volume, only one copy of the volume is restored. Use the VARY command to bring the mirrored volume online. The mirrored volume is then synchronized the with the restored volume. Snapshot database backups cannot be used to restore a database to its most current state. Syntax >>-DSMSERV RESTORE DB——————————————-> .-Preview–=–No——. >–DBVol–=–volume_name–+———————+————–>< '-Preview--=--+-No--+-' '-Yes-' Parameters DBVol (Required) Specifies the name of the database volume to restore. If the volume is mirrored, you can specify the name of any volume that contains a copy of the volume to be restored. Use the DSMSERV DISPLAY DBVOLUMES command to find the volume names. Preview Specifies whether you want the server to display a list of the database backup volumes needed to restore the database volume you specify, without performing the restore. This parameter is optional. The default value is NO. Possible values are: No Specifies that you want to restore the database volume. Yes Specifies that you only want to display the list of database backup volumes. Examples Task Restore database volume dbvol2 to its most current state. The recovery log is available and intact. Command: dsmserv restore db dbvol=dbvol2 If a volume history file is available, you can restore a database to a point in time. A device configuration file with the applicable device information (library, drive, and device class definitions) must also be available, or you must manually create one (see Administrator's Guide ). If the volume history file is not available, use the method described in Restoring a Database to a Point-in-Time -- Volume History File Unavailable. Full and incremental database backups or snapshot database backups can be used to restore a database to a point in time. Syntax >>-DSMSERV RESTORE DB–TODate–=–date————————–> .-TOTime–=–23:59:59-. .-Source–=–DBBackup——-. >–+———————+–+—————————+——-> ‘-TOTime–=–time—–‘ ‘-Source–=–+-DBBackup—+-‘ ‘-DBSnapshot-‘ .-Preview–=–No——. >–+———————+————————————->< '-Preview--=--+-No--+-' '-Yes-' Parameters TODate (Required) Specifies the date to which to restore the database. Possible values are: MM/DD/YYYY Specifies that you want to restore a database using the last backup series created before the specified date. TODAY Specifies that you want to restore a database using the most recent backup series that was created before the current date. TODAY- numdays or - numdays Specifies that you want to restore a database using the most recent backup series that was created the specified number of days before the current date. TOTime Specifies the time of day to which to restore the database. This parameter is optional. The default is the end of the day (23:59:59). Possible values are: HH:MM:SS Specifies that you want to restore the database using the last backup series created on or before the specified time on the specified date. NOW Specifies that you want to restore the database using a backup series created on or before the current time on the specified date. For example, if you issue the DSMSERV RESTORE DB command at 9:00 with TOTIME=NOW, the database is restored using the last backup series created on or prior to 9:00 on the specified date. NOW- numhours:numminutes or - numhours:numminutes Specifies that you want to restore the database using a backup series created on or before the current time minus a specified number of hours and, optionally, minutes on the specified date. For example, if you issue the DSMSERV RESTORE DB command at 9:00 with TOTIME=NOW-3:30 or TOTIME+-3:30, the database is restored using the last backup series created on or prior to 5:30 on the specified date. Source Specifies whether the database is restored using either database full and incremental backup volumes or snapshot database volumes. This parameter is optional. The default value is DBBackup. Possible values are: DBBackup Specifies that the database is restored as follows: Reads the volume history file to locate the database full and incremental backup volumes needed Requests mounts and loads data from database full and incremental backup volumes as required to restore the database volume to the specified time. DBSnapshot Specifies that the database is restored as follows: Reads the volume history file to locate the snapshot database volumes needed Requests mounts and loads data from snapshot database volumes as required to restore the volume to the specified time. Preview Specifies whether you want the server to display a list of the volumes needed to restore the database, without performing the restore. This parameter is optional. The default value is NO. Possible values are: No Specifies that you want to perform the restore operation. Yes Specifies that you only want to display the list of database backup volumes. Examples Task Restore the database to its state on May 12, 1999 at 2:25 pm. The volume history file is available. Command: dsmserv restore db todate=05/12/1999 totime=14:45 preview=no If the volume history file is unavailable, you can use one or more DSMSERV RESTORE DB commands to restore the database to a specific point in time. For example, to load a full backup and one or more incremental backups, issue a DSMSERV RESTORE DB command for the full backup and an additional DSMSERV RESTORE DB command for each incremental backup. When you use multiple DSMSERV RESTORE DB commands, specify COMMIT=NO for each command except the last one. For the last command, specify COMMIT=YES. The database remains in an inconsistent and unusable state until you issue a DSMSERV RESTORE DB command with a COMMIT=YES. A device configuration file with the applicable device information (library, drive, and device class definitions) must also be available, or you must manually create one (see Administrator's Guide ). Full and incremental database backups or snapshot database backups can be used to restore a database to a point in time. To restore the database using snapshot backup volumes, you must: Specify all the volume names for the same snapshot backup series List the volumes in the sequence in which the backup was written Specify COMMIT=YES Notes: If you issue a DSMSERV RESTORE DB command with COMMIT=NO, and you decide not to load another incremental backup, reissue the last DSMSERV RESTORE DB command with COMMIT=YES. If you issue a DSMSERV RESTORE DB command with COMMIT=YES, and you decide to load an additional incremental backup, reissue all the DSMSERV RESTORE DB commands in order with COMMIT=NO on each. Then, enter any additional DSMSERV RESTORE DB commands, with COMMIT=YES on the last one. Syntax >>-DSMSERV RESTORE DB–DEVclass–=–device_class_name———–> .-,———–. V | >–VOLumenames–=–+—volume_name-+-+————————–> ‘-FILE:file_name–‘ .-COMMIT–=–No——. >–+——————–+————————————–>< '-COMMIT--=--+-No--+-' '-Yes-' Parameters DEVclass (Required) Specifies the name of the sequential access device class to use. The device class must be defined in a device configuration file. If a device configuration file is not available, you can manually create one (see Administrator's Guide ). VOLumenames (Required) Specifies the backup volumes to use to restore the database. Possible values are: volume_name Specifies the names of the volumes. To specify multiple volumes, separate the names with commas and without intervening spaces. List the volumes in the order in which they were written. FILE: file_name Specifies the name of a file that contains a list of the volumes. Enter the volumes in the order in which they were written with each name on a separate line. COMMIT Specifies whether this is the last restore command needed to restore the database. This parameter is optional. The default value is NO. Possible values are: No Specifies that you will issue one or more additional DSMSERV RESTORE DB commands. Yes Specifies that this is the last restore command to restore the database. Examples Task 1 Restore the database to the time of its most recent incremental backup. The volume history file is not available. Tape volumes FULL1, FULL2, INCR1, and INCR2 contain the database backup series. Commands dsmserv restore db devclass=tape volumenames=full1,full2 commit=no dsmserv restore db devclass=tape volumenames=incr1 commit=no dsmserv restore db devclass=tape volumenames=incr2 commit=yes Task 2 Restore a database to the time of its most recent snapshot backup. The volume history file is not available. Tape volumes TAPE01 and TAPE02 are snapshot volume names in a volume sequence that spans two tapes. Command dsmserv restore db devclass=8MM volumenames=tape01,tape01 commit=yes
subject:”dsmserv restore db”
Thanks to all the responded to this. I am right now running a dry run of the dsmserver restore db, to migrate my TSM db from a 7025-F50 to a 7026-6H1. Once atldd/Atape are installed, and the Library Manager Control Point is configured, dsmserv can talk to the 3494, and mount my db tape. I did have to remove some stuff from devconfig, as I don’t think it liked the server to server stuff much, but I did not have to define the 3494 as a manual library, which would disrupt the other three systems sharing it. Thanks again. On Mon, 27 Jan 2003, Seay, Paul wrote: If you have the 3494 mtlib code installed for Windows you can issue this command and not even go to the library. The command is: mtlib -l [library] -m -x [device serial] -V [volume number] After TSM is done with the tape it will unload it but not put it away. mtlib -l [library] -d -x [device serial] I do this all the time when a tape gets left in a drive for some unknown reason. Paul D. Seay, Jr. Technical Specialist Northrop Grumman Information Technology 757-688-8180 -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 3:34 PM To: [EMAIL PROTECTED] Subject: Re: 3494 and dsmserv restore db As a matter of fact, I had to do this last Friday to restore a Windows TSM server. I did exactly as described below in the support item Lloyd posted. You edit a copy of your devconfig file as below. Then when you run dsmserv restore db, the first thing you get is a MOUNT message. Put your 3494 in PAUSE, open the door, throw the tape in the drive requested in the MOUNT message. After the restore is done, remember to take the tape OUT of the drive. Put back your original devconfig file and restart the server. It was much less painful than I expected! -Original Message- From: Lloyd Dieter [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 2:38 PM To: [EMAIL PROTECTED] Subject: Re: 3494 and dsmserv restore db Steve, Attached (at the end) is a snippet from a howto on IBM’s support site that you may want to look over… -Lloyd On Mon, 27 Jan 2003 14:04:43 -0500 Steve Roder [EMAIL PROTECTED] wrote: Hi All, According to the doc., dsmserv restore db only supports manual and scsi libraries. Has anyone on this list restored a db via a 3590 drive inside a 3494? Since the 3494 is not libtype=scsi, I am thinking that I will have to put my 3494 into pause or manual mode, and fake TSM into thinking the 3590 is standalone, and then manually insert the dbbackup volume into the correct drive. Has anyone done this? Thanks, Steve Roder, University at Buffalo HOD Service Coordinator VM Systems Programmer UNIX Systems Administrator (Solaris and AIX) TSM/ADSM Administrator ([EMAIL PROTECTED] | (716)645-3564) Problem One may need to temporarily configure your 3494 library as manual in order to perform a database restore. The following provides instruction on how to change your devconfig file to do so. Solution First, make a copy of your devconfig.out file and rename it. Do this so that after the DB restore completes you can just rename the file back to devconfig.out without having to re-write anything. Next, open the current devconfig.out file in a text editor. All but four lines will need to be moved. Below is an example of the edited devconfig file: /* Device Configuration */ DEFINE DEVCLASS 3494CLASS DEVTYPE=3590 LIBRARY=3494LIB SET SERVERNAME SERVERNAME DEFINE LIBRARY 3494LIB LIBTYPE=manual DEFINE DRIVE 3494LIB DRIVE1 DEVICE=/dev/rmt/tsm_drive1 For TSM Version 5.1 and higher, edit as follows: /* Device Configuration */ DEFINE DEVCLASS 3494CLASS DEVTYPE=3590 LIBRARY=3494LIB SET SERVERNAME SERVERNAME DEFINE LIBRARY 3494LIB LIBTYPE=manual DEFINE DRIVE 3494LIB DRIVE1 DEFINE PATH SERVERNAME DRIVE1 SRCType=server DESTType=drive LIBR=3494LIB DEVICE=/dev/rmt/tsm_drive1 ONLINE=YES Save the file and issue your restore syntax. One will then be prompted to mount the volume. After acknowledging the mount, the resore should run to completion. When the restore has completed, discard the edited devconfig file and replace it with the old one. Assuming the restore was successful, the server will start up and reference the proper devconfig file. — – Lloyd Dieter- Senior Technology Consultant Registered Linux User 285528 Synergy, Inc. http://www.synergyinc.cc [EMAIL PROTECTED] Main:585-389-1260fax:585-389-1267 – Steve Roder, University at Buffalo HOD Service Coordinator VM Systems Programmer UNIX Systems Administrator (Solaris and AIX) TSM/ADSM Administrator ([EMAIL PROTECTED] | (716)645-3564)
TSM 6.x DB Restore
Embed Size (px) 344 x 292 429 x 357 514 x 422 599 x 487
DESCRIPTION
TSM 6.x DB restore procedure
=================================================================================MAIN=================================================================================In order to backup and restore TSM 6.1.0 DB I performed the following actions:1) create schedule to perform daily db backup (server maintainence in ISC) – either full + incremental or dbsnapshot (but if using dbsnapshot PIT is available only that is why it is necessary to use tsm 6.1.2)2) copy volhist.dat and devconf.dat (dsmserv.opt is not required) to outer storage (it is possible to write them manually).on another machine where TSM server is going to be restored:1) all pools and backups available from old server must be available on a new one too 2) launch dsmicfgx to create a new tsm server instance – install it under the same location as an old server (e.g. c:\tsm\server1)3) cd to db2/bin and run: 3.1) chcp 1251 3.2) net stop “tsm server1” 3.3) net stop “DB2 – DB2TSM1 – SERVER1” (or just net stop “server1”) manual: 3.4) db2idrop server1 3.5) db2icrt -u db2user1 server1 (then enter db2user1 password) 3.6) set DB2INSTANCE=server1 3.7) db2set -i server1 DB2_VENDOR_INI=c:\tsm\server1\tsmdbmgr.env 3.8) db2stop 3.9) db2start 3.10) set DSMI_CONFIG=c:\tsm\server1\tsmdbmgr.opt 3.11) “c:\program files\tivoli\tsm\server\dsmsutil.exe” UPDATEPW /NODE:$$_TSMDBMGR_$$ /PASSWORD:TSMDBMGR /VALIDATE:NO 3.12) rd /s /q c:\SERVER1 (folder is created after creating new database – delete it) 3.13) del /s /q c:\tsm\server1\db\* (delete all files belonging to a newly created database) 3.14) keep active and archive logs in server instance directory (they are deleted during restore db 🙁 ) 3.15) create dbdir.txt file that contains path to db dir (e.g. c:\tsm\server1\db) 3.16) restore db: 3.16.1) tsm 6.1.0: “c:\program files\tivoli\tsm\server\dsmserv” restore db on=c:\tsm\server1\dbdir.txt (PIT restore along with “on” parameter causes failure – bug) 3.16.2) tsm 6.1.2: “c:\program files\tivoli\tsm\server\dsmserv” restore db source=dbsnapshot todate=today on=c:\tsm\server1\dbdir.txt if dsmicfgx was used to create tsm server instance: 3.4) dsmserv removedb tsmdb1: http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=/com.ibm.itsm.srv.ref.doc/r_cmd_dsmserv_removedb.html 3.5) dsmserv restore db: http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.ref.doc/r_cmd_dsmserv_restore_db_current.html =================================================================================TROUBLESHOOTING=================================================================================———————————————————————————Q: The server failed to format the database TSMDB1A: db2cmd.exe -i -w -c db2 drop database TSMDB1http://www.ibm.com/developerworks/wikis/pages/viewpage.action?pageId=104532493———————————————————————————Q: PIT db restore in tsm 6.1.0?A: IC61496 (http://www-01.ibm.com/support/docview.wss?rs=663&context=SSGSG7&dc=DB550&uid=swg1IC61496&loc=en_US&cs=UTF-8&lang=en&rss=ct663other)workaround:”c:\program files\tivoli\tsm\server\dsmserv” removedb tsmdb1″c:\program files\tivoli\tsm\server\dsmserv” format ACTIVELOGD=c:\tsm\server1\al MIRRORLOGD=c:\tsm\server1\alm ARCHL=c:\tsm\server1\pal ARCHF=c:\tsm\server1\sal DBD=c:\tsm\server1\db”c:\program files\tivoli\tsm\server\dsmserv” restore db todate=today source=dbsnapshotbut in my case it caused “connection with client severed” error.———————————————————————————Q: Database backup terminated. DB2 SQLCODE -2033 SQLERRMC 406A: see 3) above — all these tricks with db2 should fix it———————————————————————————Q: ANR0227S: Incorrect database opened. Server cannot start.A: tivoli management console -> tsm server1 -> wizards -> service configuration -> advanced -> redirect server output to c:\tsm\server1\console.log.wrong dsmserv.dbid in tsm server instance directory – delete it and start server manually (not as a service):server/dsmserv.exe -S (-S to skip DB ID check and create a new one)the process will run in foreground (service not started). after killing the process it is possible to start tsm server service since correct dbid file has already been created.———————————————————————————Q: can’t connect to new server in ISCA: delete current connection and create a new one———————————————————————————Q: can’t delete database because it is not foundA: server1 folders might have been deleted – it necessary to uncatalog database:db2cmd: db2 uncatalog db tsmdb1 db2 list db directory———————————————————————————=================================================================================RESOURCES=================================================================================http://www.adsm.org/forum/showthread.php?t=17712 (most useful)http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=/com.ibm.itsm.srv.ref.doc/r_cmd_dsmserv_restore_db_pit.html (dsmserv restore db command syntax)http://www.adsm.org/forum/showthread.php?t=8427 (RL copy and restore)=================================================================================CREDENTIALS=================================================================================db2user1/db2user1 – user under which instance database manager works (the 1st screen of dsmicfgx wizard) it can be any local user and it must be in group “Administrators”iscadmin/iscadmin – ISC user credentials (used by default)admin/admin1 – TSM administrator (specified when using dsmadmc, configuration wizards in Management Console, when creating connection to TSM server in ISC)=================================================================================USING DB2 STD TOOLS=================================================================================1) ????? ????? ????????? ?? ?????? ?? ?????? ????:db2cmd db2 BACKUP DATABASE TSMDB1 ONLINE TO “C:\DB2_BACKUP” INCLUDE LOGS2) ?????????? ?? ?? ????? ???? ?? ????? ?????set DB2INSTANCE=SERVER1db2cmd db2 RESTORE DATABASE TSMDB1 FROM “C:\DB2_BACKUP” TAKEN AT 20100410114109 WITHOUT PROMPTING3) ??????? ????? ????? ?? ????? ????? ? ?????? ?????: db2cmd db2 RESTORE DATABASE TSMDB1 LOGS FROM “C:\DB2_BACKUP” TAKEN AT 20100410114109 LOGTARGET “C:\DB2_LOGS”4) ?????? ????? ?? ?????? ?????? ? ????? ?? ?????? ????: db2cmd db2 ARCHIVE LOG FOR DB TSMDB15) ??????? ???? ????? ???? ? ????? C:\DB2_LOGS6) ?????? ????? ? ??????? ?????? ????????? ??? TSM:clean all directories pertaining to old database (database and logs)7) ????? ????? ?????? ?? ????????????? ????:db2cmd db2 ROLLFORWARD DATABASE TSMDB1 TO END OF LOGS AND COMPLETE OVERFLOW LOG PATH (C:\DB2_LOGS)8) ???????? ????????? ??? TSM:dsmserv=================================================================================1-? ????? ?? ??????? ??????????? ???? ??=================================================================================???????????? ???? ?????? Tivoli Storage Manager ?????????? ?????? ? ??????? ??????? dsmserv restore db. ??? ???????????? ???? ?????? Tivoli Storage Manager ???????? ????? ???? ????: ” volhist.dat – ????? ????????? ??? ? ?????????? ??????; ” devconf.dat – ?????? ? ??????? ??????.??? ????????????? ???? ?????? ??? ???????? ???? ??? TSM (??? ?? ????? – “tsm server1”) ? ???????? ??? ?????? ??? ??? (??? ?? ????? – “server1”):net stop “tsm server1″net stop “server1”????? ???????? ????? ?????????? ???? ?????? TSM ? ??????? ????? ???????:dsmserv removedb tsmdb1????? tsmdb1 – ?? ??? ???? ?????? ??? TSM ?? ?????.??? ??? ????? ??????? ? ???????????? ???? ?????? ? ??????? ????? ???????:dsmserv restore db?????? ??????? ???? ?????? ?? ??? history.dat ? ???????? ?????????? ???? ??????, ?????? ??????? ?? ??? ????? ????? (?? ???
키워드에 대한 정보 dsmserv restore db
다음은 Bing에서 dsmserv restore db 주제에 대한 검색 결과입니다. 필요한 경우 더 읽을 수 있습니다.
이 기사는 인터넷의 다양한 출처에서 편집되었습니다. 이 기사가 유용했기를 바랍니다. 이 기사가 유용하다고 생각되면 공유하십시오. 매우 감사합니다!
사람들이 주제에 대해 자주 검색하는 키워드 Làm chủ SQL Server – Bài 8: Hướng dẫn Restore Database. Cực dễ hiểu
- Trần Quốc Huy
- Wecommit
- Làm chủ SQL
- Oracle
- SQL server
- My SQL
- Database
- Restore database
- DAtabase adminstrator
- dba
- backupdatabase
- backup
- dangxuanduy
- SQL cho người mới
- hướng dẫn restoredatabase
- restoredatabase như thế nào?
- Hướng dẫn restore database cực dễ hiểu.
- OCA
- hướng dẫn restore database
- restore database như thế nào?
Làm #chủ #SQL #Server #- #Bài #8: #Hướng #dẫn #Restore #Database. #Cực #dễ #hiểu
YouTube에서 dsmserv restore db 주제의 다른 동영상 보기
주제에 대한 기사를 시청해 주셔서 감사합니다 Làm chủ SQL Server – Bài 8: Hướng dẫn Restore Database. Cực dễ hiểu | dsmserv restore db, 이 기사가 유용하다고 생각되면 공유하십시오, 매우 감사합니다.
