- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- DL 380 G5
ProLiant Servers (ML,DL,SL)
1753280
Members
5436
Online
108792
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2010 03:47 AM
05-02-2010 03:47 AM
DL 380 G5
hi Guys !!! i need to extend c: drive on server 2008 cz my sql log file expend fast, its reach 80 gb with in month . ple i need ur help people.
thanks
thanks
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2010 01:20 PM
05-02-2010 01:20 PM
Re: DL 380 G5
Adding more disk space is just delaying the inevitable, and makes the actual problem harder to solve (because the increasing file size will limit your options).
You should *really* figure out what the log file is and what you can do with it.
If it's an information-only log, you might want to set up a log rotation: the log should be sliced into e.g. one-week or one-day files, and the older files should be compressed, archived to tape or just deleted, depending on how necessary they are.
But if this is a log that contains all the database changes ("archive log" in Oracle terminology), then you should really check your database backup procedures.
If a database is producing an archive log, that usually means someone was going to implement an on-line database backup system. But if the log is not archived to tape automatically, the job is only half done.
If the archive log is not backed up, the database events since the last full database backup will be lost if the archive log becomes unreadable. But after a succesful full database backup, the archive logs from before the full backup may be no longer needed.
A file-level backup is not good for a database, unless the database is shutdown or somehow "frozen" while it's backed up.
If the database is running normally at backup time, the beginning of the database file backup will reflect the state of the database at time T, while the end of the backup will reflect the DB state at some time T+x. In other words, the backup will be corrupted and useless for database recovery.
*Really* talk with your DataBase Administrator about this.
MK
You should *really* figure out what the log file is and what you can do with it.
If it's an information-only log, you might want to set up a log rotation: the log should be sliced into e.g. one-week or one-day files, and the older files should be compressed, archived to tape or just deleted, depending on how necessary they are.
But if this is a log that contains all the database changes ("archive log" in Oracle terminology), then you should really check your database backup procedures.
If a database is producing an archive log, that usually means someone was going to implement an on-line database backup system. But if the log is not archived to tape automatically, the job is only half done.
If the archive log is not backed up, the database events since the last full database backup will be lost if the archive log becomes unreadable. But after a succesful full database backup, the archive logs from before the full backup may be no longer needed.
A file-level backup is not good for a database, unless the database is shutdown or somehow "frozen" while it's backed up.
If the database is running normally at backup time, the beginning of the database file backup will reflect the state of the database at time T, while the end of the backup will reflect the DB state at some time T+x. In other words, the backup will be corrupted and useless for database recovery.
*Really* talk with your DataBase Administrator about this.
MK
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP