Our asterisk server was compromised. some calls were made to Asia countries last weekend.
Thought we have improved our network configuration, we still want to determine how the intrusion was done, we think there are clues in our asterisk log files.
but we don't know what to look for, based in a default asterisk:
How would you check if your postgresql DB instance needs more RAM memory to handle their current working data?
After reading the Postgresql documentation, we found that it's recommendable to run the Vacuum tasks daily:
We recommend that active production databases be vacuumed frequently (at least nightly), in order to remove dead rows.
Nonetheless, we're considering running the Reindex tasks in a daily basis too, but we're concerned about the possible implications of doing it (maybe the database size could increase as a consequence of the daily reindex, for example)
We're moving some of our applications to a new hosting provider and we want to make it seamless for our users. Nonetheless, we have big databases and we've got to move about 48GB of data.
Our proposal -if it's possible- is taking full backups of our databases and move them to our new servers. once the backups upload is finished, we're going to take differential backups from our databases and move them to the new server to finish the data migration.
Then, is it possible to create a differential backup in a separate file from the full backup?
EDIT:
I used this procedure to do it using SSMS
In order to restore a differential backup, you will first need to restore the last full backup with NO RECOVERY option. So, in SSMS you need to select the appropriate full-backup and choose Restore With NoRecovery option from the Options page. Once restored, the database will be shown in the Object Explorer as Restoring. Notice that the database is non-available/non-functional at this time and is waiting for a differential backup to be applied. Now, restore the appropriate differential backup and choose Restore With Recovery from the Options page. That’s it. You have successfully restored a differential backup.
we got some connections timeouts running a stored procedure in a SQL Server 2008 instance. after a while, the DB started to work as usual, and there weren't any additional timeout errors.
So I'm trying to get additional info about the error.
Does SQL server 2008 have any kind of error log that I can look into?
Do exist any auditing/logging features that I can activate to trace the error (if it happens again)?
My database files look very suspicious. we are using the DB in a production stage. and I'm seeing how the LDF file grows more and more. while the MDF file seems as it is not growing at all (I don't have a file size history to demonstrate it, but I think it is not doing it!! I bet!)
So I guess what could be happening? How could I force the merge to the MDF?
What is the IIS7 default time for HTTP keepAlive?