Hi!
I have a server running the old ASE 11.0.3 on AIX 5.1.
I have used TSM/SQL BackTrack (4.0.50) to copy a large database from another server, and this worked fine - despite every version of every tool being a tad old.
Before restoring to my AIX 5.1 server I created the raw logical volumes and Sybase data and log devices exactly as on the original server, performed the CREATE DATABASE and ALTER DATABASE routines with the assistance of a dba (I'm a sysadmin)and then restored through sbacktrack/TSM.
This copied database is going to provide the template for other databases to be installed after it is "cut down" substantially.
What I would like to do is dump the template database to disk (I have plenty of space on a JFS2 file system) whijch will be well over 60GB after being trimmed, and then restore it as an differently-named database.
At this point I am getting a bit vague. I know I would again need to build uniquely-named raw logical volumes and Sybase data/log devices, and once again CREATE DATABASE and allocate resource with ALTER DATABASE.
I think a custom "dtsdump" with the -as <new database name> and other arguments will suffice to dump my template database, and "dtsrestore" to promptly restore it.
Will pursuing this top-level strategy work, or is there a better route to follow?
Many thanks
recl
I have a server running the old ASE 11.0.3 on AIX 5.1.
I have used TSM/SQL BackTrack (4.0.50) to copy a large database from another server, and this worked fine - despite every version of every tool being a tad old.
Before restoring to my AIX 5.1 server I created the raw logical volumes and Sybase data and log devices exactly as on the original server, performed the CREATE DATABASE and ALTER DATABASE routines with the assistance of a dba (I'm a sysadmin)and then restored through sbacktrack/TSM.
This copied database is going to provide the template for other databases to be installed after it is "cut down" substantially.
What I would like to do is dump the template database to disk (I have plenty of space on a JFS2 file system) whijch will be well over 60GB after being trimmed, and then restore it as an differently-named database.
At this point I am getting a bit vague. I know I would again need to build uniquely-named raw logical volumes and Sybase data/log devices, and once again CREATE DATABASE and allocate resource with ALTER DATABASE.
I think a custom "dtsdump" with the -as <new database name> and other arguments will suffice to dump my template database, and "dtsrestore" to promptly restore it.
Will pursuing this top-level strategy work, or is there a better route to follow?
Many thanks
recl