Just after an upgrade there's some SSdb backups in $SPECROOT\SS that you can use should it all go a bit wrong and you can restore to the previous upgrade state.
They're named db_<date>,x.SSdb and db_<date>,x.after.SSdb where date is the date of the upgrade and the x is the backup iteration (for example if you're going from 9.2 to 10 on the same box on the same day ,1, will be the first upgrade to 9.3 and then the next upgrade will be ,2, and so on.) One will be larger than the other - the large one has the models in, the smaller is the "legacy" db but with a modelling catalog. To get your SSdb to the last post-upgrade state, initialize the DB in Spectrum Control Panel, then in a shell/cmd cd $SPECROOT/SS ../SS-Tools/SSdbload -m db_<date>,x.SSdb This will load the models from the last upgrade into a legacy DB. If you do the same again with the _after.SSdb and use -c, you'll get the correct modelling catalog. This was a tip given to me by CA support when I had a very very sick database a while back and I didn't have viable backup from the version I was running at the time. To fix the DB on your primary, if the secondary is OK, first, get an outage window and stop SS in SCP or with the stopSS.pl script. Next, backup the secondary DB with ssdbsave, and copy it back to the primary. Then, on the primary, reset DB to legacy, then ssdbload -ila 10 <backup.SSdb> which will load your backup back into the primary with priority 10. Your Archive manager by this time will be out of sync with the SSdb, so you can either do ddm_load -i to initialize the Archive Manager on the primary and ditch history or you can attempt to ddm_save the secondary, copy back to primary and then ddm_load. For safety's sake I just ditch the event history. Then restart SS on the SECONDARY. Once it's running, restart SS on the primary. Ensure archive manager is working too. Once all is confirmed OK, run an online backup on the primary and it should take over full time again. Hope this helps! Dave David K. Game Infrastructure Management Systems Consultant Logicalis UK Ltd 110 Buckingham Avenue, Slough, Berkshire, SL1 4PF Logicalis Optimal Network Insight How future-ready is your network? Find out more _________________________________________________________________ -----Original Message----- From: Cashell, Christopher P. [mailto:cpcash...@west.com] Sent: 29 February 2016 19:31 To: spectrum <spectrum@listserv.unc.edu> Cc: 'James Wiedel' <wie...@usc.edu> Subject: RE: :[spectrum] load db from secondary server on primary after crash. You can run a backup from an active Fault-Tolerant Secondary SpectroSERVER and load it on the primary in a case where you don't have an available or viable backup from the primary. We ran into this during a recent upgrade. One of our Primary SpectroSERVERs crashed (core dump) right after upgrading, and Spectrum refused to load the backup we ran just before the upgrade. We ended up dumping a backup from the Fault-Tolerant Secondary server, and loading that on the primary. I'm guessing support probably wouldn't be happy with this, but it seemed like a better option than downgrading (which is typically unsupported, thank you CA), importing the backup, and then upgrading again. I wouldn't recommend it except as a last resort, but It Worked For Us (tm). -- Christopher Cashell Enterprise Systems Engineer West Corporation -----Original Message----- From: James Wiedel [mailto:wie...@usc.edu] Sent: Sunday, February 28, 2016 2:33 PM To: spectrum <spectrum@listserv.unc.edu> Cc: spectrum <spectrum@listserv.unc.edu> Subject: Re: :[spectrum] load db from secondary server on primary after crash. Hi Jon, There should be a viable backup that was used to send to the secondary system from the last automated online backup unless something happened to it in the meantime. If the file is still there, reload the database from the control panel and initialize the database when that question pops up. Once it reloads the database successfully you should be able to start the Spectroserver normally. Make SURE you are talking to the primary system! If the primary's backup database is damaged or missing you can try this: (I've never tried this but it should work) On the secondary system do an online backup (via OneClick). When that is finished you can FTP the backed up database to the primary server putting it in the same directory that the normal online backups are going (default is the SS-DB-Backup directory or something close to that). Then reload the database on the primary system via the control panel. Say yes to the initialize question. Once reloaded you should be able to restart SpectroSERVER via the control panel. If for some reason you can't make the secondary do an online database save you will need to stop the secondary SpectroSERVER then manually do the backup with the command line utility SSDbsave located in the SS-Tools directory. Then FTP the resultant save to the primary and reload it there. I hope some of this helps! James Sent from my iPhone > On Feb 28, 2016, at 1:58 AM, Jon Magnus Dullerud <dulle...@gmail.com> wrote: > > Hi. > My primary ss vent down last night, so I am running an the failover. > The backup in the primary doesn't load either when I try to load it it says: > ERROR: This application has been started using a Spectrum db with was not > GRACEFULLY CLOSED. > The application > will now shut down to allow you to load a previously saved good db. > > Since the failover is running it´s not a big problem for now. We are also in > the progress of setting up a new environment so I dont want to use to much > time on this old one. > My question is: is there a way to load the db on the failover on the primary, > I will have to load it on the primary with a precedence lover than it runs on > the failover. > Is it doable? > > Best Regards > Jon magnus Dullerud > --- > To unsubscribe from spectrum, send email to lists...@unc.edu with the > body: unsubscribe spectrum wie...@usc.edu --- To unsubscribe from spectrum, send email to lists...@unc.edu with the body: unsubscribe spectrum cpcash...@west.com --- To unsubscribe from spectrum, send email to lists...@unc.edu with the body: unsubscribe spectrum david.g...@uk.logicalis.com Please be aware that Logicalis UK Ltd may monitor email traffic data and also email content for security purposes. ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ This email communication does not create or vary any contractual relationship between Logicalis and you. Internet communications are not secure and accordingly Logicalis does not accept any legal liability for the contents of this message. The contents of this email are confidential to the intended recipient at the email address to which it has been addressed. It may not be disclosed to or used by anyone other than this addressee, nor may it be copied in any way. If received in error, please contact Logicalis on the above switchboard number quoting the name of the sender and the addressee and then delete it from your system. Please note that neither Logicalis nor the sender accepts any responsibility for viruses and it is your responsibility to scan the email and attachments (if any). Please be aware that Logicalis UK Ltd may monitor email traffic data and also email content for security purposes. Logicalis UK Ltd, Registered in England and Wales No: 3732397, Registered Office: 110 Buckingham Avenue, Slough. Berkshire, SL1 4PF ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ --- To unsubscribe from spectrum, send email to lists...@unc.edu with the body: unsubscribe spectrum arch...@mail-archive.com
