Free Space On server

Hi all,
Our server is running out of space because of the log files and I have to manually shrink the log files for all the database almost everyday. We are planning to upgrade the server but also, in the meantime, I would like to know whether I can change the default path of the log files to a different drive and if yes, how to proceed?
Thanks in advance,
Joseph

Hi!
You can move your mdf and ldf files to different Location.
1. Open MS-SQL Databse
2. Enable Object Explorer
3. Right Click on your Company DB and select Detach, before doing detach please ensure that you are logged in to the databse via, SAP B1,New Query Window,Stop Mail Services,Stop Backup Services of SAP.
4. After Detaching, your DB will detached from the Databse List of MS-SQL
5. Now, go to your Installtion Path of MS-SQL Server Database.(C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data)
6. Cut the mdf and ldf file of your database.
7. Paste the same in different Location.
8. Open MS-SQL Database.
9. on Object Explorer, Right Clik on the Data Base
10. Select Attach
11. Map the mdf path of your company DB

Similar Messages

A second issue - no free space on server, possibly hacked?

On Monday morning, 4/30/2007, I came in to discover the last 80 GB left on our server was filled with 0 GB of free space. All the space had been taken up by a file/directory somewhere in one of the root folders (/etc, /var, etc). I never found out what took up all the space. Looking at our firewall, there had been a very large number of spoofed IP attempts to the server on ports 22 (SSH) and 135 and 139 (part of Samba) from a variety of IP addresses. Looking at the console log, the only thing I could find was the following error message just about every three minutes for hours and hours:
DirectoryService[55]: Failed Authentication return is being delayed due to over five recent auth failures for username: root.
So, I ended up rebooting the server after I came in, and shortly thereafter, the free space eventually returned. Was this a DoS attack or were we hacked?
I could not find any other evidence in our logs that anyone made it in, but I could be wrong.
Just as a note, I am dealing with a couple of other server issues:
1) "Could not chdir to home directory /Network/Servers/..."
http://discussions.apple.com/thread.jspa?threadID=948408&tstart=0
2) server spontaneously returns to the login screen:
http://discussions.apple.com/thread.jspa?threadID=948445
Thanks,
Tyler

Why is an unsecured ssh publicly available ?
Mac OS X or any other flavor of *nix, you must secure ssh.
Don't make it publicly available (why are you forwarding traffic for port 22 ?), use ssh keys if ssh access is truly needed, and use something other than the default port (most easily done by forwarding it from a different port externally to port 22 internally at your router/firewall)
Disallow root ssh access.
http://www.google.com/search?q=securing+ssh
http://images.apple.com/server/pdfs/TigerServer_Security_Config021507.pdf
p. 191+

Time machine on server doesn't show correct amount of free space

Hi
I have a mac mini server running 10.9.3, with a drobo raid connected via usb (I wouldn't have chosen the drobo, but not my decision..). The server has Time Machine service enabled, pointing to a folder on the drobo.
When users connect to it (various mavericks clients) they can choose to use it for Time Machine, but when the clients starts to back up, they all quits quite fast, because it states that there is only from around 3-400 MB to around 80-90 GB free space.
There is, however, around 1.5 TB free space on the disk, and this registers also fine in the server app on the server.
I have tried to use another drive as the backup target, which leads to the same issue.
I have also tried to remove the backup and initiate a new on the client, but still the same. It is not consistent how far the client backup gets - the one that have gone furthest is around 45 GB.
Any idea on what it might be?
A few more details:
- the drobo is hfs+ journaled
- I have checked the size restriction in the time machine settings on the server and have tried with both a 500 GB restriction and no restriction
- the clients are all set up to do unencrypted backup
- the clients have both been cabled connections and wifi connections
- the clients have no problem backing up to a local connected drive
TIA,
Peter

I haven't got access to the server right now (so I can't provide the complete details), but something like 6-700 GB (which is more than it shows in the client time machine windows, but less than what is true (which was around 1,5 TB))

Get Total DB size , Total DB free space , Total Data & Log File Sizes and Total Data & Log File free Sizes from a list of server

how to get SQL server Total DB size , Total DB free space , Total Data & Log File Sizes and Total Data & Log File free Sizes from a list of server

