Unsolved
This post is more than 5 years old
6 Posts
0
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
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
0 events found
No Events found!


ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
February 13th, 2007 03:00
cesia
6 Posts
0
February 13th, 2007 05:00
- 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.
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
February 13th, 2007 06:00
It sounds as marking it full was correct action (if you sum those 900GB, data already written and some data from cloning device).
cesia
6 Posts
0
February 13th, 2007 06:00
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?
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
February 13th, 2007 07:00