-
-
Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.
TSM and Pervasive SQL
- Thread starter sabbyg
- Start date
chad_small
ADSM.ORG Moderator
- Joined
- Dec 17, 2002
- Messages
- 2,262
- Reaction score
- 52
- Points
- 0
- Location
- Gilbert, AZ
- Website
- www.tsmadmin.com
So its not MS SQL? If not then it is not supported by TSM and you would have to do one of a couple things to get it backed up:
1. Stop the app and DB and allow TSM to back it up cold (on UNIX systems when mirroring we break the mirror and backup the mirror so the app can stay up).
2. If the app has an internal backup or export facility use it to dump the DB to a file(s) on disk and allow TSM to back the files up (or archive and delete them).
3. You could set TSM to DYNAMIC mode and backup the DB live and hope the app can do cleanup of any partial transaction caught during the backup.
If it is an SQL DB you need the SQL TDP and yes you should have a license.
1. Stop the app and DB and allow TSM to back it up cold (on UNIX systems when mirroring we break the mirror and backup the mirror so the app can stay up).
2. If the app has an internal backup or export facility use it to dump the DB to a file(s) on disk and allow TSM to back the files up (or archive and delete them).
3. You could set TSM to DYNAMIC mode and backup the DB live and hope the app can do cleanup of any partial transaction caught during the backup.
If it is an SQL DB you need the SQL TDP and yes you should have a license.
dazd
Newcomer
yes this can be done first you create a bat file that looks like the one below on the machine that will be backed up
@echo off
c:\PVSW\Bin\BUTIL.EXE -startbu @D:\rhombus\data\mkdfiles.lst
if errorlevel 0 goto end
echo files not put into continuous mode try again
:end
echo all files were put into continuous mode ok
after you have done this and changed the script to match the location of your data files create a file called mkdfiles.lst or whatever you want to call it and in that file list all the files that you want to backup for example
\\server name\sharename$\DATA\ACT.MKD
\\server name\sharename$\DATA\BOM.MKD
you need to create a second script to run after the backup as below
@echo off
c:\PVSW\Bin\BUTIL.EXE -endbu @d:\rhombus\data\mkdfiles.lst
if errorlevel 0 goto end
echo files not put into normal mode try again
:end
echo all were files were put into normal mode ok
this works by having the first script called via tsm client to put the database into a sort of offline mode each data file has a new file created for it datfilename.^^^ all changes and deletes are kept in this .^^^ file, you can now backup the normal .mkd file. Then the second script copies the changes held in the .^^^ back to the .mkd file and deletes the .^^^ file (need to put an entry in dsm.opt to stop it trying trying to backup the .^^^ file)
If you are using a version above 8 I think there is also an online backup utility which saves you writing the scripts, but it works in the same way.
@echo off
c:\PVSW\Bin\BUTIL.EXE -startbu @D:\rhombus\data\mkdfiles.lst
if errorlevel 0 goto end
echo files not put into continuous mode try again
:end
echo all files were put into continuous mode ok
after you have done this and changed the script to match the location of your data files create a file called mkdfiles.lst or whatever you want to call it and in that file list all the files that you want to backup for example
\\server name\sharename$\DATA\ACT.MKD
\\server name\sharename$\DATA\BOM.MKD
you need to create a second script to run after the backup as below
@echo off
c:\PVSW\Bin\BUTIL.EXE -endbu @d:\rhombus\data\mkdfiles.lst
if errorlevel 0 goto end
echo files not put into normal mode try again
:end
echo all were files were put into normal mode ok
this works by having the first script called via tsm client to put the database into a sort of offline mode each data file has a new file created for it datfilename.^^^ all changes and deletes are kept in this .^^^ file, you can now backup the normal .mkd file. Then the second script copies the changes held in the .^^^ back to the .mkd file and deletes the .^^^ file (need to put an entry in dsm.opt to stop it trying trying to backup the .^^^ file)
If you are using a version above 8 I think there is also an online backup utility which saves you writing the scripts, but it works in the same way.