Hi Shivanq,
To get a list of databases, their sizes and the space available in each on the local SQL instance.
dir SQLSERVER:\SQL\localhost\default\databases | Select Name, Size, SpaceAvailable | ft -auto
This article is also helpful for you to get DB and Log File size information:
Checking Database Space With PowerShell
I hope this helps.

Windows Server 2012 Logical Disk Free Space (%) Low

I enabled the monitor "Windows Server 2012 Logical Disk Free Space (%) Low" and configured a low threshold to test. I started to get a bunch of warnings from servers, for example:
The disk \\?\Volume{ee0222ed-16de-40a5-af89-f95db3fdf5a4} on computer PC is running out of disk space. The value that exceeded the threshold is 11% free space.
Now I checked on the server, and all the disks have more than 11% free space. Additionally, I don't see any disks with such a name/guid.
When looking at the additional knowledge of the monitor, I see that it is using the following information:
Object Name: Logical Disk
Counter Name: PercentFree
My question is where is this disk coming from, and how can I avoid these disks from creating false alarms? When looking in the Windows Server
From my analyzing the DB, I see that these are the partitions on the server without a volume letter. Any way to avoid getting these discovered and/or alerts, without overriding each one?

Hi,
These "strange" disks are called mount points.
They get discovered by the "Mount Point Discovery Rule".
Go to your authoring => rules => search for the rule above and disable it.
If you want to remove all the instances in your environment you need to use Remove-SCOMDisabledClassInstance
powershell cmdlet.
More info on the cmdlet can be found here: http://technet.microsoft.com/en-us/library/hh920257%28v=sc.20%29.aspx
If you have any more questions please do not hesitate to ask
It's doing common things uncommonly well that brings succes. Check out my SCOM link blog:
SCOM link blog

Need to find the free space on storage server

Hi,
I need to find the free space on storage server through Java code, and even find whether web server has access to the storage server.
So please tell me how do i do that.

This will be through an API for your "storage
server". It would be helpful if you at least
indicated what this "storage server" is: a NFS? an
FTP site? something else?I forgot to mention that. Its NFS. Please let me know
clearly, what APIs I need to use and in simple how.How am I supposed to clearly know this?
Consult the documentation for your NFS system and figure it out. That's what to do.

Logical disk free space counters missing for server 2008 r2 and 2012 r2

I'm trying to get low disk space alerts for server 2008R2 and 2012 R2. While the monitors exist for 2008 and 2012 (Not-R2), they are missign for all R2 operating systems. Any idea how to either obtain these monitors, or create them so I can
get alerts for % disk free alerts?

What is your meaning of " monitors exist for 2008 and 2012 (Not-R2), they are missing for all R2 operating systems."? Does it means that the monitor is missing on all Windows 2008 R2 and Windows 2012 R2 machine or it just a blank circle ?
By default, Windows XXX Logical disk Free Space monitor is enable for all windows XXX. You may check whether an override to disable it. Moreover, Windows Server XXXX Logical Disk Free Space (%) Low and Windows Server 2008 Logical Disk Free Space (MB) Low
is disable by default and you should manually enable it.
Roger

I have to backup of Gmail with Thunderbird Portable, so I could free some space on server - but when I use IMAP (to keep labels) after deletin on server...

I have to backup of Gmail with Thunderbird Portable, so I could free some space on server - but when I use IMAP (to keep labels) after deletin on server...
...my post also deletes on Thunderbird. Please make an option to prevent it, so deleting on a server doesn't effect mail in the Thunderbird. I would be so happy to have it...
David

First Thunderbird portable is supported by its author at portableapps.com.
Secondly you are describing exactly how the IMAP email standard works and Thunderbird has no control over that.
Thunderbird has Local Folders to move messages that you want to keep locally. Maybe the portable version does too.

Getting folder free space in a Windows 2003 server with folder cuotas

Dear Friends:
First I have to request apologizes about my bad English.
I was wondering if the following could be done: stablish a folder cuota un Windows 2003 Server R2, and retrieve the folder free space with Java.
With the file.getUsableSpace, I can obtain the free space of the entire partition, but I'm only interested in a specific folder.
Is that possible?
Thanks in advance.
R. Camps.

