- #Tivoli storage manager client backup tutorial update
- #Tivoli storage manager client backup tutorial full
This is needed in case the entire database is corrupted and needs to be restored. This line will create a backup of the Tivoli Storage Manager configured devices. Upd script backup "backup devconfig filenames=F:\TSM_Backup_Files\devconfig.out" line=004 So line 3 is added to the script which creates a volume history file of all volumes in the TSM system including the ones just added by the backup. Upd script backup "backup volhistory filenames=F:\TSM_Backup_Files\volhist.out" line=003 The next line will cover this exact item. This is important as we do not want to backup the volume history until th evolues from the database backup have been created. This causes the script to wait and not process subsequent commands tillt he backup is complete. Finally not the w=y or wait=yes option on the backup commnad.
#Tivoli storage manager client backup tutorial full
Also the backup is a full backup to allow it to be used on it's own for a restore. Since the script now exists, the rest o the lines must be added with this option.
#Tivoli storage manager client backup tutorial update
Note that to add an additional line we used the update rather than the define command. Line 2 to backup the database has now been added to the script. Upd script backup "ba db dev=backups t=f w=y" line=002 Next we will add line 2 which will do tha actual database backup.
This line starts the definition of a script call backup and adds line 1 to that script.
This keeps the volhist file from becoming too cumbersome over time.ĭef script backup "del volhist todate=today-5 type=dbb" line=001 Start the script with a deletion of old database backup volumes from the volume history. For example: You do not want to take a backup of your volume history before the database backup completes or you will not have the volumes of that backup defined in it. The reson is that some of the steps need to occur inthe correct sequence and this makes sure that they do. This post is going to talk about using the Tivoli Storage Mnager admin client scripting tool to gather all the parts of the database backup into a single scheduled set of commands.įirst you may ask, why the script and why not seperate schedules. So now we have the database backup, the devcnfig backup and the volhist backup.OK, we had been talkign about database backups before I rambled off on a couple of other topics. And you can designate the same file each time this runs as both of the backup commands will overwrite existing files. The location is not just the directory, but the file in that directory. But as long as you have this file, you have the info needed to restore the database.Īnd of course, the only parameter this command really has other than the type of info to backup is the F or File location where you want the information stored. These volumes can include copy storage pool sequential disk volumes as wll as the databae backup volumes. This is a listing of all the volumes created for sequential disk volumes by the TSM server. The second line backs up the volume history. So the TSM server, when started up from the command line and told to do a restore will look for a devconfig.out file. And if the device information is in the database and you are trying to restore the database. Won't you get it back when you restore the database? Yes you will, but you need a device to tell TSM where to get the volumes for the restore. Now you ask, why do you need that? The device configuration information is in the database. The first line will backup the the device configuration file. These two commands will backup the device configuration and volume history tables in your TSM database to flat text files on the file system.
No, rather than put yourself in this position, there are two simple commands that can be scheduled to run in parallel with the backups or can be scripted to run right after the backup. Remember the system where they were not watching the size of the backup volumes in the device class as compared to the size of the database and had over 700 volumes in each backup? Try typing all those into a custom volume history file. That will slow you down and could be next to impossible. In this situation, you could, but you would have to manually create a device configuration file and specify each volume of the backup in the restore command. So you just need to take the volumes form the database backup and restore them, correct? Well, close. and your CIO is breathing down your neck to get it restored. Then, during the night the databse on your enterprise TSM systems becomes corrupted. OK, after the last post, you have a backup image of your Tivoli Storage Manager database by doing a Full backup.
0 kommentar(er)
