This post is more than 5 years old
70 Posts
0
3649
February 21st, 2013 17:00
Windows 2k8 r2 File system backup failing for SQL 2012 server using NMM2.4
Hi All
I am new to NW and we are trying to do implement NW for SQL 2012 DB backups direct to Data domain
File system backups are failing using NMM2.4
Can anyone help me fix this issue ?
Client properties are like this
Saveset-ALL
Backup command-nsrsnap_vss_save.exe
Application information-
NSR_SNAP_TYPE=VSS
NSR_IGNORE_MISSING_SYSTEM_FILES=yes
NSR_VSS_FORCE_SYSTEM_PROVIDER=yes
Please let me know were i am doing wrong? all are exactly in same way including cap locks
Thank you.
No Events found!
CarlosRojas
1.7K Posts
0
February 27th, 2013 03:00
Hi Deepu,
Sorry but I'm very confused.
Can you please clarify?:
1.- Are you running VSS or VDI SQL backups?
2.- Which backups are failing, File System or SQL DB?
3.- Can you please share any error message you are getting (check in /nsr/logs/sg/group_name) and check out if there is anything in there.
4.- Check also the nmm.raw file. Are the nsrexecd and the Replication ManagerAgentPS services running?
5.- Change saveset to C:\Windows\Temp and change NSR_SNAP_TYPE=vss (note the vss in lower case) and please give it a try by running:
savegrp -D3vvv -c client_name group_name and check out the output, if you don't find the error please share it with us.
Thank you.
Carlos.
wmtW1BHxGX12559
1 Rookie
•
100 Posts
0
February 22nd, 2013 01:00
Are you trying to do a filesystem backup or just MS SQL? Is this clustered environment?
If you are planning to do both filesystem and MS SQL backups, please consider dividing those backups in a separate backup groups, and make sure that they do not start at the same time, because you cannot start two or more NMM backups at the same time.
For filesystem it is OK to leave "All" for Save set.
For MS SQL, please run Command Prompt as Administrator and type "nsrsnap_vss_save.exe -? -v" on MS SQL server. What you get as result paste it to the Save set box without quotes.
In both cases you should have at least:
Apps & Modules tab:
Backup command: nsrsnap_vss_save.exe
Application information: NSR_SNAP_TYPE=vss
ble1
4 Operator
•
14.3K Posts
0
February 22nd, 2013 01:00
Can you also share what the error is that you get?
BSequeira
30 Posts
0
February 22nd, 2013 02:00
Hello,
Can you doublecheck you saveset configuration?
If you specified saveset ALL (uppercase), most likely the backup will fail.
Please try specifying saveset: All (Uppercase A, lowercase ll)
If this still fails, please share the error message.
Bruno
Deepu83
70 Posts
0
February 22nd, 2013 10:00
Hi All
This is Windows2k8 r2 server and yes i am trying to backup file system backup of SQL2012 Read only db server its not windows cluster server
Trying OS backup if it completed then i will do DB backups any tips for SQL2012 Always on read only DB side backups are greatly appreciated as well.
Backups are waiting for ever and not giving any errors except the time out errors
Unable to execute save job on host Timed out
Deepu83
70 Posts
0
February 27th, 2013 06:00
Thanks a lot Carlos i fixed the file system backups using NMM which you answered in other thread
Thank you so much ........
Issues with SQL2012 DB secondary replica (read only DB) its part of Windows cluster for primary replica servers A and B
:Start time: Tue Feb 26 19:57:08 2013
43621:(pid 5584):Computer Name: xxxxx User Name: xxxxx
37981:(pid 5584): Cannot connect to resdb database: Program not registered
85555:(pid 5584):Unable to fetch Application Information from resdb database
29336:(pid 5584):Cannot connect to resdb database
43709:(pid 5584):Stop time: Tue Feb 26 19:57:09 2013
Group properties-No snapshot enabled
restart windows-00:01
savegrp parr-0
Client properties-
Saveset-MSSQL: do i need to use MSSQLRD: ?
pool-Datadomian
client driect enabled
no directive
remote user-Sysadmin
password-gave password
backup command-nsrsqlsv -A SQLserver name
Deduplication-data domain
storage node-nsrserverhost
hendix
1 Message
0
March 6th, 2015 06:00
This is what you have to do:
1. Create a domain account
2. make that account an admin on the SQL server
3. Give that account admin rights on the SQL database
4. Edit the secpol.msc, under security policies - disable run all administrators in admin approval mode and admin aprroval mode for the built in administrator account.
5. reboot the system and run your backup again.