Dear Andrew:
Thank you for your suggestion, but I know more or less how to configure the quotas over Windows folders. That is not a problem.
I will try to explain my problem in other words. Imagine a folder called "c:\myfolder", with a quota of 2Gb, in a hard disk with 250Gb of total space.
When I do:
File f=new File ("c:\myfolder");
long s=f.getUsableSpace();the method getUsableSpace returns 250Gb, not 2Gb. For me, it would be wonderful to obtain the free space of the quota value, not the free space of the partition.
Thank you very mucch for your attention.
R. Campos.

DFSR Error that the server does not have Adequate free space. But it does.

Hi, I have a 3 memeber DFS replication group on Windows 2008 R2 servers. On one of members replication stopped and the Health diagnostics report states that there is not enough disk space on the drive to replicate. But there is. It
replicates to the other member with much less free space. I have increased the staging quota after running the caculation command in Power shell to determine the largest 32 files. There is pleanty of free space. I have restarted the
DFS service and restarted the server. I have created a new Replication group on the same volume and it works fine.
Any Ideas?
Steve
Steve

Hi Steve,
It will only copy the changed data to sync all files when re-add the failing member server back to the replication group. If the changed data is very large, you could do a robocopy to copy the changed data, then re-add the failing member server back to the
replication group.
You could refer to the article below to know some considerations when re-add a member server back to a replication group.
After you re-add a member server to a DFS replication group in Windows Server 2003 R2, initial replication does not occur on the member server, and changes in the replicated folder are replicated unexpectedly to other replication partners
http://support.microsoft.com/kb/961655
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Querying free space on RDBMS server's drive from within the RDBMS?

Hi,
I would like to query free space on a certain drive of the RDBMS
host mashine from within the RDBMS. Is this feasable?
TIA,
Tamas Szecsy

Depends on the OS and what type of object you are querying from.
if in Sql*plus you can use the 'host' command to get into the
shell and execute OS commands (bdf on HP-UX for example). I've
never seen an Oracle package that queries that sort of
information.

Not Enough Free Space on NetBoot Image Partition

Since the NetBoot server isn't all that popular, I'm going to explain how it works a bit before I get into my problem.
I assume everyone knows how it works on the client end. You choose an image and your Mac boots that image over the network. Quick, easy, painless. It's a cool system. So on the server/admin side…
Every version of OS X Server comes with it's own System Imaging Utility. So lets say you want to make a netboot image with some utilities on it. So you take an external hard drive. Make two partitions on it. On one partition, you set it up to be the netboot image. So you install all of the utilities you want installed. You configure all of the preferences just the way you want them. Set your background image, etc, etc. On the other image, you just do a quick clean plain installation of your OS. And you also install your OS X Server Admin tools (or in case of 10.8, the Server app). So once your image-to-be is configured, you boot the second partition, and run the imaging utility. This utility will turn your volume into a netboot image. A netboot image is basically just a folder with some .plists in it, a read-only disk image of your initial volume, and a kernel or two (10.5).
NetBoot images are read-only. So when you boot them, you can make as many changes as you want. But once you shut down, all changes are lost. Every time any mac boots a netboot image, it is booting the image exactly as it was when you made it. The changes you make are stored in shadow files on the server that you can periodically toss, since they are only used during the current active session. Once you reboot, the shadow files are useless.
So here is the problem: When you make a netboot image from a real volume, the utility only leaves a small amount of free space on the volume. Even though the disk image is read only, the amount of free space matters because that's still all you get to use. In other words, if the .dmg file in the netboot image i just made only has 900 MB of free space in the volume, then that's all I get for free space on any machine I boot off that image. Even though the image is read only, and all of the "free space" is actually being stored as shadow files on the server, that limit is still applied. And 900 MB is not very much free space. So you can boot a utilities volume and if a program eats up a lot of ram, that virtual memory can eat up what little free HD space you have, and suddenly your netboot image is not very functional.
Now being the clever fellow that I am, I came up with a solution to this problem last time around. I used the following command to resize the partition (and only the partition) of the .dmg file, inside the netboot image (netboot images are just folders).
hdiutil resize -size 60g -partitiononly NetBoot.dmg
This resized the volumes to 60 GB. But it was all blank space, so the .dmg file's size did not change. It would just mount as a read only volume with 40 GB of free space instead of a few hundred MB. This little trick worked very well. But it's not working any more. I can't figure out why. But every time I try to run this command on the .dmg file, I get an error very similar to the following:
hdiutil: resize request 125829120 is above maximum size 18005952 allowed.
hdiutil: resize: failed. Invalid argument (22)
I get this error while running 10.8, 10.7, or 10.6. I get this error whether I'm trying to resize an image containing 10.8, 10.7, 10.6, 10.5, 10.4 or 10.3. I get this error whether I convert the image to a read/write image first, or even a spare image first. I get this error whether the original hard drive that volumes were on, is partitioned as APM or GUID.
The "maximum size" listed in the error message is different for each image I try to resize. It's as if the tool is trying to fit the increase volume inside the existing free space of the image's volume. Which isn't what I'm trying to do at all.
I've been using netboot images filled with utilities for years now. And overall it works very very well. I started back when the first macbooks came out with no firewire. I quickly realized I needed a better solution than booting my Mac into firewire mode to repair other Macs. And then when I got into it, I realized I could host images of all different OS versions. So now I can plug my MBP into a client's network, and boot any Mac they have off of a utility volume of any version of Mac OS X needed, all the way down to 10.3, all at the same time. And I also have NetInstall volumes too that let me install OS X for all these versions as well. The only real quirk I've had over the years, is this 'free' space issue. In the past (before the last time I updated my images, where I used the command above to resize the partitions and solve the problem), what I've done when I've ran into a HD pinch while working, is to immediately start deleting apps I don't think I'm going to need, right off the netbooted Mac. This frees up space on the netboot volume and the system is happy. And again it's all read only, so I'm not actually making changes to the image itself. One real half assed solution I thought of was to set up all of my netboot volumes as having a 1 GB file in their trash and not emptying it before creating a netboot image from the volume. Then when this problem came up and the OS was running out of disk space, I could just empty the trash. I'm quite sure this little trick would have worked, but it's so half-assed. I'd much rather just have more free space on the mounted disk images.

