Unsolved

This post is more than 5 years old

6 Posts

566

February 13th, 2007 03:00

File type device used space

I have a problem with Networker 7.3 on a Windows Server 2003;

I created a File type device for diskbackup purpose; the device is a folder in a striped set of 4,5 TB.

Backups directed to file device fail because the device is marked full (with about 60 GB of used space) on the Device pane on Networker Console; the problem is that on the file system I can see more than 900 GB of free space available!!

It seems that Networker misunderstands the real capacity of the disk or that there is some kind of size limit for File type device.

Anyone has helpful suggestion??

Thanks

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

February 13th, 2007 03:00

I doubt NW misunderstood anything in this case (unless you are really playing with 7.3 where anything is possible). Are you using file or advance file device (it seems as file device so I would suggest to use advanced one)? Did you see any I/O error prior to device being marked full? What is the capacity defined for device (if using file device)? What tier license do you use and is this the only disk device for datazone? Are you really using 7.3 - if yes you should really skip to 7.3.2 jumbo ASAP.

6 Posts

February 13th, 2007 05:00

Here are the answer to your questions:

- I am running Networker 7.3.
- I am using File Type device; I choose this instead ADV because it supports Consolidation.
- I havn't set the default capacity for this volume.
- I am using a tier 2 diskbackup license (1 to 6 TB)


Looking messages file on networker server I can see "NetWorker media: (warning) J:\diskbackup writing: No space left on device, at file 1909324381 record 1", that means that filesystem is full and no more data can be written; after a while an instance of nsrim checked the media db and deleted about 900 GB of expired savesets but volume mode was left "full".
I use another volume (called Clone.00) on the same disk J: to clone some tape backups and this volume's mode is correctly switched to "appendable" at the end of db checking.

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

February 13th, 2007 06:00

I don't remember anymore if deleting saveset would change volume to appendable when using ordinary file device, but I assume it should. I would recommend to update to latest patch level first (7.3.2 jumbo).

It sounds as marking it full was correct action (if you sum those 900GB, data already written and some data from cloning device).

6 Posts

February 13th, 2007 06:00

This behaviour sounds quite strange....I have 2 file device configured on the same disk: one of those, labelled Clone.00, is marked as "appendable" when expired savesets are deleted, but the other one, labelled Disk.03, is left in "full" mode even if disk space is free.

I will apply latest patch soon.
I am also thinking about creation of more file devices (labelled Disk.nn): I can put these devices in Diskbackup pool so Networker can mount an empty device when the previous is full (as happens with tape devices)
do You think this can solve my problem?

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

February 13th, 2007 07:00

I think having multiple NW disk devices on same disk is not good thing. Actually there was an document in old LGTO KB where they even went so far to state it was not supported.

0 events found

No Events found!

Top