Unsolved
This post is more than 5 years old
2 Intern
•
63 Posts
0
1084
April 25th, 2012 02:00
Backup seperate filesystem on DPM server
Hi all,
In our environment, we have a DPM server (Windows 2008 R2), and the windows administrators want us to backup the E:\ - drive only.
This filesystem only contains some binaries and flat files. No databases, no DPM volumes, ...
However, when I start my backup, it seems that it doesn't want to start, even after a very long time, it won't start.
And the CPU on the DPM server is 100% used the entire time.
After some basic checks, I started to do a debug backup (backup command: save.exe -D 9 ), and now I see that VSS starts with a snapshot of the C-drive, and thus also all the DPM volumes (several TB's), this causes the backup to wait, and asks that many CPU.
Any idea how to shut this off on a Win2k8 (since VSS:*=off isn't possible)?
I've attached the head of my debug file (untill it starts with all the DPM volumes) from a backup which only tries to backup 1 file of 1KB on the E-drive
Kind regards
TimTh
2 Intern
•
63 Posts
0
April 25th, 2012 06:00
Hello Carlos,
Thank you for the reply.
I've added the output of the 2 vssadmin commands as attachments (to the original post).
No, I'm not sure that there is nothing more in this volume. As I don't manage this server, I'm unable to look at it.
I've asked the admins, and they told me that nothing special was installed on the E-drive.
I tried several savesets:
But all gave the same behaviour.
The last one is just a single file of 1KB in size.
It is indeed just a regular networker client, no NMM or any other module.
Kind regards
CarlosRojas
1.7K Posts
0
April 25th, 2012 04:00
Hi Tim,
Can you please provide us the output of the following comands?:
vssadmin list shadows
vssadmin list volumes
Also, are you sure there is nothing more in that volume? Change folder options and ensure there is no hidden system files? There will be always system volume information, and that is considered as critical data for VSS.
Also check the configuration of VSS, in case E:\ points to any other drive to place the shadow created.
What is the saveset you specify for that client?
You are using NW client, right? and not NMM.
Thank you.
Carlos.
CarlosRojas
1.7K Posts
0
April 29th, 2012 04:00
Hi Tim,
I didn't see anything really strange...
Could you please run this command on the DPM server and capture the output to a file and attach it here?:
See below information about how to capture all the required information:
You can start diskshadow and logging all outputs to a file by starting a Command Prompt and launching this command:
diskshadow /l c:\diskshadow.out
From the diskshadow prompt, issue the following commands:
reset
list writers
list writers status
list writers metadata
list writers detailed
list providers
exit
The output of all the above commands will be found in c:\diskshadow.out. The output can use useful to see the list of files which are reported by the VSS writers to be included and excluded by the backup.
The reason behind that is to know if there is any writer related file sitting in E:\
Thank you.
Carlos.