But how did my command work so perfectly last time? Here's an image. On the left, the info window of the disk image inside my 10.7 Utilities netboot image. On the right, the info window for that disk image's mounted volume. The file is only 7 GB and the volume is a 30 GB volume with ~23 GB free. None of the free space of the volume is using up any actual disk space in the .dmg file. I did this once, there's got to be a way to reproduce this again?
Here's the same thing with my 10.6 Utilities netboot image. Also in case I'm not being clear, these netboot images these screen shots are of, are from the last time I updated my netboot images ~11 months ago. These are not my current batch that I'm trying to finalize.

Re-use of free space

Hi,
after a large client delete or after important data archiving, does Oracle re-use new freed space into datafile ? ... we need to delete a large client and then copy e new mid-size client but we haven't a lot of free space in dev system.
Regards.
Ganimede Dignan.

Hello Ganimede,
>> after a large client delete or after important data archiving, does Oracle re-use new freed space into datafile ?
Oracle reuses the freed space inside the same segment. For example if you have freed space in table MSEG, you can reuse the allocated space only for table MSEG (=same segment).
For indexes its a little bit "special", because the freed space (in blocks) can only be reused if they are completely empty, because of the index must be sorted.
You can take a look at the ALL_TABLES on column AVG_SPACE to estimate the freed size in the tables (but take care, the values are only updated on statistic gathering):
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/statviews_2105.htm#i1592091
Regards
Stefan

WBAdmin BMR backup says "There is not enough free space on the backup storage location to back up the data."

