I don't think it does. I just checked and I have log files with timestamps
going back to January 12 (the day we restored the server) and I do full DB
backups daily.
On Thu, Jan 28, 2016 at 11:14 AM, Lee, Gary <glee AT bsu DOT edu> wrote:
> Shouldn't have to delete anything. Backing up the db should do it if
> memory serves.
> Been too long since I did it, and can't find my notes.
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Zoltan Forray
> Sent: Thursday, January 28, 2016 10:52 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Upgrade server from 6.3 to 7.1
>
> So, if I read correctly, to reduce my activelogsize, I
>
> 1. Backup the DB
> 2. Stop the TSM server
> 3. DELETE everything in the activelog directory/filesystem (in my case -
> /tsmlog) i.e. rm /tsmlog/*
> 4. Change ACTIVELOGSIZE to 65536
> 5. Restart the TSM server
>
> Or is it simpler than that, i.e. just change ACTIVELOGSIZE and restart the
> server. Unless I missed it, the link/article posted by Erwann (
> http://www-01.ibm.com/support/docview.wss?uid=swg21677011) doesn't
> clarify. It just says "*Decrease the ACTIVELOGSIZE to allow the current
> filesystem to be 20% greater than the ACTIVELOGSIZE specified*" but no link
> says exactly how to do it.
>
> On Wed, Jan 27, 2016 at 2:26 PM, Nixon, Charles D. (David) <
> cdnixon AT carilionclinic DOT org> wrote:
>
> > This is what we had to do too (shrink logs to 50% before upgrade and then
> > grow after the procedure). It tried to double logs and then I believe
> that
> > it forgot about the mirrored location because we were out of space.
> >
> >
> > ---------------------------------------------------
> > David Nixon
> > System Programmer II
> > Technology Services Group
> > Carilion Clinic
> > 451 Kimball Ave.
> > Roanoke, VA 24015
> > Phone: 540-224-3903
> > cdnixon AT carilionclinic DOT org
> >
> > Our mission: Improve the health of the communities we serve.
> >
> >
> >
> > ________________________________________
> > From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] on behalf of
> > Lee,
> > Gary [glee AT BSU DOT EDU]
> > Sent: Monday, January 25, 2016 12:50 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: [ADSM-L] Upgrade server from 6.3 to 7.1
> >
> > I never saw it in the docs.
> >
> > What I had to do was disable the server, do a full backup on the db, then
> > once I had verified the logs were empty, reduced log size to less than
> half
> > file system space.
> > Then do the upgrade, and enlarge logs as necessary after upgrade is
> > verified working.
> >
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> > Behalf Of
> > Rainer Tammer
> > Sent: Monday, January 25, 2016 11:16 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: [ADSM-L] Upgrade server from 6.3 to 7.1
> >
> > Hello,
> > Is this mentioned in the docs?
> >
> > That would be a bit difficult in our setup:
> >
> > Filesystem GB blocks Free %Used Iused %Iused Mounted on
> > /dev/lvtsmactlog 130.00 1.98 99% 262 1%
> > /tsminst1/tsmactlog <- active log
> > /dev/lvtsmarchlog 197.00 193.37 2% 25 1%
> > /tsminst1/tsmarchlog <- archive log
> >
> >
> > Bye
> > Rainer
> >
> > On 25.01.2016 16:51, Lee, Gary wrote:
> > > Yes.
> > >
> > > Make sure that you have at least double the size of your active and
> > archive logs as available free space in the respective log directories.
> > > i.e. . if your active log size is 32 gB, insure that your log directory
> > has more than 64 gB free. Otherwise the database upgrade will fail on
> > install.
> > >
> > > Other than that, it went well, going from 6.3.4 to 7.1.3.
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> > > Behalf
> > Of molin gregory
> > > Sent: Monday, January 25, 2016 10:30 AM
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: [ADSM-L] Upgrade server from 6.3 to 7.1
> > >
> > > Hello everyone
> > >
> > > I plan to upgrade my server from version 6.3 to version 7.1.
> > > Have you had problems with this procedure?
> > >
> > > Thank you beforehand
> > > Grégory
> > > "ATTENTION.
> > >
> > > Ce message et les pièces jointes sont confidentiels et établis à
> > l'attention exclusive de leur destinataire (aux adresses spécifiques
> > auxquelles il a été adressé). Si vous n'êtes pas le destinataire de ce
> > message, vous devez immédiatement en avertir l'expéditeur et supprimer ce
> > message et les pièces jointes de votre système.
> > >
> > > This message and any attachments are confidential and intended to be
> > received only by the addressee. If you are not the intended recipient,
> > please notify immediately the sender by reply and delete the message and
> > any attachments from your system. "
> > >
> > >
> >
> > ________________________________
> >
> > Notice: The information and attachment(s) contained in this communication
> > are intended for the addressee only, and may be confidential and/or
> legally
> > privileged. If you have received this communication in error, please
> > contact the sender immediately, and delete this communication from any
> > computer or network system. Any interception, review, printing, copying,
> > re-transmission, dissemination, or other use of, or taking of any action
> > upon this information by persons or entities other than the intended
> > recipient is strictly prohibited by law and may subject them to criminal
> or
> > civil liability. Carilion Clinic shall not be liable for the improper
> > and/or incomplete transmission of the information contained in this
> > communication or for any delay in its receipt.
> >
>
>
>
> --
> *Zoltan Forray*
> TSM Software & Hardware Administrator
> Xymon Monitor Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> www.ucc.vcu.edu
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html
>
--
*Zoltan Forray*
TSM Software & Hardware Administrator
Xymon Monitor Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html
|
