Backup Windows Server to NAS
I have a Windows Server 2012 R2 that I want to backup to a synology NAS (412+) network share.
I've created a shared folder on the NAS.
In windows backup when I select "Backup Schedule..." and go through the wizard I select:
- Back up to a shared network folder
- I add "nasbackupetc..." under the Location: field (I can browse to that directory via windows exporer and create files in it).
- Then I press "Next" and I get Windows Security showing me a dialog to provide my credentials.
- I click "Finish" and then I get: "Creating backup schedule..."
- a few moments later: "The user name being used for accessing the remote share folder is not recognized by the local computer".
which fails the backup.
My nas is added to the domain (so I enter a domain user credentials, that has access to the folder)
I've also tried different ways to sign in (user, local server user, nas user, domainuser, user@domain, user@domain.local, domain.localuser, ...) everytime with the same message.
I've mapped a network drive but in Windows Backup I cannot select that mapped network drive (e.g. Z: ) to backup.
At synology support, I don't know if they don't care but their suggestions don't work (and sometimes they think I want to backup my nas, instead of creating a backup of a server to a nas.).
Anyone who has more info to solve this?
(I've also disabled SMB 2 and Large MTU)
backup nas windows-server-2012-r2
|
show 3 more comments
I have a Windows Server 2012 R2 that I want to backup to a synology NAS (412+) network share.
I've created a shared folder on the NAS.
In windows backup when I select "Backup Schedule..." and go through the wizard I select:
- Back up to a shared network folder
- I add "nasbackupetc..." under the Location: field (I can browse to that directory via windows exporer and create files in it).
- Then I press "Next" and I get Windows Security showing me a dialog to provide my credentials.
- I click "Finish" and then I get: "Creating backup schedule..."
- a few moments later: "The user name being used for accessing the remote share folder is not recognized by the local computer".
which fails the backup.
My nas is added to the domain (so I enter a domain user credentials, that has access to the folder)
I've also tried different ways to sign in (user, local server user, nas user, domainuser, user@domain, user@domain.local, domain.localuser, ...) everytime with the same message.
I've mapped a network drive but in Windows Backup I cannot select that mapped network drive (e.g. Z: ) to backup.
At synology support, I don't know if they don't care but their suggestions don't work (and sometimes they think I want to backup my nas, instead of creating a backup of a server to a nas.).
Anyone who has more info to solve this?
(I've also disabled SMB 2 and Large MTU)
backup nas windows-server-2012-r2
If you are using the NAS only for backup purpose i would recomend to create a ISCSI Volume with a LUN and attatch the nas using the ISCSI_initiator. Doing this the NAS appears to the server like it is a normal hard drive.
– Ivan Viktorovic
Feb 2 '15 at 8:33
Can you create a local user on the NAS that has RW access and then you can try the username preceeded by the NAS hostname, e.g.NAS1nasuser
? Not ideal, but a workaround. Have you also checked that your domain users have RW on the NAS, I'm assuming it's SAMBA so you may need to add your domain groups to the SAMBA config.
– Kinnectus
Feb 2 '15 at 8:35
@IvanViktorovic nas also have other things, so I can't do that.
– juFo
Feb 2 '15 at 8:36
@BigChris I've already tested this and yes my domain group/user has RW access (via windows explorer I can create, modify and delete files).
– juFo
Feb 2 '15 at 8:37
1
I just wanted to add that after you create the local admin account on the NAS and on the domain, you do not use thedomainuser
ornasuser
. Simply use theusername
andpassword.
– Travis
Jan 15 at 16:05
|
show 3 more comments
I have a Windows Server 2012 R2 that I want to backup to a synology NAS (412+) network share.
I've created a shared folder on the NAS.
In windows backup when I select "Backup Schedule..." and go through the wizard I select:
- Back up to a shared network folder
- I add "nasbackupetc..." under the Location: field (I can browse to that directory via windows exporer and create files in it).
- Then I press "Next" and I get Windows Security showing me a dialog to provide my credentials.
- I click "Finish" and then I get: "Creating backup schedule..."
- a few moments later: "The user name being used for accessing the remote share folder is not recognized by the local computer".
which fails the backup.
My nas is added to the domain (so I enter a domain user credentials, that has access to the folder)
I've also tried different ways to sign in (user, local server user, nas user, domainuser, user@domain, user@domain.local, domain.localuser, ...) everytime with the same message.
I've mapped a network drive but in Windows Backup I cannot select that mapped network drive (e.g. Z: ) to backup.
At synology support, I don't know if they don't care but their suggestions don't work (and sometimes they think I want to backup my nas, instead of creating a backup of a server to a nas.).
Anyone who has more info to solve this?
(I've also disabled SMB 2 and Large MTU)
backup nas windows-server-2012-r2
I have a Windows Server 2012 R2 that I want to backup to a synology NAS (412+) network share.
I've created a shared folder on the NAS.
In windows backup when I select "Backup Schedule..." and go through the wizard I select:
- Back up to a shared network folder
- I add "nasbackupetc..." under the Location: field (I can browse to that directory via windows exporer and create files in it).
- Then I press "Next" and I get Windows Security showing me a dialog to provide my credentials.
- I click "Finish" and then I get: "Creating backup schedule..."
- a few moments later: "The user name being used for accessing the remote share folder is not recognized by the local computer".
which fails the backup.
My nas is added to the domain (so I enter a domain user credentials, that has access to the folder)
I've also tried different ways to sign in (user, local server user, nas user, domainuser, user@domain, user@domain.local, domain.localuser, ...) everytime with the same message.
I've mapped a network drive but in Windows Backup I cannot select that mapped network drive (e.g. Z: ) to backup.
At synology support, I don't know if they don't care but their suggestions don't work (and sometimes they think I want to backup my nas, instead of creating a backup of a server to a nas.).
Anyone who has more info to solve this?
(I've also disabled SMB 2 and Large MTU)
backup nas windows-server-2012-r2
backup nas windows-server-2012-r2
edited Dec 6 '16 at 8:55
Burgi
3,88792543
3,88792543
asked Feb 2 '15 at 8:24
juFojuFo
20431121
20431121
If you are using the NAS only for backup purpose i would recomend to create a ISCSI Volume with a LUN and attatch the nas using the ISCSI_initiator. Doing this the NAS appears to the server like it is a normal hard drive.
– Ivan Viktorovic
Feb 2 '15 at 8:33
Can you create a local user on the NAS that has RW access and then you can try the username preceeded by the NAS hostname, e.g.NAS1nasuser
? Not ideal, but a workaround. Have you also checked that your domain users have RW on the NAS, I'm assuming it's SAMBA so you may need to add your domain groups to the SAMBA config.
– Kinnectus
Feb 2 '15 at 8:35
@IvanViktorovic nas also have other things, so I can't do that.
– juFo
Feb 2 '15 at 8:36
@BigChris I've already tested this and yes my domain group/user has RW access (via windows explorer I can create, modify and delete files).
– juFo
Feb 2 '15 at 8:37
1
I just wanted to add that after you create the local admin account on the NAS and on the domain, you do not use thedomainuser
ornasuser
. Simply use theusername
andpassword.
– Travis
Jan 15 at 16:05
|
show 3 more comments
If you are using the NAS only for backup purpose i would recomend to create a ISCSI Volume with a LUN and attatch the nas using the ISCSI_initiator. Doing this the NAS appears to the server like it is a normal hard drive.
– Ivan Viktorovic
Feb 2 '15 at 8:33
Can you create a local user on the NAS that has RW access and then you can try the username preceeded by the NAS hostname, e.g.NAS1nasuser
? Not ideal, but a workaround. Have you also checked that your domain users have RW on the NAS, I'm assuming it's SAMBA so you may need to add your domain groups to the SAMBA config.
– Kinnectus
Feb 2 '15 at 8:35
@IvanViktorovic nas also have other things, so I can't do that.
– juFo
Feb 2 '15 at 8:36
@BigChris I've already tested this and yes my domain group/user has RW access (via windows explorer I can create, modify and delete files).
– juFo
Feb 2 '15 at 8:37
1
I just wanted to add that after you create the local admin account on the NAS and on the domain, you do not use thedomainuser
ornasuser
. Simply use theusername
andpassword.
– Travis
Jan 15 at 16:05
If you are using the NAS only for backup purpose i would recomend to create a ISCSI Volume with a LUN and attatch the nas using the ISCSI_initiator. Doing this the NAS appears to the server like it is a normal hard drive.
– Ivan Viktorovic
Feb 2 '15 at 8:33
If you are using the NAS only for backup purpose i would recomend to create a ISCSI Volume with a LUN and attatch the nas using the ISCSI_initiator. Doing this the NAS appears to the server like it is a normal hard drive.
– Ivan Viktorovic
Feb 2 '15 at 8:33
Can you create a local user on the NAS that has RW access and then you can try the username preceeded by the NAS hostname, e.g.
NAS1nasuser
? Not ideal, but a workaround. Have you also checked that your domain users have RW on the NAS, I'm assuming it's SAMBA so you may need to add your domain groups to the SAMBA config.– Kinnectus
Feb 2 '15 at 8:35
Can you create a local user on the NAS that has RW access and then you can try the username preceeded by the NAS hostname, e.g.
NAS1nasuser
? Not ideal, but a workaround. Have you also checked that your domain users have RW on the NAS, I'm assuming it's SAMBA so you may need to add your domain groups to the SAMBA config.– Kinnectus
Feb 2 '15 at 8:35
@IvanViktorovic nas also have other things, so I can't do that.
– juFo
Feb 2 '15 at 8:36
@IvanViktorovic nas also have other things, so I can't do that.
– juFo
Feb 2 '15 at 8:36
@BigChris I've already tested this and yes my domain group/user has RW access (via windows explorer I can create, modify and delete files).
– juFo
Feb 2 '15 at 8:37
@BigChris I've already tested this and yes my domain group/user has RW access (via windows explorer I can create, modify and delete files).
– juFo
Feb 2 '15 at 8:37
1
1
I just wanted to add that after you create the local admin account on the NAS and on the domain, you do not use the
domainuser
or nasuser
. Simply use the username
and password.
– Travis
Jan 15 at 16:05
I just wanted to add that after you create the local admin account on the NAS and on the domain, you do not use the
domainuser
or nasuser
. Simply use the username
and password.
– Travis
Jan 15 at 16:05
|
show 3 more comments
5 Answers
5
active
oldest
votes
A domain user should be used to do the backup. Because the NAS is belong to a domain, you should give access to a share folder to a domain user, and use DOMAINusername. This use the correct format.
Alternatively, make a new user in active directory with the same name as the local user on your NAS Drive (QNAP) and then make the user a member of admins or backup operators.
Any other combinations than the two above are very unlikely to work.
add a comment |
I was able to get by the error by creating a local user on my 2008 VM server that matched the Synology user name and password. After that I was able to schedule the server backup successfully. (I did join the NAS to the domain before I tried creating the local user, but that did not solve the problem. I am not sure it is even necessary for the fix to work)
add a comment |
Synology DSM 5.2 (beta) now supports SMB 3. Hooray! :-)
SMB 3 encryption for secure transmissions
Support for SMB 3 encryption allows your DiskStation to secure file
transfers to Windows 8 and Windows Server 2012 or later, reducing the
possibility of tampering and eavesdropping when data moves across your
company's network. Protect your sensitive information without
installing or spending resources on extraneous third-party encryption
solutions.
More info: https://www.synology.com/en-us/dsm/5.2beta/
add a comment |
Are you using Windows Server Backup "wbadmin start backup "commands to backup the windows machine on the NAS?
I have faced lot many issues while taking this kind of backups, which was later fixed by setting up Cloudberry backup for synology (free), it has a clean GUI for managing these backups and can be restored without a commercial license onto Synology NAS or any Windows machine.
1
If you'd read the existing answers you would see this has been resolved by an updated released by Synology. Please read existing answers to make sure the answer you're considering is still valid.
– music2myear
Jun 19 '17 at 18:26
add a comment |
- copy the backup image to any partition
- use local administrator
- share backup path with permission every one
- restore the backup
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f872557%2fbackup-windows-server-to-nas%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
A domain user should be used to do the backup. Because the NAS is belong to a domain, you should give access to a share folder to a domain user, and use DOMAINusername. This use the correct format.
Alternatively, make a new user in active directory with the same name as the local user on your NAS Drive (QNAP) and then make the user a member of admins or backup operators.
Any other combinations than the two above are very unlikely to work.
add a comment |
A domain user should be used to do the backup. Because the NAS is belong to a domain, you should give access to a share folder to a domain user, and use DOMAINusername. This use the correct format.
Alternatively, make a new user in active directory with the same name as the local user on your NAS Drive (QNAP) and then make the user a member of admins or backup operators.
Any other combinations than the two above are very unlikely to work.
add a comment |
A domain user should be used to do the backup. Because the NAS is belong to a domain, you should give access to a share folder to a domain user, and use DOMAINusername. This use the correct format.
Alternatively, make a new user in active directory with the same name as the local user on your NAS Drive (QNAP) and then make the user a member of admins or backup operators.
Any other combinations than the two above are very unlikely to work.
A domain user should be used to do the backup. Because the NAS is belong to a domain, you should give access to a share folder to a domain user, and use DOMAINusername. This use the correct format.
Alternatively, make a new user in active directory with the same name as the local user on your NAS Drive (QNAP) and then make the user a member of admins or backup operators.
Any other combinations than the two above are very unlikely to work.
answered Feb 2 '15 at 10:09
OvermindOvermind
7,88331631
7,88331631
add a comment |
add a comment |
I was able to get by the error by creating a local user on my 2008 VM server that matched the Synology user name and password. After that I was able to schedule the server backup successfully. (I did join the NAS to the domain before I tried creating the local user, but that did not solve the problem. I am not sure it is even necessary for the fix to work)
add a comment |
I was able to get by the error by creating a local user on my 2008 VM server that matched the Synology user name and password. After that I was able to schedule the server backup successfully. (I did join the NAS to the domain before I tried creating the local user, but that did not solve the problem. I am not sure it is even necessary for the fix to work)
add a comment |
I was able to get by the error by creating a local user on my 2008 VM server that matched the Synology user name and password. After that I was able to schedule the server backup successfully. (I did join the NAS to the domain before I tried creating the local user, but that did not solve the problem. I am not sure it is even necessary for the fix to work)
I was able to get by the error by creating a local user on my 2008 VM server that matched the Synology user name and password. After that I was able to schedule the server backup successfully. (I did join the NAS to the domain before I tried creating the local user, but that did not solve the problem. I am not sure it is even necessary for the fix to work)
answered Dec 4 '16 at 19:39
Tim ShawTim Shaw
111
111
add a comment |
add a comment |
Synology DSM 5.2 (beta) now supports SMB 3. Hooray! :-)
SMB 3 encryption for secure transmissions
Support for SMB 3 encryption allows your DiskStation to secure file
transfers to Windows 8 and Windows Server 2012 or later, reducing the
possibility of tampering and eavesdropping when data moves across your
company's network. Protect your sensitive information without
installing or spending resources on extraneous third-party encryption
solutions.
More info: https://www.synology.com/en-us/dsm/5.2beta/
add a comment |
Synology DSM 5.2 (beta) now supports SMB 3. Hooray! :-)
SMB 3 encryption for secure transmissions
Support for SMB 3 encryption allows your DiskStation to secure file
transfers to Windows 8 and Windows Server 2012 or later, reducing the
possibility of tampering and eavesdropping when data moves across your
company's network. Protect your sensitive information without
installing or spending resources on extraneous third-party encryption
solutions.
More info: https://www.synology.com/en-us/dsm/5.2beta/
add a comment |
Synology DSM 5.2 (beta) now supports SMB 3. Hooray! :-)
SMB 3 encryption for secure transmissions
Support for SMB 3 encryption allows your DiskStation to secure file
transfers to Windows 8 and Windows Server 2012 or later, reducing the
possibility of tampering and eavesdropping when data moves across your
company's network. Protect your sensitive information without
installing or spending resources on extraneous third-party encryption
solutions.
More info: https://www.synology.com/en-us/dsm/5.2beta/
Synology DSM 5.2 (beta) now supports SMB 3. Hooray! :-)
SMB 3 encryption for secure transmissions
Support for SMB 3 encryption allows your DiskStation to secure file
transfers to Windows 8 and Windows Server 2012 or later, reducing the
possibility of tampering and eavesdropping when data moves across your
company's network. Protect your sensitive information without
installing or spending resources on extraneous third-party encryption
solutions.
More info: https://www.synology.com/en-us/dsm/5.2beta/
answered Apr 3 '15 at 7:35
juFojuFo
20431121
20431121
add a comment |
add a comment |
Are you using Windows Server Backup "wbadmin start backup "commands to backup the windows machine on the NAS?
I have faced lot many issues while taking this kind of backups, which was later fixed by setting up Cloudberry backup for synology (free), it has a clean GUI for managing these backups and can be restored without a commercial license onto Synology NAS or any Windows machine.
1
If you'd read the existing answers you would see this has been resolved by an updated released by Synology. Please read existing answers to make sure the answer you're considering is still valid.
– music2myear
Jun 19 '17 at 18:26
add a comment |
Are you using Windows Server Backup "wbadmin start backup "commands to backup the windows machine on the NAS?
I have faced lot many issues while taking this kind of backups, which was later fixed by setting up Cloudberry backup for synology (free), it has a clean GUI for managing these backups and can be restored without a commercial license onto Synology NAS or any Windows machine.
1
If you'd read the existing answers you would see this has been resolved by an updated released by Synology. Please read existing answers to make sure the answer you're considering is still valid.
– music2myear
Jun 19 '17 at 18:26
add a comment |
Are you using Windows Server Backup "wbadmin start backup "commands to backup the windows machine on the NAS?
I have faced lot many issues while taking this kind of backups, which was later fixed by setting up Cloudberry backup for synology (free), it has a clean GUI for managing these backups and can be restored without a commercial license onto Synology NAS or any Windows machine.
Are you using Windows Server Backup "wbadmin start backup "commands to backup the windows machine on the NAS?
I have faced lot many issues while taking this kind of backups, which was later fixed by setting up Cloudberry backup for synology (free), it has a clean GUI for managing these backups and can be restored without a commercial license onto Synology NAS or any Windows machine.
answered Jun 19 '17 at 18:01
user8010482user8010482
1
1
1
If you'd read the existing answers you would see this has been resolved by an updated released by Synology. Please read existing answers to make sure the answer you're considering is still valid.
– music2myear
Jun 19 '17 at 18:26
add a comment |
1
If you'd read the existing answers you would see this has been resolved by an updated released by Synology. Please read existing answers to make sure the answer you're considering is still valid.
– music2myear
Jun 19 '17 at 18:26
1
1
If you'd read the existing answers you would see this has been resolved by an updated released by Synology. Please read existing answers to make sure the answer you're considering is still valid.
– music2myear
Jun 19 '17 at 18:26
If you'd read the existing answers you would see this has been resolved by an updated released by Synology. Please read existing answers to make sure the answer you're considering is still valid.
– music2myear
Jun 19 '17 at 18:26
add a comment |
- copy the backup image to any partition
- use local administrator
- share backup path with permission every one
- restore the backup
add a comment |
- copy the backup image to any partition
- use local administrator
- share backup path with permission every one
- restore the backup
add a comment |
- copy the backup image to any partition
- use local administrator
- share backup path with permission every one
- restore the backup
- copy the backup image to any partition
- use local administrator
- share backup path with permission every one
- restore the backup
edited Jun 18 '17 at 4:15
Stephen Rauch
2,27581725
2,27581725
answered Jun 18 '17 at 1:11
islamislam
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f872557%2fbackup-windows-server-to-nas%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If you are using the NAS only for backup purpose i would recomend to create a ISCSI Volume with a LUN and attatch the nas using the ISCSI_initiator. Doing this the NAS appears to the server like it is a normal hard drive.
– Ivan Viktorovic
Feb 2 '15 at 8:33
Can you create a local user on the NAS that has RW access and then you can try the username preceeded by the NAS hostname, e.g.
NAS1nasuser
? Not ideal, but a workaround. Have you also checked that your domain users have RW on the NAS, I'm assuming it's SAMBA so you may need to add your domain groups to the SAMBA config.– Kinnectus
Feb 2 '15 at 8:35
@IvanViktorovic nas also have other things, so I can't do that.
– juFo
Feb 2 '15 at 8:36
@BigChris I've already tested this and yes my domain group/user has RW access (via windows explorer I can create, modify and delete files).
– juFo
Feb 2 '15 at 8:37
1
I just wanted to add that after you create the local admin account on the NAS and on the domain, you do not use the
domainuser
ornasuser
. Simply use theusername
andpassword.
– Travis
Jan 15 at 16:05