TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace: • tmss10assigncontainer
server:reload

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
server:reload [2017/06/12 16:11] – dcummingserver:reload [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== Reloading the database ======+====== Reloading The Database ======
  
 You may wish to reload the TapeTrack Database for the following reasons: You may wish to reload the TapeTrack Database for the following reasons:
Line 6: Line 6:
   - You have deleted a lot of data and the database contains a lot of slack space.   - You have deleted a lot of data and the database contains a lot of slack space.
   - You have lost the database log files or the database has become inconsistent with the database log files.   - You have lost the database log files or the database has become inconsistent with the database log files.
 +  - You upgraded your Server to the latest version and the large gap between versions requires update of database architecture.
  
 <note tip>In heavily fragmented TapeTrack databases reloading may reduce their size by a factor of one third.</note> <note tip>In heavily fragmented TapeTrack databases reloading may reduce their size by a factor of one third.</note>
 <note warning>Large databases may take 2 to 3 hours to completely reload.</note> <note warning>Large databases may take 2 to 3 hours to completely reload.</note>
-<note warning>Although the reload procedure takes a copy of each file before reloading please ensure that you take a full backup before attempting the reload. In the event of a reload failure you should rename the ''var/db'' and ''var/dblogs'' directory and restore from a backup.</note>+<note warning>Although the reload procedure takes a copy of each file before reloading, please ensure that you take a full backup before attempting the reload. In the event of a reload failure you should rename the ''var/db'' and ''var/dblogs'' directory and restore from a backup.</note> 
 + 
 + 
 +===== Automatic Reloading Of The Database  ===== 
 + 
 +Preferred method for reloading the database as the script not only handles the reload for you, it makes the clean-up after the reload a lot easier. 
 + 
 +  - [[server:start_stop|Stop]] the Framework Server if it is running. 
 +  - Open File Explorer and navigate to ''TapeTrack\TapeTrack Framework Server\var\db'' (default location C:\Program Files\TapeTrack\TapeTrack Framework Server\var\db) 
 +  - [[server:backups|Backup the TapeTrack database files]]. 
 +  - Delete the folder ''$Save'' if it exists from a previous database reload.  
 +  - In File Explorer, navigate to ''TapeTrack\TapeTrack Framework Server\scripts'' 
 +  - Right click the file ''Reload.bat'' and select ''Run as administrator'' 
 +  - Click ''Yes'' to the popup to allow the script to run.  If the script closes immediately, check to make sure the Framework Server is not running. 
 +  - From the command window, read through the output and click ''Y'' to continue the reload procedure. 
 +  - When the script finishes the command window will close 
 +  - Navigate to TapeTrack Framework Server\var\dblogs and delete the log file/s 
 +  - [[server:start_stop|Start]] the Framework Server and login to TapeMaster to confirm the procedure completed correctly. 
 + 
 +If your login to TapeMaster was successful, open File Explorer and navigate to ''TapeTrack\TapeTrack Framework Server\var\db'' and delete the folder ''$Save''. 
 + 
 + 
 + 
 +===== Manual Reload Procedure =====
  
-===== Reload procedure ===== 
   - Notify your users that the TapeTrack System will be unavailable.   - Notify your users that the TapeTrack System will be unavailable.
   - [[server:start_stop|Stop the TapeTrack Service]].   - [[server:start_stop|Stop the TapeTrack Service]].
   - [[server:backups|Backup the TapeTrack database files]].   - [[server:backups|Backup the TapeTrack database files]].
-  - Open a command prompt as Administrator. +  - Open File Explorer and navigate to the ''TapeTrack Framework Server/var/dblogs'' directory 
-  - Change directory to the TapeTrack Database file (you can use variable [[variable:TMSS10DB|TMSS10DB]]). +  - Delete all the log files in the ''dblogs'' folder 
-  - Run the command TMSS10Server with the ''-L argument''.+  - Navigate to the ''TapeTrack Framework Server/var/db'' directory 
 +  - Delete the files ''_db.001'', ''_db.002'', ''_db.003'' and ''_db.004'' 
 +  - Open a command prompt with **Administrator privileges**. 
 +  - Change directory to the TapeTrack Database file ''TapeTrack Framework Server/var/db'' (you can use variable [[variable:TMSS10DB|TMSS10DB]]). 
 +  - Run the command TMSS10Server with the -L argument  ''TMSS10Server -L''.
   - Check the output to ensure each of the steps ended with a zero return code.   - Check the output to ensure each of the steps ended with a zero return code.
   - [[server:start_stop|Start the TapeTrack Service]].   - [[server:start_stop|Start the TapeTrack Service]].
 +
 +Login to TapeMaster to make sure the database loaded correctly.
 +
 +Open File Explorer and navigate to ''TapeTrack Framework Server/var/db'', delete all (and only) files with  a file type of ''SAVE file'' or ''DUMP file'' to clean up the backup files from the database reload.
 +
 +<note warning>If the TapeTrack Database was moved to another location after the initial install the TapeTrack database may not be in the location that is reflected in the variable [[variable:TMSS10DB|TMSS10DB]].</note>
  
 <code> <code>
Line 110: Line 143:
 </code> </code>
  
-<- server:database_location|Changing the database location ^ server:advanced|Advanced Administration ^ ->+<- server:database_copy|Copying TapeTrack Database ^ server:advanced|Advanced Administration ^ ->
server/reload.1497283911.txt.gz · Last modified: 2025/01/21 22:07 (external edit)