We're doing nightly BMR backups of a small 2012 R2 Hyper-V host via wbadmin to 2TB USB disks, via
wbadmin start backup -backupTarget:z: -quiet -noverify -vssFull -include:e:,c: -allCritical
(where E: contains the sole VM).
We are using the same backup system on other similar Hyper-V hosts running 2008 R2 and 2012, with no problems. However, with this 2012 R2 host, after a few months of no problems the backups started failing with:
There is not enough free space on the backup storage location to back up the data.
This made no sense, and continues to make no sense:
The 2TB backup disks are only half full (>1TB free), with 600GB of unallocated shadowstorage.
There should be room for many more backups on these disks. Each currently contains 11 to 13 backups, with the initial full backup having required about 600GB and each subsequent backup only requiring another 20GB to 40GB.
There is over 40GB free on the C: drive and 300GB free on the E: drive; free space on the host volumes is not an issue.
Increasing the shadowstorage limit on the backup disks to unbounded doesn't resolve the issue.
This is not a problem of a RECOVERY partition that's too small, and SystemState backups always complete successfully.
The first workaround we found was to temporarily reduce (not increase) the shadowstorage allocation on the E: drive (containing the VM) and then increase it back (with the end result of deleting old shadow copies).
This worked reliably, but looking for a root cause led us to uninstall the Windows Updates installed mid-September (in particular the Aug 2014 and Sep 2014 roll-ups), which preceded the start of this problem. But instead of resolving the problem the uninstalls
made it worse, in that our workaround stopped working.
We reinstalled the Windows Updates, and then tried setting backup performance to normal, in case the problem was related to VSS on the host volumes, but the errors continued.
At this point the only way we've found to work around the error is to delete 1 or 2 of the oldest backups on the destination disk, via
wbadmin delete backup -backupTarget:z: -deleteOldest
after which the new backup will succeed.
But, again, this makes no sense, as the destination disks are only half full, and even if space was an issue wbadmin should delete old backups as required. And this same system is working fine on 2008 R2 and 2012.
Any suggestions?
Thanks,
John

Hi John,
Please check run the command below to check if the space required to complete the backup causes the snapshot storage space to become less than 1/8 of the target size.
vssadmin list shadows /for=x: will list the shadow copies on x: and creation time.
WSB will not shrink the diff area to less than 1/8 of Target volume size as we do not want to lose all past backups just to accommodate this one.
For more detailed information, please refer to the article below:
Windows Server Backup automatic disk usage management
http://blogs.technet.com/b/filecab/archive/2011/03/14/windows-server-backup-automatic-disk-usage-management.aspx
V. Backup, Restore and Disaster Recovery
http://social.technet.microsoft.com/wiki/contents/articles/1846.v-backup-restore-and-disaster-recovery.aspx?Sort=MostUseful&PageIndex=1
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Need to separate drive alerts with Logical Disk Free Space monitoring in SCOM 2012

I have an interesting need here to separate our SCOM alerts for Logical Disk Free space so that one alert is for OSSystem drives ONLY (C:/D:) and the other monitor alerts on all APP drives only (E:, etc). So far we have had great success using Kevin Holman's
blog post.
http://blogs.technet.com/b/kevinholman/archive/2009/11/24/writing-monitors-to-target-logical-or-physical-disks.aspx
We have overrides set so that the monitors report ONLY the percentage of free space left and ignores any MB threshold. So far so good, the alert comes in that host A reports low disk space on D: at 2.345...% free or host B reports low disk space on F: at
4.567...% free space etc. Now that we have our monitors working within the Windows Server classes Logical Disk, we need to set these monitors so that one is just for C or D drives with the alert named system Logical Disk Free Space OS Disk Warn and the other
monitor just reports on E - Z drives (excluding C or D) with the alert named Logical Disk Free Space APP Disk Warn.
We are very new to SCOM so I made the rookie mistake of creating a dynamic group for all Windows Server 2003 Logical Disk class that only includes Device Name = C or D. But found out too late you cant point a monitor to a group, it has to target a class.
And using the current monitors we set up with the above blog uses the correct logical disk class, but it doesnt care what instance (device Id = value), it will report low disk space on ANY logical drive. How in the world can we separate and exclude these monitors
so that one alerts only on OS disks (C and D) and the other only alerts on app disks (E through Z)?

Hi Kevsharp,
Quite confusing after reading your question.
So based on your requirement, What i understand is you need separate alerts for all the drives of the disk is running at low or out of space right ?
For the above just create a simple performance counter monitor and use the same counters as kevin has used in his blog.
Now Target: Use Windows server operating system (This will target all the Windows operating system agents in your SCOM. If the specified discovery MP's are installed).
Set a threshold Below 10% is critical or what ever. You will get the alerts in your console.
Gautam.75801

Free Space On server

Similar Messages

Maybe you are looking for